[Fixed] Web367 operational issues

Posted in Downtime by

2017-02-01 23:20 UTC: We are investigating the issue and will update the post as soon as we have further details.

2017-02-02 01:16 UTC: Web367 has suffered a catastrophic disk failure. We’ve recovered some data from the server, and have the remaining data in our backups. We’re presently restoring the machine to new hardware and will notify affected customers with the new server details.

2017-02-02 02:48 UTC: The file transfer is 50% complete.

2017-02-02 05:17 UTC: The file transfer is complete. We’re still working on restoring database passwords and permissions. If you notice a problem with your site, please open a support ticket for immediate assistance.

2017-02-02 15:00 UTC: We were able to recover all the data on Web367 and brought the original machine back online.

-
-

[Fixed] Sites on some servers inaccessible

Posted in Uncategorized by

Currently, websites on Web501, Web507, Web513 are be unreachable. We’re actively investigating this, please stand by for further updates.

2016-12-16 03:41 UTC: Websites and applications should be resolving for all three servers. We’ll monitor them for a little while. Please open a support ticket if you believe there are any persisting issues. Thank you for your patience.

-
-

[Fixed] Web349 inaccessible

Posted in Uncategorized by

The server is currently not responding. We are investigating the issue and will update this post as soon as we have further details.

2016-12-14 04:29:30 UTC: We’ve identified, isolated the load on the server. All services should be restored to normal. We will continue to monitor the server. If there are any issues please let us know via support ticket.

 

-
-

[Fixed] Web162 inaccessible

Posted in Downtime by

2016-10-17 01:07 UTC: The server is currently not responding. We are investigating the issue and will update this post as soon as we have further details.

2016-10-17 01:57 UTC: The server is now operational. We’re continuing to monitor it before marking the issue resolved. Thank you for your patience.

2016-10-17 04:25 UTC: This issue is considered resolved. Please open a support ticket if you believe issues persist and we can look into it right away.

 

-
-

[Monitoring] Web473 inaccessible

Posted in Downtime by

The server is currently not responding. We are investigating the issue and will update as soon as we have further details.

2016-09-23 15:09 UTC: We’re still investigating this issue.

2016-09-23 16:03 UTC: The issue is still under investigation.

2016-09-23 17:49 UTC: We find out that a DDoS is in place and we are mitigating it.

2016-09-23 18:55 UTC: We put the server under mitigation.

2016-09-24 23:34 UTC: The attack briefly subsided but had place into mitigation again while we continue to work towards a resolution. We appreciate your patience.

2016-09-25 22:51 UTC: The attack has subsided and mitigation has been removed. We’re continuing to monitor, please let us know if you experience any issues.

-
-

[Fixed] Web522 inaccessible

Posted in Downtime by

The server is currently not responding. We are investigating the issue and will update as soon as we have further details.

2016-09-23 05:15 UTC The server is back online. There was a network issue due to an unexpected kernel error. Thank you for your patience.

 

-
-

[Fixed] Web473 Inaccessible (DDoS)

Posted in Downtime by

The server is currently inaccessible due to high traffic to the machine. We are investigating the issue.

2016-08-06 03:40 UTC: The server has been placed under DDoS mitigation. It is currently accessible, but some customers may experience degraded network connectivity. We continue to monitor the machine closely.

 

-
-

[Fixed] Web442 DDoS

Posted in Problems by

Web442 is currently inaccessible. We are investigating the issue; please stand by for updates.

2016-04-17 03:45 UTC: Our upstream provider have enabled DDOS protection for the server. Network traffic will be degraded during that time. We will remove the DDOS protection as soon as the attack subsides.

2016-04-18 03:25 UTC: The heavy traffic has subsided and mitigation has been removed. At this time the server is stable. We will monitor the server a little further.

2016-04-18 09:30 UTC: The attack has resumed and the server is currently null-routed. We are working to restore the services ASAP.

2016-04-18 13:35 UTC: We’ve managed to mitigate the attack. We are monitoring the server closely.

2016-04-18 14:05 UTC: Our mitigation system was not able to contain the severity of the attack. The server has been null-routed again.

2016-04-18 22:19 UTC: The null route has been lifted and service has been restored. We’ll continue to monitor.

2016-04-20 10:30 UTC: The attack has resumed and our upstream provider has enabled DDOS protection for the server. Degraded network traffic and intermittent connectivity issues are to be expected while DDOS mitigation is active. We are working to restore normal connectivity as soon as possible.

2016-04-22 10:00 UTC: The attack has subsided and normal connectivity has been restored. We’ll continue to monitor.

2016-04-25 04:21 UTC: The attack has resumed and we’re working to have the null route removed and DDoS mitigation services enabled.

2016-04-25 05:27 UTC: The null route was removed under an hour ago and the server should be accessible. Keep in mind there may be intermittent access for some due to the DDoS mitigation service in place.

2016-04-25 10:00 UTC: The connectivity to the server has been stable for several hours. The DDoS mitigation service is still in place and we continue to monitor the server.

2016-04-26 04:25 UTC: The attack has subsided and normal connectivity has been restored. We’ll continue to monitor.

-
-

[Fixed] Web493 inaccessible

Posted in Downtime by

Web493 is currently inaccessible, we’re working with the datacenter to investigate and resolve the outage. Please stand by.

2016-04-11 04:02 UTC:  We’re in the process of rebooting the server to further diagnose the issue.

2016-04-11 05:21 UTC: We find out a faulty network link on server, we have replaced the faulty equipment and the server is up and running at the moment

 

-
-

[Fixed] Web508 DDoS

Posted in Problems by

We are currently experiencing a DDoS attack on web508. Our upstream provider has enabled mitigation for this attack.

There are still some intermittent access issues until the attack subsides further.

We will update this post as soon as we have further information.

2016-04-08 04:40 UTC:  The attack has subsided and Web508 is back online.

2016-04-08 06:24 UTC:  The attack has resumed, we’re continuing to work towards restoring services. Sorry for the troubles, thank you for your patience.

2016-04-08 08:10 UTC: The attack has subsided and Web508 is back online. We are monitoring the server to ensure the proper operation of all services.

2016-04-08 09:40 UTC: The attack has resumed, we are working to restore the services ASAP.

2016-04-08 11:00 UTC: The nature of the attack has changed; we are still working to mitigate it.

2016-04-08 11:40 UTC: At this point the attack was mitigated. We are monitoring the server closely.

2016-04-08 18:45 UTC: Web508 has been stable for the past several hours. We’ll continue to monitor.

2016-04-09 03:57 UTC: Web508 is inaccessible at the moment, we’re working to restore it once more. Please stand by.

2016-04-09 06:55 UTC: The DDoS has subsided, Web508 is now accessible and for the moment stable. We’re continuing to monitor it while looking at other avenues to help further mitigate any future attacks.

2016-04-09 09:30 UTC: The attack is back. We are working to mitigate it.

2016-04-09 10:10 UTC: We managed to mitigate the attack. The server is now operational, but the attack is still ongoing, so we’ll continue to monitor the server.

2016-04-09 14:30 UTC: Web508 has been stable for the past several hours. We’ll continue to monitor.

2016-04-11 02:22 UTC: The attack on Web508 seems to have stopped but we will continue to monitor the server for a little longer to be sure. Thank you for your patience.

2016-04-12 16:03 UTC: The attack on Web508 has resumed and the server is currently null-routed. We’re working to mitigate the attack and restore service at this time.

2016-04-12 16:35 UTC: Connectivity to Web508 has been restored. We’ll continue to monitor.

2016-04-13 23:29 UTC: Web508 has been stable for over 24 hours.

2016-04-15 18:06 UTC: The attack on Web508 has resumed and the server is currently null-routed. We’re working to mitigate the attack and restore service at this time.

2016-04-15 18:52 UTC: Connectivity to Web508 has been restored. We’ll continue to monitor.

2016-04-18 14:10 UTC: The attack on Web508 has resumed and the server has been placed in DDoS mitigation.  The server is now operational, but the attack is still ongoing, so we’ll continue to monitor the server. Some traffic may be blocked or a delayed as part of the mitigation.

 

-
-