Shock Hosting Outage History

cPanel has rolled out a fix and the user interfaces are now available again as servers complete the license checks.

Type: Incident Duration: 1 hour and 1 minute Affected Components: New York Sep 8, 09:33:00 GMT+0 - Investigating - We are currently investigating an outage with NY-S4; it appears to be refusing to power up, so the DC tech will be investigating further. Sep 8, 10:34:00 GMT+0 - Resolved - The machine's power cables were reseated, and it is now booting up. All services should be back online.

Type: Incident Duration: 19 minutes Affected Components: Chicago Sep 2, 15:42:33 GMT+0 - Identified - PDU-B in our West Chicago rack is currently experiencing failures, causing intermittent power; replacement is being arranged. Sep 2, 16:01:14 GMT+0 - Resolved - The PDU has been replaced; all affected services should be back online.

Type: Incident Duration: 48 minutes Affected Components: Frankfurt Sep 1, 11:06:04 GMT+0 - Investigating - We are aware of an outage in Frankfurt and are investigating the cause. Sep 1, 11:54:33 GMT+0 - Resolved - Our datacenter provider claimed they had not received our monthly rent payment, but after we provided proof, they located the payment and restored our service.

Type: Maintenance Duration: 1 hour Affected Components: Frankfurt Aug 25, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Aug 25, 14:00:00 GMT+0 - Identified - On Monday, August 25th, at approximately 4:00 PM CEST (GMT +2) we will be upgrading the memory capacity of the DE-K1 VPS node in Frankfurt. Unfortunately, the node needs to be removed from the server cabinet to perform the upgrade, so we expect about 30 to 60 minutes of downtime for this task to be completed. Please let us know if you have any questions or concerns. Aug 25, 14:00:01 GMT+0 - Identified - Maintenance is now in progress

Type: Incident Duration: 59 minutes Affected Components: Singapore Jun 6, 05:10:07 GMT+0 - Investigating - We are currently investigating this incident. Jun 6, 06:09:07 GMT+0 - Resolved - This outage was due to faulty memory causing the server to enter a boot loop. The server has been brought back online and we will schedule a replacement of the faulty memory as soon as possible.

Type: Maintenance Duration: 22 minutes Affected Components: Singapore May 28, 06:00:01 GMT+0 - Identified - Maintenance is now in progress May 28, 06:00:00 GMT+0 - Identified - 2 x memory DIMM's determined to be faulty will be replaced in SG-K4\. We expect approximately 30 to 60 minutes of downtime for this task to be completed. May 28, 06:21:44 GMT+0 - Completed - Maintenance has completed successfully.

Type: Maintenance Duration: 1 hour Affected Components: Los Angeles Mar 29, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 29, 14:00:00 GMT+0 - Completed - Maintenance has completed successfully Mar 29, 13:00:00 GMT+0 - Identified - On Saturday, March 29th at 6:00 AM Los Angeles time (PST) we will be moving the following VPS nodes to a different cabinet in the same datacenter (CoreSite LA2) to balance the power load: \- LA-K3 \- LA-K4 We anticipate about 30 minutes of downtime to fully shut down the nodes, move them to the other cabinet, and then power them back on. Please let us know if you have any questions or concerns.

Type: Maintenance Duration: 2 hours and 13 minutes Affected Components: Denver, Los Angeles Feb 9, 14:13:16 GMT+0 - Completed - Maintenance has completed successfully. Feb 9, 12:00:00 GMT+0 - Identified - As mentioned in our notification email, we will be upgrading these servers running CloudLinux 7 to CloudLinux 8. The upgrade will take approximately 1 to 2 hours, and there will be intermittent downtime for websites and cPanel during the upgrade process. Feb 9, 12:00:01 GMT+0 - Identified - Maintenance is now in progress

Type: Maintenance Duration: 2 hours and 30 minutes Affected Components: Dallas, Chicago Feb 9, 13:29:43 GMT+0 - Completed - Maintenance has completed successfully. Feb 9, 11:00:00 GMT+0 - Identified - As mentioned in our notification email, we will be upgrading these servers running CloudLinux 7 to CloudLinux 8. The upgrade will take approximately 1 to 2 hours, and there will be intermittent downtime for websites and cPanel during the upgrade process. Feb 9, 11:00:01 GMT+0 - Identified - Maintenance is now in progress

Type: Maintenance Duration: 3 hours and 30 minutes Affected Components: New York, Jacksonville Feb 9, 10:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 9, 10:00:00 GMT+0 - Identified - As mentioned in our notification email, we will be upgrading these servers running CloudLinux 7 to CloudLinux 8. The upgrade will take approximately 1 to 2 hours, and there will be intermittent downtime for websites and cPanel during the upgrade process. Feb 9, 13:29:54 GMT+0 - Completed - Maintenance has completed successfully.

Type: Maintenance Duration: 3 hours and 12 minutes Affected Components: Coventry Feb 9, 00:12:10 GMT+0 - Completed - All but UK-S2 have been completed due to an issue with the ELevate script, this will be upgraded during the next run. Feb 8, 21:00:00 GMT+0 - Identified - As mentioned in our notification email, we will be upgrading these servers running CloudLinux 7 to CloudLinux 8. The upgrade will take approximately 1 to 2 hours, and there will be intermittent downtime for websites and cPanel during the upgrade process. Feb 8, 21:00:01 GMT+0 - Identified - Maintenance is now in progress

Type: Maintenance Duration: 10 days, 11 hours and 38 minutes Affected Components: Netherlands Feb 9, 00:11:37 GMT+0 - Completed - All but NL-S3 have been completed due to an issue with a repository mirror, NL-S3 will keep retrying and we're unfortunately unable to rollback at this stage. Feb 8, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 8, 20:00:00 GMT+0 - Identified - As mentioned in our notification email, we will be upgrading these servers running CloudLinux 7 to CloudLinux 8. The upgrade will take approximately 1 to 2 hours, and there will be intermittent downtime for websites and cPanel during the upgrade process.

Type: Maintenance Duration: 3 hours and 57 minutes Affected Components: Sydney, Singapore Feb 8, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 8, 22:56:44 GMT+0 - Completed - Maintenance has completed successfully. Feb 8, 19:00:00 GMT+0 - Identified - As mentioned in our notification email, we will be upgrading these servers running CloudLinux 7 to CloudLinux 8. The upgrade will take approximately 1 to 2 hours, and there will be intermittent downtime for websites and cPanel during the upgrade process.

Type: Incident Duration: 5 hours and 29 minutes Affected Components: Los Angeles Jan 23, 11:55:48 GMT+0 - Investigating - Our network provider in Los Angeles has indicated that they are performing an "Emergency Maintenance" which is causing an outage. More details will be shared shortly. Jan 23, 12:44:18 GMT+0 - Monitoring - The network has come back online, but we are still waiting for more information from our network provider on what caused this. We apologize for any inconvenience caused. Jan 23, 17:25:09 GMT+0 - Resolved - This was confirmed by our network provider to be caused by a routing issue with Cogent and the issue has now been resolved. Sorry again for any inconvenience caused, and please open a ticket if you'd like to receive compensation under our uptime guarantee.

Type: Incident Duration: 15 hours and 46 minutes Affected Components: Jacksonville Nov 19, 09:20:21 GMT+0 - Investigating - Our network provider in Jacksonville is currently experiencing an outage. They have been notified, we will post more updates as soon as we hear from them. Nov 19, 13:23:15 GMT+0 - Investigating - Apologies for the delay. Unfortunately, our provider experienced a delay in responding, which we are actively investigating. Network connectivity has now been restored, and we are currently awaiting confirmation regarding the root cause of the issue. Nov 20, 01:06:38 GMT+0 - Resolved - Our provider identified an error regarding MAC address programming on our network port, which caused it to drop. They resolved the issue by resetting the port on their end and will continue to monitor our BGP session to ensure it remains stable and prevent any recurrence. Thank you for your patience.