[Fixed] Web506 inaccessible

Posted in Downtime by

The server is currently inaccessible. We are investigating the issue.

2016-02-04 06:51 UTC: Apologies for the delay, we’ve been working directly with the datacenter technicians to determine the cause and work towards restoring service to the server.

2016-02-04 07:01 UTC: Services have been restored to normal capacity, Web506 is online. It experienced a hardware issue related to the upstream network, which has been repaired. Please open a support ticket if there are any unresolved issues and we will look into it right away. Thank you for your patience.

2016-02-04 07:41 UTC: There appears to be some re-occurring network disturbances, so we’re re-opening this issue while we take further steps with the datacenter towards  a resolution. Thank you for your patience.

2016-02-04 10:40 UTC: Our datacenter engineers are still working to resolve the network issue. We will update this post as soon as new information arrives.

2016-02-04 11:40 UTC: The network connectivity has been restored through an alternative network interface.  We are still working to get the primary interface online, but things are stable at the moment.

2016-02-04 13:00 UTC: All issues with the network have been resolved.

2016-02-04 18:01 UTC: Web506 has lost connectivity again. We’re working to restore service and will update this post as soon as more information is available.

2016-02-04 20:11 UTC: Our data center team suspects motherboard failure. We’re scheduling a chassis swap at this time.

2016-02-04 20:27 UTC: We’re taking the server down for a chassis swap at this time.

2016-02-05 00:34 UTC: Apologies for the delays. Our datacenter team ran into some issues re-configuring the network interfaces for the new chassis. They are working to get the server up as quickly as possible.

2016-02-05 02:22 UTC: Public access has been restored, though please stand by for further updates confirming resolution on the situation.

2016-02-05 05:18 UTC: The server has been stable for a couple hours now, we’re marking the issue as resolved but will monitor the situation. If you experience any issues you believe to be unresolved, please open a support ticket and we will look into it right away. Thank you again for your patience.

2016-02-05 06:31 UTC: There has been a detectable outage on the server again, we’re once more in communication with our datacenter. Please stand by for further updates.

2016-02-05 09:44 UTC: Currently, the connectivity has been restored, but our data center engineers are still working to resolve the issue permanently. Please stand by for further updates.

2016-02-05 13:00  UTC: The connectivity has been stable in the past hours. We are still monitoring the server closely and working with the data center team towards a permanent resolution.

2016-02-05 14:00  UTC: The network connectivity issue has been resolved permanently.

-
-

[Fixed] Web489 inaccessible

Posted in Downtime by

The server is currently inaccessible. We are investigating the issue.

2016-02-03 23:27 UTC: Web489 is online, we’re still monitoring the server. Please stand by for further updates.

2016-02-04 01:10 UTC: Web489 has been stable for some time now. Please open a support ticket if there are any other issues.

 

-
-

[Fixed] MySQL down on Web416

Posted in Downtime by

The shared MySQL database service on Web416 is currently down. We’re working to restore service at this time. We’ll update this post when more information is available.

2016-01-14 04:16 UTC: All databases have been restored and MySQL is back online. If you have any problems, please open a support ticket.

2016-01-14 08:20 UTC: Some MySQL databases were not properly restored. We are now working on fixing this issue as soon as possible.

2016-01-14 11:45 UTC: All databases have been restored. If you are still seeing any issues, please open a support ticket.

-
-

[Fixed] Web504 inaccessible

Posted in Downtime by

We are checking into the problem, and we’ll get the server back online as quickly as possible.

2015-12-12 23:03 UTC: The server experienced issues with the local NGINX, network configuration. We were able to resolve this and all services should now be functioning as per usual. Thank you for your patience, apologies for any inconveniences.

-
-

[Fixed] Web506 inaccessible

Posted in Downtime by

We are currently looking into the issue and will resolve it as quickly as possible.

2015-12-04 02:20 UTC: The server is back online. Apologies for the downtime. If further issues are detected please open a ticket with support and we will look into it right away.

-
-

[Fixed] Web416 is inaccessible

Posted in Downtime by

We are currently looking into the issue and will resolve it as quickly as possible.

2015-09-01 10:00 UTC:  The shared MySQL database appears to be corrupt.  We are working to restore operation.

2015-09-01 12:00 UTC:  We are in the process of restoring all shared MySQL data from backups.

2015-09-01 16:08 UTC: The database restore is 75% complete.

2015-09-01 18:07 UTC: All databases have been restored.

2015-09-25 21:16 UTC: The public network is inaccessible, we are looking into the issue.

2015-09-25 21:55 UTC: The server is back online.

-
-

[Fixed] Web444 is inaccessible

Posted in Downtime by

We are currently looking into the issue and will resolve it as quickly as possible.

2015-07-30 00:41:47 UTC: Web444 is back online, we’re monitoring the server.

2015-07-30 00:45:49 UTC: Though the server is UP, there may be intermittent access or function while we troubleshoot. Please stand by.

2015-07-30 01:52:16 UTC: Web444 is inaccessible again, our System Administrators persist towards a resolution.

2015-07-30 02:07:00 UTC: Web444 is back online, please stand by for further updates.

2015-07-30 02:35:05 UTC: Web444 is back online, we’ve reduced certain traffic that was causing load spikes making it inaccessible. Please open a ticket if you have further issues and we can assist you.

-
-

[Fixed] Web353 is inaccessible

Posted in Downtime by

We are currently looking into the issue and will resolve as quickly as possible.

2015-07-03 11:00 UTC: Web353 is back online. If you have any problems, please open a support ticket.

2015-07-03 15:01 UTC: The machine is inaccessible again, we are looking into the problem.

2015-07-03 16:33 UTC: The file system is corrupt, we are migrating the machine to new hardware.

2015-07-03 20:19 UTC: As part of the migration process the main IP address will change from 75.126.24.76 to 75.126.217.39. We will update this blog post with the migration progress.

2015-07-03 20:33 UTC: All databases have been restored.

2015-07-03 22:29 UTC: Home directories up to the letter “b” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-03 23:27 UTC: The machine is inaccessible again, we are taking further steps in restoring the machine. Stand by for updates.

2015-07-04 03:01 UTC: The machine is back online and we are continuing to copy home directories.

2015-07-04 04:45 UTC: Home directories up to the letter “e” have been copied to the new server. We’re continuing to copy the rest of the home
directories.

2015-07-04 08:41 UTC: Home directories up to the letter “f” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-04 09:50 UTC: Home directories up to the letter “g” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-04 11:50 UTC: Home directories up to the letter “i” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-04 13:00 UTC: Home directories up to the letter “j” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-04 14:00 UTC: Home directories up to the letter “k” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-04 15:00 UTC: Home directories up to the letter “n” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-04 16:00 UTC: Home directories up to the letter “p” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-04 16:20 UTC: Home directories up to the letter “r” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-04 17:15 UTC: Home directories up to the letter “s” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-04 19:15 UTC: Home directories up to the letter “t” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-05 03:06 UTC: Home directories up to the letter “v” have been copied to the new server. We’re continuing to copy the rest of the home directories.

2015-07-05 03:38 UTC: The migration is now over. If you experience any issues with your sites, open a ticket and we’ll look into it ASAP. We have setup a proxy on the old server to redirect all HTTP and HTTPS traffic to the new server. The proxy will stay active for 5 days.

-
-

[Fixed] Web389 Down

Posted in Downtime by

Web389 is currently inaccessible. We are investigating the issue. We will update this post as soon as we have more information.

2015-04-17 04:30 UTC The  server is back online and functioning normally.

-
-

[Done] DDoS attack on Web419

Posted in Downtime by

The server is currently under a heavy DDoS attack. We are working with our network engineers to resolve the issue.

2015-02-11 02:55 UTC: The attack has subsided, services have been restored, we are monitoring the server.

2015-02-11 07:37 UTC: The server has remained stable since the last update.

 

-
-