20i Outage History

Started Oct 22, 2026, 02:52 PM UTC· resolved Oct 22, 2026, 02:57 PM UTC

1. investigating Oct 22, 2026, 02:52 PM UTC

   We are aware of reports of some websites hosted on our London Shared Hosting platform returning 503 errors. Our System Administrators are currently investigating the issue to identify the cause and restore normal service.

2. investigating Oct 22, 2026, 02:57 PM UTC

   The intermittent 503 errors affecting some websites on our London Shared Hosting platform have now been resolved. Our System Administrators have confirmed that services have returned to normal.

Read the full incident report →

Started Oct 21, 2026, 02:24 PM UTC· resolved Oct 21, 2026, 08:01 PM UTC

1. investigating Oct 21, 2026, 02:24 PM UTC

   We are aware of the recently disclosed PHP security vulnerabilities, commonly referred to as PHP2Shell. As a precaution, we have already implemented additional security measures across our hosting platform. Our systems team is now working on deploying the latest PHP security patches across our hosting platform, including backporting the necessary fixes where required. We will continue to monitor the situation closely and provide a further update once the rollout is complete.

2. investigating Oct 21, 2026, 04:37 PM UTC

   Our system administration team have applied the upstream patches and have started to deploy the latest PHP Versions across our platforms.

3. investigating Oct 21, 2026, 05:30 PM UTC

   PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 are now available and the upstream security fixes have also been backported to all older PHP versions. The roll out to our hosting platform has completed. Cloud Servers are in progress.

4. investigating Oct 21, 2026, 06:51 PM UTC

   All Cloud Servers have now received PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The backported PHP versions are rolling out to cloud servers now.

5. investigating Oct 21, 2026, 08:01 PM UTC

   All Cloud Servers have now been successfully updated. This completes our deployment and all PHP versions across all platforms are now fully patched against the recently disclosed PHP vulnerabilities.

Read the full incident report →

Started Oct 19, 2026, 08:48 PM UTC· resolved Oct 19, 2026, 09:49 PM UTC

1. investigating Oct 19, 2026, 08:48 PM UTC

   We are receiving reports of intermittent connectivity to our hosting platform via the FRA1 CDN node. Our system administrators are investigating this matter, and we will provide further updates as soon as we have more information available.

2. monitoring Oct 19, 2026, 08:59 PM UTC

   Our system administrators have identified the cause of the connectivity issues seen, and normal service has been restored. We will continue to monitor FRA1 connectivity to ensure that this does not re-occur.

3. resolved Oct 19, 2026, 09:49 PM UTC

   Our system administrators have identified the cause of the connectivity issues seen, and normal service has been restored.

Read the full incident report →

Started Oct 11, 2026, 05:15 PM UTC· resolved Oct 11, 2026, 05:40 PM UTC

1. monitoring Oct 11, 2026, 05:15 PM UTC

   Incident: We're aware of issues with sending emails from our platform. Our System Administrators are currently investigating, and updates will be provided as we have more information available.

2. monitoring Oct 11, 2026, 05:15 PM UTC

   Incident: We're aware of issues with sending emails from our platform. Our System Administrators are currently investigating, and updates will be provided as we have more information available.

3. resolved Oct 11, 2026, 05:40 PM UTC

   Incident Update: Our system administrators have identified and resolved the email sending issues. Email sending functionality is fully restored.

4. resolved Oct 11, 2026, 05:40 PM UTC

   Incident Update: Our system administrators have identified and resolved the email sending issues. Email sending functionality is fully restored.

Read the full incident report →

Started Oct 08, 2026, 09:34 PM UTC· resolved Oct 08, 2026, 09:34 PM UTC

1. resolved Oct 08, 2026, 09:34 PM UTC

   Incident Update: Connectivity with the affected upstream provider has been resolved, and full network redundancy has now been restored.

2. resolved Oct 08, 2026, 09:34 PM UTC

   Incident Update: Connectivity with the affected upstream provider has been resolved, and full network redundancy has now been restored.

Read the full incident report →

Started Oct 07, 2026, 07:59 PM UTC· resolved Oct 09, 2026, 09:57 PM UTC

1. monitoring Oct 07, 2026, 07:59 PM UTC

   Incident: We are investigating intermittent connectivity in London, further updates will be provided shortly.

2. monitoring Oct 07, 2026, 07:59 PM UTC

   Incident: We are investigating intermittent connectivity in London, further updates will be provided shortly.

3. monitoring Oct 07, 2026, 10:31 PM UTC

   Incident Update: Earlier today, we experienced intermittent connectivity through one of our IP transit providers. We have temporarily removed this provider from our routing whilst we investigate the underlying cause. All services are currently stable but operating at reduced resiliency. We are continuing to monitor connectivity closely.

4. monitoring Oct 07, 2026, 10:31 PM UTC

   Incident Update: Earlier today, we experienced intermittent connectivity through one of our IP transit providers. We have temporarily removed this provider from our routing whilst we investigate the underlying cause. All services are currently stable but operating at reduced resiliency. We are continuing to monitor connectivity closely.

Read the full incident report →

Started Oct 07, 2026, 01:33 AM UTC· resolved Oct 07, 2026, 01:59 AM UTC

1. monitoring Oct 07, 2026, 01:33 AM UTC

   Incident: We're currently receiving reports of packages on the US shared hosting platform experiencing 502 errors. Our system administration team are investigating the issue now, and updates will be provided as more information becomes available. Apologies for any inconvenience caused.

2. monitoring Oct 07, 2026, 01:33 AM UTC

   Incident: We're currently receiving reports of packages on the US shared hosting platform experiencing 502 errors. Our system administration team are investigating the issue now, and updates will be provided as more information becomes available. Apologies for any inconvenience caused.

3. monitoring Oct 07, 2026, 01:59 AM UTC

   Incident Update: The issue with the intermittent 502 errors has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

4. monitoring Oct 07, 2026, 01:59 AM UTC

   Incident Update: The issue with the intermittent 502 errors has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

Read the full incident report →

Started Oct 01, 2026, 06:34 PM UTC· resolved Oct 01, 2026, 06:34 PM UTC

1. monitoring Oct 01, 2026, 06:27 PM UTC

   Incident: We are currently experiencing an issue with kvmhost31, which is causing VPS and Cloud Servers on this host to be unavailable. Our system administration team is actively investigating the problem and working to restore services as quickly as possible. We will provide further updates as soon as more information becomes available.

2. monitoring Oct 01, 2026, 06:27 PM UTC

   Incident: We are currently experiencing an issue with kvmhost31, which is causing VPS and Cloud Servers on this host to be unavailable. Our system administration team is actively investigating the problem and working to restore services as quickly as possible. We will provide further updates as soon as more information becomes available.

3. resolved Oct 01, 2026, 06:34 PM UTC

   Incident Update: We are pleased to inform you that all VPS and Cloud Servers on kvmhost31 have been successfully restored and are now fully operational. Our system administration team will continue to monitor the host closely to ensure stability and performance.

4. resolved Oct 01, 2026, 06:34 PM UTC

   Incident Update: We are pleased to inform you that all VPS and Cloud Servers on kvmhost31 have been successfully restored and are now fully operational. Our system administration team will continue to monitor the host closely to ensure stability and performance.

Read the full incident report →

Started Oct 01, 2026, 01:16 PM UTC· resolved Oct 01, 2026, 01:16 PM UTC

1. monitoring Oct 01, 2026, 12:56 PM UTC

   Incident: We’re aware of an issue causing intermittent connectivity to Webmail for some users. Our team is investigating and working to restore normal service as soon as possible. We’ll provide further updates as they become available.

2. monitoring Oct 01, 2026, 12:56 PM UTC

   Incident: We’re aware of an issue causing intermittent connectivity to Webmail for some users. Our team is investigating and working to restore normal service as soon as possible. We’ll provide further updates as they become available.

3. resolved Oct 01, 2026, 01:16 PM UTC

   Incident Update: The intermittent connectivity issues affecting Webmail have now been resolved. Webmail services are operating normally.

4. resolved Oct 01, 2026, 01:16 PM UTC

   Incident Update: The intermittent connectivity issues affecting Webmail have now been resolved. Webmail services are operating normally.

Read the full incident report →

Started Sep 16, 2026, 01:25 AM UTC· resolved Sep 16, 2026, 01:25 AM UTC

1. monitoring Sep 16, 2026, 01:01 AM UTC

   Incident: We're currently aware of intermittent database connectivity. This appears to be impacting the following database hosts: sdb-83, shareddb47, and shareddb48. Our System Administrators are currently investigating, and updates will be provided as we have more information available.

2. monitoring Sep 16, 2026, 01:01 AM UTC

   Incident: We're currently aware of intermittent database connectivity. This appears to be impacting the following database hosts: sdb-83, shareddb47, and shareddb48. Our System Administrators are currently investigating, and updates will be provided as we have more information available.

3. resolved Sep 16, 2026, 01:25 AM UTC

   Incident Update: Our system administrators have identified the cause of the connectivity issues seen and have deployed a fix to restore database connectivity.

4. resolved Sep 16, 2026, 01:25 AM UTC

   Incident Update: Our system administrators have identified the cause of the connectivity issues seen and have deployed a fix to restore database connectivity.

Read the full incident report →

Started Aug 22, 2026, 02:44 PM UTC· resolved Aug 24, 2026, 10:50 AM UTC

1. monitoring Aug 22, 2026, 10:46 AM UTC

   Incident: We are receiving reports of intermittent connectivity to our hosting platform, with some traffic seeing 502 Errors. Our system administrators are investigating this matter, and we will provide further updates as soon as we have more information available.

2. monitoring Aug 22, 2026, 10:52 AM UTC

   Incident: We are receiving reports of intermittent connectivity to our hosting platform via the FRA1 CDN Node, with some traffic seeing 502 Errors. Our system administrators are investigating this matter, and have taken mitigating action to prevent further issues, whilst we continue to investigate. We will provide further updates as soon as we have more information available.

3. monitoring Aug 22, 2026, 02:44 PM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

4. monitoring Aug 22, 2026, 02:44 PM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

Read the full incident report →

Started Aug 18, 2026, 02:15 PM UTC· resolved Aug 18, 2026, 02:15 PM UTC

1. monitoring Aug 18, 2026, 01:36 PM UTC

   Incident: We're currently aware of intermittent database connectivity. This appears to be impacting the following database host: wordpressdb-a. Our System Administrators are currently investigating, and updates will be provided as we have more information available.

2. monitoring Aug 18, 2026, 01:36 PM UTC

   Incident: We're currently aware of intermittent database connectivity. This appears to be impacting the following database host: wordpressdb-a. Our System Administrators are currently investigating, and updates will be provided as we have more information available.

3. resolved Aug 18, 2026, 02:15 PM UTC

   Incident Update: Our system administrators have identified the cause of the intermittent connectivity and have deployed a fix to restore database connectivity.

4. resolved Aug 18, 2026, 02:15 PM UTC

   Incident Update: Our system administrators have identified the cause of the intermittent connectivity and have deployed a fix to restore database connectivity.

Read the full incident report →

Started Aug 16, 2026, 05:09 AM UTC· resolved Aug 17, 2026, 05:52 AM UTC

1. monitoring Aug 16, 2026, 05:09 AM UTC

   Incident Update: All services at our Frankfurt location have remained stable overnight, with no further disruption observed. The facility operator has confirmed that cooling has now been fully restored across all affected areas, with temperatures remaining stable and within normal operating thresholds. Cooling redundancy has also been restored. We are therefore marking this incident as resolved. We have requested a full Root Cause Analysis (RFO) from the facility operator and will review this once available. We apologise for the disruption caused.

2. monitoring Aug 16, 2026, 05:09 AM UTC

   Incident Update: All services at our Frankfurt location have remained stable overnight, with no further disruption observed. The facility operator has confirmed that cooling has now been fully restored across all affected areas, with temperatures remaining stable and within normal operating thresholds. Cooling redundancy has also been restored. We are therefore marking this incident as resolved. We have requested a full Root Cause Analysis (RFO) from the facility operator and will review this once available. We apologise for the disruption caused.

Read the full incident report →

Started Aug 16, 2026, 05:09 AM UTC· resolved Aug 17, 2026, 05:52 AM UTC

1. monitoring Aug 15, 2026, 03:11 AM UTC

   Incident: Due to problems with cooling in the Franktfurt DC, kvmhosts are being temporarily shut down to protect hardware. Frankfurt based websites may be unavailable. This will affect sites hosted on kvmhost135, kvmhost136, and kvmhost137.

2. monitoring Aug 15, 2026, 03:11 AM UTC

   Incident: Due to problems with cooling in the Franktfurt DC, kvmhosts are being temporarily shut down to protect hardware. Frankfurt based websites may be unavailable. This will affect sites hosted on kvmhost135, kvmhost136, and kvmhost137.

Read the full incident report →

Started Aug 15, 2026, 07:21 PM UTC· resolved Aug 17, 2026, 05:52 AM UTC

1. monitoring Aug 15, 2026, 05:00 PM UTC

   Incident Update: Recovery work continues to progress at our Frankfurt location. Cloud Servers at this location remain unavailable, while CDN traffic continues to be rerouted to alternative locations. Three of the facility’s chillers have now been brought back online and temperatures within parts of the data centre have started to decrease. Temporary cooling equipment has also been deployed, with additional units being delivered to assist the recovery. Engineers continue to investigate the chilled-water system affecting other areas of the facility. Cooling will be restored incrementally as sections of the system are confirmed to be free from further leaks.

2. monitoring Aug 15, 2026, 05:00 PM UTC

   Incident Update: Recovery work continues to progress at our Frankfurt location. Cloud Servers at this location remain unavailable, while CDN traffic continues to be rerouted to alternative locations. Three of the facility’s chillers have now been brought back online and temperatures within parts of the data centre have started to decrease. Temporary cooling equipment has also been deployed, with additional units being delivered to assist the recovery. Engineers continue to investigate the chilled-water system affecting other areas of the facility. Cooling will be restored incrementally as sections of the system are confirmed to be free from further leaks.

3. monitoring Aug 15, 2026, 07:21 PM UTC

   Incident Update: Recovery work has made significant progress at our Frankfurt location. Cloud Servers at this location remain unavailable, while CDN traffic continues to be rerouted to alternative locations. The facility operator has confirmed that cooling has now been restored across the majority of the data centre, with temperatures returning to normal operational ranges. Additionally cooling redundancy has returned to normal operating levels. Our equipment remains powered down while we confirm that environmental conditions are suitable for it to be safely brought back online. We are closely monitoring the recovery and will provide a further update as progress is made.

4. monitoring Aug 15, 2026, 07:21 PM UTC

   Incident Update: Recovery work has made significant progress at our Frankfurt location. Cloud Servers at this location remain unavailable, while CDN traffic continues to be rerouted to alternative locations. The facility operator has confirmed that cooling has now been restored across the majority of the data centre, with temperatures returning to normal operational ranges. Additionally cooling redundancy has returned to normal operating levels. Our equipment remains powered down while we confirm that environmental conditions are suitable for it to be safely brought back online. We are closely monitoring the recovery and will provide a further update as progress is made.

5. monitoring Aug 15, 2026, 07:47 PM UTC

   Incident Update: We have begun restoring our network infrastructure at the Frankfurt location following the stabilisation of temperatures. Our engineers are bringing infrastructure back online in a controlled manner and monitoring systems closely as the recovery progresses. Cloud Servers at this location remain unavailable while this work is carried out, and CDN traffic continues to be rerouted to alternative locations. We will provide a further update as more of our infrastructure is restored and services begin to recover.œ

6. monitoring Aug 15, 2026, 07:47 PM UTC

   Incident Update: We have begun restoring our network infrastructure at the Frankfurt location following the stabilisation of temperatures. Our engineers are bringing infrastructure back online in a controlled manner and monitoring systems closely as the recovery progresses. Cloud Servers at this location remain unavailable while this work is carried out, and CDN traffic continues to be rerouted to alternative locations. We will provide a further update as more of our infrastructure is restored and services begin to recover.œ

7. monitoring Aug 15, 2026, 08:23 PM UTC

   Incident Update: All infrastructure at our Frankfurt location has now been restored and services are operating normally. Cloud Servers are back online and our network infrastructure has been fully restored. We are continuing to closely monitor the environment and our systems to ensure stability following the earlier cooling incident. We apologise for the disruption this incident has caused and would like to thank everyone affected for their patience and understanding while recovery work was carried out. We will be requesting a full Root Cause Analysis (RFO) from the facility operator to understand the circumstances surrounding the incident and the actions being taken to prevent a recurrence. We will continue monitoring before marking this incident as resolved.

8. monitoring Aug 15, 2026, 08:23 PM UTC

   Incident Update: All infrastructure at our Frankfurt location has now been restored and services are operating normally. Cloud Servers are back online and our network infrastructure has been fully restored. We are continuing to closely monitor the environment and our systems to ensure stability following the earlier cooling incident. We apologise for the disruption this incident has caused and would like to thank everyone affected for their patience and understanding while recovery work was carried out. We will be requesting a full Root Cause Analysis (RFO) from the facility operator to understand the circumstances surrounding the incident and the actions being taken to prevent a recurrence. We will continue monitoring before marking this incident as resolved.

Read the full incident report →

Started Aug 15, 2026, 11:22 AM UTC· resolved Aug 17, 2026, 05:52 AM UTC

1. monitoring Aug 15, 2026, 11:22 AM UTC

   Incident Update: The facility operator continues to make progress restoring cooling systems at our Frankfurt location. Cloud Servers at this location remain unavailable and CDN traffic continues to be rerouted to alternative locations. The original water leak has been repaired. During restoration work, a second leak was identified and has since been isolated while its cause is investigated. Refilling of the chilled-water system is progressing, with one buffer tank now full and the second currently being refilled. Specialist cooling engineers are onsite and, once the water systems have been refilled, the facility operator plans to restart and test each chiller individually before returning the cooling systems to service. Work to remove water and reduce humidity within affected areas is also continuing. We are closely monitoring recovery efforts and will provide a further update as progress is made.

2. monitoring Aug 15, 2026, 11:22 AM UTC

   Incident Update: The facility operator continues to make progress restoring cooling systems at our Frankfurt location. Cloud Servers at this location remain unavailable and CDN traffic continues to be rerouted to alternative locations. The original water leak has been repaired. During restoration work, a second leak was identified and has since been isolated while its cause is investigated. Refilling of the chilled-water system is progressing, with one buffer tank now full and the second currently being refilled. Specialist cooling engineers are onsite and, once the water systems have been refilled, the facility operator plans to restart and test each chiller individually before returning the cooling systems to service. Work to remove water and reduce humidity within affected areas is also continuing. We are closely monitoring recovery efforts and will provide a further update as progress is made.

Read the full incident report →

Started Aug 09, 2026, 08:02 AM UTC· resolved Aug 09, 2026, 08:02 AM UTC

1. monitoring Aug 09, 2026, 06:48 AM UTC

   Incident: We are receiving reports of intermittent connectivity to our hosting platform via the SIN1 CDN node. Our system administrators are investigating this matter, and we will provide further updates as soon as we have more information available.

2. monitoring Aug 09, 2026, 06:48 AM UTC

   Incident: We are receiving reports of intermittent connectivity to our hosting platform via the SIN1 CDN node. Our system administrators are investigating this matter, and we will provide further updates as soon as we have more information available.

3. monitoring Aug 09, 2026, 08:02 AM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

4. monitoring Aug 09, 2026, 08:02 AM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

Read the full incident report →

Started Aug 07, 2026, 01:30 AM UTC· resolved Aug 07, 2026, 01:30 AM UTC

1. monitoring Aug 07, 2026, 12:57 AM UTC

   Incident: We're currently receiving reports of some websites experiencing 503 errors. Our system administration team are investigating the issue now, and updates will be provided as more information becomes available. 1 Updates

2. monitoring Aug 07, 2026, 12:57 AM UTC

   Incident: We're currently receiving reports of some websites experiencing 503 errors. Our system administration team are investigating the issue now, and updates will be provided as more information becomes available. 1 Updates

3. monitoring Aug 07, 2026, 01:30 AM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

4. monitoring Aug 07, 2026, 01:30 AM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

Read the full incident report →

Started Aug 03, 2026, 12:53 AM UTC· resolved Aug 04, 2026, 10:34 AM UTC

1. monitoring Aug 02, 2026, 04:18 PM UTC

   Incident Update: The issues regarding intermittent 503 errors on some websites have now been fixed. The issue originated from an upstream network transit provider and has now been resolved.

2. monitoring Aug 02, 2026, 04:18 PM UTC

   Incident Update: The issues regarding intermittent 503 errors on some websites have now been fixed. The issue originated from an upstream network transit provider and has now been resolved.

Read the full incident report →

Started Aug 02, 2026, 04:18 PM UTC· resolved Aug 04, 2026, 10:34 AM UTC

1. monitoring Aug 02, 2026, 01:38 PM UTC

   Incident: We're currently receiving reports of some websites experiencing 503 errors. Our system administration team are investigating the issue now, and updates will be provided as more information becomes available.

2. monitoring Aug 02, 2026, 01:38 PM UTC

   Incident: We're currently receiving reports of some websites experiencing 503 errors. Our system administration team are investigating the issue now, and updates will be provided as more information becomes available.

Read the full incident report →

Started Jul 22, 2026, 01:00 PM UTC· resolved Jul 22, 2026, 01:00 PM UTC

1. monitoring Jul 22, 2026, 11:58 AM UTC

   Incident: We are aware of potential performance degradation on a number of websites using our shared hosting platform in London. Our team are investigating, and we will provide another update as soon as possible.

2. monitoring Jul 22, 2026, 11:58 AM UTC

   Incident: We are aware of potential performance degradation on a number of websites using our shared hosting platform in London. Our team are investigating, and we will provide another update as soon as possible.

3. resolved Jul 22, 2026, 01:00 PM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

4. resolved Jul 22, 2026, 01:00 PM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

Read the full incident report →

Started Jul 21, 2026, 03:48 PM UTC· resolved Jul 21, 2026, 03:48 PM UTC

1. monitoring Jul 21, 2026, 12:00 PM UTC

   Incident: We are currently aware of some reports of slow websites using storage "40b" on our shared hosting platform. Our team are investigating, and we will provide another update as soon as possible.

2. monitoring Jul 21, 2026, 12:02 PM UTC

   Incident: We are currently aware of some reports of slow websites using storage "40a" and "40b" on our shared hosting platform. Our team are investigating, and we will provide another update as soon as possible.

3. resolved Jul 21, 2026, 03:48 PM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

4. resolved Jul 21, 2026, 03:48 PM UTC

   Incident Update: The issue has now been resolved, and normal service has been restored. We will continue to monitor closely to ensure services remain stable.

Read the full incident report →

Started Jul 21, 2026, 08:32 AM UTC· resolved Jul 21, 2026, 12:02 PM UTC

1. monitoring Jul 21, 2026, 08:30 AM UTC

   Incident: We're currently aware of intermittent database connectivity. Our System Administrators are currently investigating, and updates will be provided as we have more information available.

2. monitoring Jul 21, 2026, 08:32 AM UTC

   Incident Update: We're receiving further reports of intermittent database connectivity. This appears to be impacting the following database hosts: sdb-63.hosting.stackcp.net sdb-64.hosting.stackcp.net sdb-65.hosting.stackcp.net, sdb-66.hosting.stackcp.net wpdb-31.hosting.stackcp.net wpdb-32.hosting.stackcp.net. Our System Administrators are currently investigating, and updates will be provided as we have more information available

3. monitoring Jul 21, 2026, 08:32 AM UTC

   Incident Update: We're receiving further reports of intermittent database connectivity. This appears to be impacting the following database hosts: sdb-63.hosting.stackcp.net sdb-64.hosting.stackcp.net sdb-65.hosting.stackcp.net, sdb-66.hosting.stackcp.net wpdb-31.hosting.stackcp.net wpdb-32.hosting.stackcp.net. Our System Administrators are currently investigating, and updates will be provided as we have more information available

4. monitoring Jul 21, 2026, 08:33 AM UTC

   Incident: We're currently aware of intermittent database connectivity. Our System Administrators are currently investigating, and updates will be provided as we have more information available.

5. monitoring Jul 21, 2026, 09:13 AM UTC

   Incident Update: Shared database connectivity affecting sdb-63.hosting.stackcp.net, sdb-64.hosting.stackcp.net, sdb-65.hosting.stackcp.net, sdb-66.hosting.stackcp.net, wpdb-31.hosting.stackcp.net & wpdb-32.hosting.stackcp.net have now been resolved. Our System Administrators have identified the cause of the database connectivity issue and are now monitoring the situation.

6. monitoring Jul 21, 2026, 09:16 AM UTC

   Incident Update: Shared database connectivity affecting sdb-63.hosting.stackcp.net, sdb-64.hosting.stackcp.net, sdb-65.hosting.stackcp.net, sdb-66.hosting.stackcp.net, wpdb-31.hosting.stackcp.net & wpdb-32.hosting.stackcp.net have now been resolved. Our System Administrators have identified the cause of the database connectivity drop and are now monitoring the situation.

7. resolved Jul 21, 2026, 12:02 PM UTC

   Incident Update: Our system administrators have identified the cause of the connectivity issues seen and have deployed a fix to restore database connectivity.

8. resolved Jul 21, 2026, 12:02 PM UTC

   Incident Update: Our system administrators have identified the cause of the connectivity issues seen and have deployed a fix to restore database connectivity.

Read the full incident report →

Started Jul 19, 2026, 04:57 AM UTC· resolved Jul 19, 2026, 04:57 AM UTC

1. monitoring Jul 19, 2026, 02:17 AM UTC

   Incident: We are currently experiencing an issue with kvmhost31, which is causing VPS and Cloud Servers on this host to be unavailable. Our system administration team is actively investigating the problem and working to restore services as quickly as possible. We will provide further updates as soon as more information becomes available.

2. monitoring Jul 19, 2026, 02:17 AM UTC

   Incident: We are currently experiencing an issue with kvmhost31, which is causing VPS and Cloud Servers on this host to be unavailable. Our system administration team is actively investigating the problem and working to restore services as quickly as possible. We will provide further updates as soon as more information becomes available.

3. resolved Jul 19, 2026, 04:57 AM UTC

   Incident Update: We are pleased to inform you that all VPS and Cloud Servers on kvmhost24 have been successfully restored and are now fully operational. Our system administration team will continue to monitor the host closely to ensure stability and performance.

4. resolved Jul 19, 2026, 04:57 AM UTC

   Incident Update: We are pleased to inform you that all VPS and Cloud Servers on kvmhost24 have been successfully restored and are now fully operational. Our system administration team will continue to monitor the host closely to ensure stability and performance.

Read the full incident report →

Started Jul 10, 2026, 06:59 PM UTC· resolved Jul 10, 2026, 06:59 PM UTC

1. monitoring Jul 08, 2026, 04:58 PM UTC

   Incident: SSH is currently unavailable on our hosting platforms across our UK, US, and Singapore locations. Our engineers are working to restore SSH access as quickly as possible. We will provide further updates as more information becomes available.

2. monitoring Jul 08, 2026, 04:58 PM UTC

   Incident: SSH is currently unavailable on our hosting platforms across our UK, US, and Singapore locations. Our engineers are working to restore SSH access as quickly as possible. We will provide further updates as more information becomes available.

3. resolved Jul 10, 2026, 06:59 PM UTC

   Incident Update: We're pleased to confirm that SSH connectivity has now been fully restored across our UK, US, and Singapore hosting platforms. Our system administrators have completed the necessary work, and SSH access is once again available.

4. resolved Jul 10, 2026, 06:59 PM UTC

   Incident Update: We're pleased to confirm that SSH connectivity has now been fully restored across our UK, US, and Singapore hosting platforms. Our system administrators have completed the necessary work, and SSH access is once again available.

Read the full incident report →