20i Outage History

20i is up right now

20i had 40 outages in the last 2 years totaling 319h 48m of downtime — averaging 1.6 incidents per month.

There were 40 20i outages since April 27, 2026 totaling 319h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://stackstatus.com

Minor October 11, 2026

Email Sending Issues

Detected by Pingoru
Oct 11, 2026, 05:15 PM UTC
Resolved
Oct 11, 2026, 05:40 PM UTC
Duration
25m
Timeline · 4 updates
  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 →

Minor October 8, 2026

Network Connectivity - Resolved

Detected by Pingoru
Oct 08, 2026, 09:34 PM UTC
Resolved
Oct 08, 2026, 09:34 PM UTC
Duration
—
Timeline · 2 updates
  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 →

Minor October 7, 2026

Network Connectivity - London, UK

Detected by Pingoru
Oct 07, 2026, 07:59 PM UTC
Resolved
Oct 09, 2026, 09:57 PM UTC
Duration
2d 1h
Timeline · 4 updates
  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 →

Minor October 7, 2026

US Shared Platform Issues

Detected by Pingoru
Oct 07, 2026, 01:33 AM UTC
Resolved
Oct 07, 2026, 01:59 AM UTC
Duration
26m
Timeline · 4 updates
  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 →

Minor October 1, 2026

VPS/Cloud Server Unavailable - kvmhost31

Detected by Pingoru
Oct 01, 2026, 06:34 PM UTC
Resolved
Oct 01, 2026, 06:34 PM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor October 1, 2026

Webmail Intermittent Connectivity

Detected by Pingoru
Oct 01, 2026, 01:16 PM UTC
Resolved
Oct 01, 2026, 01:16 PM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor September 22, 2026

FRA1 Connectivity Issues

Detected by Pingoru
Sep 22, 2026, 03:07 PM UTC
Resolved
Sep 22, 2026, 03:07 PM UTC
Duration
—
Timeline · 4 updates
  1. monitoring Sep 22, 2026, 02:56 PM UTC

    Incident: 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 Sep 22, 2026, 02:56 PM UTC

    Incident: 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.

  3. monitoring Sep 22, 2026, 03:07 PM UTC

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

  4. monitoring Sep 22, 2026, 03:07 PM UTC

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

Read the full incident report →

Minor September 16, 2026

Database Connectivity Issues

Detected by Pingoru
Sep 16, 2026, 01:25 AM UTC
Resolved
Sep 16, 2026, 01:25 AM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor August 22, 2026

Intermittent 502 Errors

Detected by Pingoru
Aug 22, 2026, 02:44 PM UTC
Resolved
Aug 24, 2026, 10:50 AM UTC
Duration
1d 20h
Timeline · 4 updates
  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 →

Minor August 18, 2026

Intermittent Database Connectivity

Detected by Pingoru
Aug 18, 2026, 02:15 PM UTC
Resolved
Aug 18, 2026, 02:15 PM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor August 16, 2026

Cooling Incident - Frankfurt - Final Update

Detected by Pingoru
Aug 16, 2026, 05:09 AM UTC
Resolved
Aug 17, 2026, 05:52 AM UTC
Duration
1d
Timeline · 2 updates
  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 →

Minor August 16, 2026

Cooling Incident – Frankfurt Data Centre

Detected by Pingoru
Aug 16, 2026, 05:09 AM UTC
Resolved
Aug 17, 2026, 05:52 AM UTC
Duration
1d
Timeline · 2 updates
  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 →

Minor August 15, 2026

Cooling Incident - Frankfurt - Update

Detected by Pingoru
Aug 15, 2026, 11:22 AM UTC
Resolved
Aug 17, 2026, 05:52 AM UTC
Duration
1d 18h
Timeline · 2 updates
  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 →

Minor August 9, 2026

SIN1 Connectivity Issues

Detected by Pingoru
Aug 09, 2026, 08:02 AM UTC
Resolved
Aug 09, 2026, 08:02 AM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor August 7, 2026

503 Errors/Service Unavailable Errors

Detected by Pingoru
Aug 07, 2026, 01:30 AM UTC
Resolved
Aug 07, 2026, 01:30 AM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor August 3, 2026

503 Errors - Fixed

Detected by Pingoru
Aug 03, 2026, 12:53 AM UTC
Resolved
Aug 04, 2026, 10:34 AM UTC
Duration
1d 9h
Timeline · 2 updates
  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 →

Minor August 2, 2026

503 Errors

Detected by Pingoru
Aug 02, 2026, 04:18 PM UTC
Resolved
Aug 04, 2026, 10:34 AM UTC
Duration
1d 18h
Timeline · 2 updates
  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 →

Minor July 22, 2026

Shared Hosting - Website Performance

Detected by Pingoru
Jul 22, 2026, 01:00 PM UTC
Resolved
Jul 22, 2026, 01:00 PM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor July 21, 2026

Website Performance - 40a/40b Storage

Detected by Pingoru
Jul 21, 2026, 03:48 PM UTC
Resolved
Jul 21, 2026, 03:48 PM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor July 21, 2026

Shared Database Connectivity

Detected by Pingoru
Jul 21, 2026, 08:32 AM UTC
Resolved
Jul 21, 2026, 12:02 PM UTC
Duration
3h 29m
Timeline · 8 updates
  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 →

Minor July 19, 2026

VPS/Cloud Server Unavailable - kvmhost24

Detected by Pingoru
Jul 19, 2026, 04:57 AM UTC
Resolved
Jul 19, 2026, 04:57 AM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor July 10, 2026

SSH Connectivity

Detected by Pingoru
Jul 10, 2026, 06:59 PM UTC
Resolved
Jul 10, 2026, 06:59 PM UTC
Duration
—
Timeline · 4 updates
  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 →

Minor July 7, 2026

Core Network Upgrades (Dallas, US)

Detected by Pingoru
Jul 07, 2026, 10:00 PM UTC
Resolved
Jul 08, 2026, 04:58 PM UTC
Duration
18h 58m
Timeline · 2 updates
  1. monitoring Jul 04, 2026, 09:07 PM UTC

    Scheduled Maintenance: We are carrying out essential core network upgrades to our Dallas, United States (DFW) infrastructure. As part of this work, we will be increasing network capacity to support future growth and improve overall platform resilience. No service interruption is expected during the maintenance window. However, due to the nature of the work being carried out, services should be considered "at risk" throughout the scheduled period. Scheduled for: 2026-07-04 22:00:00 To be completed: 2026-07-07 22:00:00

  2. monitoring Jul 04, 2026, 09:07 PM UTC

    Scheduled Maintenance: We are carrying out essential core network upgrades to our Dallas, United States (DFW) infrastructure. As part of this work, we will be increasing network capacity to support future growth and improve overall platform resilience. No service interruption is expected during the maintenance window. However, due to the nature of the work being carried out, services should be considered "at risk" throughout the scheduled period. Scheduled for: 2026-07-04 22:00:00 To be completed: 2026-07-07 22:00:00

Read the full incident report →

Minor June 29, 2026

Control Panel Performance

Detected by Pingoru
Jun 29, 2026, 07:37 AM UTC
Resolved
Jun 29, 2026, 07:37 AM UTC
Duration
—
Timeline · 4 updates
  1. monitoring Jun 29, 2026, 07:33 AM UTC

    Incident: We're currently receiving reports of degraded performance via the hosting control panel. Our system admin team are investigating, and we will provide an update as soon as possible.

  2. monitoring Jun 29, 2026, 07:37 AM UTC

    Incident: We're currently receiving reports of degraded performance via the hosting control panel. Our system admin team are investigating, and we will provide an update as soon as possible.

  3. resolved Jun 29, 2026, 07:37 AM UTC

    Incident Update: This incident has now been resolved.

  4. resolved Jun 29, 2026, 07:37 AM UTC

    Incident Update: This incident has now been resolved.

Read the full incident report →