status / Shared Server #1
100% Uptime for the last 30 days Shared Server #1
99.971% July 2021
Sun Mon Tue Wen Thu Fri Sat
27
28
29
30
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1
2
3
4
5
6
7
99.982% August 2021
Sun Mon Tue Wen Thu Fri Sat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
1
2
3
4
5
6
7
8
9
10
11
100% September 2021
Sun Mon Tue Wen Thu Fri Sat
29
30
31
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
1
2
3
4
5
6
7
8
9

Incidents

September 9th, 2021

Server #2 overload
Affected services: Shared Server #2
Monitoring

We are pleased to inform you that migration to the new machine has been completed now, and your websites will start serving from the new server.

If your domain is not using our default nameservers (e.g: is currently pointing to Cloudflare), a follow up email with specific instructions related to your service has been sent out, which contains details of next steps to be done by you.

If you are using our default nameservers: ns1.bestwebhosting.top ns2.bestwebhosting.top then no further steps required regarding DNS.

It is worth noting, however, that you may experience errors if attempting to access your website, so simply just clear your DNS cache from system and browser, as they may be storing old server IP on which the website no longer exists.

We are keeping a close eye and monitoring things as the operation is concluded. Once there's another update, it will be communicated to you here.

We would like to thank you all for your patience and understanding as we worked hard on overcoming this unprecedented incident, and it is worth noting that services in this server have been already compensated by the addition of extra month to their active subscription periods.

Thank you for being a loyal customer of ours

  • WevrLabs Hosting Team
Identified

Firstly, we would like to express sincere apologies for the extended amount of downtime caused by the disk failure of Shared Server #2 last night.

The DC team was able to install the new disks and rebuilt the raid array, and has now put the server back online, and began the process of migrating websites to the new machine.

We appreciate your patience during this time and apologise for the inconvenience caused.

Investigating

Following on this, the data center team has attempted to boot to the OS which failed and were forced to begin a raid rebuild. Unfortunately, this has an expected time of 12 hours left before completion.

The DC team have been discussing the options available to us and have begun works to spin-up a completely new machine on the new cloud infrastructure (which was already in final preparations ahead of the planned infrastructure migration as announced past days), however, it seems that this server will be the first one to be deployed on the new cloud infrastructure, and the DC team is readying for restoration to this, as part of the recovery plans.

Our partners at the data center have confirmed to us they are currently able to mount the server home directory and see no evidence of any data loss. However, there may be plans to resort to restoration of data from the latest available backup point which took place earlier this morning.

We appreciate your patience during this time and apologise for any inconvenience.

Identified

The DC team is still undergoing further maintenance operations to bring this server back online.

Investigating

The hardware swap has been completed, and now the server is currently undergoing final checks before being brought back online.

Identified

Our engineers are now in the process of replacing non-hot-swappable disk drive, which requires brief shutdown.

Investigating

hello,

We are investigating an overload issue with Server #2 ... Our engineers are working hard to restore things back to normal operation.

We apologize for the inconvenience this have caused.

(note that services on other servers are not affected by this).