nine Outage History

nine is up right now

Pingoru has recorded 34 incidents for nine: 34 in the last 12 months and 15 in the last 90 days.

Source: status.nine.ch

34incidents recorded
34last 12 months
15last 90 days
3 daystypical duration
Incidents per month
036AprMayJunJulAugSepOctNov1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking nine in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026656 of 720 (8%)
May 202600 of 744 (0%)
June 20261103 of 720 (14%)
July 20264176 of 744 (24%)
August 20264174 of 744 (23%)
September 2026534 of 720 (5%)
October 20265116 of 744 (16%)
November 202610 of 141 (0%)

Incidents, newest first

Major November 4, 2026 Crash cz41 managed router 17m Network

Started Nov 04, 2026, 07:18 AM UTC· resolved Nov 04, 2026, 07:35 AM UTC

  1. resolved Nov 04, 2026, 07:58 AM UTC

    The software on one of the CZ41 managed routers crashed. The device restarted by itself and came back up cleanly. This may have led to short network outages during the rerouting. We are monitoring the situation. Please accept our apologies for this.

Read the full incident report →

Major October 31, 2026 Crash router managed CZ42 (cz42-m19-m-r2) 12m Virtualization, Managed Kubernetes, Network

Started Oct 31, 2026, 02:58 AM UTC· resolved Oct 31, 2026, 03:11 AM UTC

  1. identified Oct 31, 2026, 02:58 AM UTC

    The second router (cz42-m19-m-r2) in the managed segment in CZ42 crashed. Due to this, traffic trying to flow via this router was not forwarded. We had to reboot the affected router, and we are now monitoring the situation and waiting until it recovers.

  2. resolved Oct 31, 2026, 03:11 AM UTC

    After a controlled reboot, the situation has been stable again for a few minutes. Thank you for your patience.

Read the full incident report →

Major October 21, 2026 PHP CVE-2026-109618 & CVE-2026-109619 4d 18h General, Deploio

Started Oct 21, 2026, 03:14 PM UTC· resolved Oct 26, 2026, 10:11 AM UTC

  1. identified Oct 21, 2026, 03:14 PM UTC

    On 21 October 2026, the PHP project published security updates for two critical vulnerabilities in PHP (CVE-2026-109618 and CVE-2026-109619). They can allow remote code execution. Affected for you: PHP on servers managed by us (Managed OS) and PHP apps on Deploio (PHP buildpack and Dockerfile). What we are doing: our engineers are reviewing the updates and will apply them for the systems we manage already. For Deploio, we depend on the updated buildpack and upstream images which are currently being released. If your Dockerfile uses a floating base image tag (e.g. `latest`), a rebuild will pick up the patched PHP version once a fixed image is available upstream. Customers with self-managed PHP installations or a pinned PHP version in their Dockerfile need to update themselves. The current patch status per OS and PHP version is tracked here and updated continuously: [Link to Progress](https://docs.google.com/spreadsheets/d/1IO_mtDMKx8_ZHlfNBn_Org5TVUQD0MdDW07UByNnt8c/) Recommended action if you are uncertain If you are unsure whether your application is affected, we recommend taking it out of service until the fixed PHP version is in place: show a static maintenance page instead of your application. The page must not run PHP, otherwise requests still reach PHP. - Deploio: deploy a static maintenance page, or scale your app to 0 replicas. - Managed servers: serve a static maintenance page for the affected virtual host. Once your PHP has been updated (see linke doc) you can bring your application back online. We will post the next update here as soon as there is progress.

  2. identified Oct 21, 2026, 09:43 PM UTC

    PHP on servers managed by us (Managed OS) are now up to date. [Link to Progress](https://docs.google.com/spreadsheets/d/1IO_mtDMKx8_ZHlfNBn_Org5TVUQD0MdDW07UByNnt8c/)

  3. monitoring Oct 22, 2026, 07:02 AM UTC

    All managed systems with patchable PHP versions have been patched. The patched combinations of managed systems are listed in the status document: [Link to Overview](https://docs.google.com/spreadsheets/d/1IO_mtDMKx8_ZHlfNBn_Org5TVUQD0MdDW07UByNnt8c/) Deploio: PHP buildpacks Apps using the PHP buildpacks have been updated as well. Deploio: Dockerfile We recommend triggering a rebuild as soon as possible to pick up the fixed PHP version. If you don't, we will trigger a rebuild ourselves at a later point. Note that a rebuild can lead to a new release of your application. If you pin a specific PHP version in your Dockerfile, please adjust it to a fixed version: 8.5.12, 8.4.27, 8.3.36 or 8.2.35.

  4. monitoring Oct 22, 2026, 08:01 AM UTC

    Deploio: Dockerfile We have started triggering rebuilds of Dockerfile applications to pick up the fixed PHP version. A rebuild can lead to a new release of your application. Depending on your setup, apps running fewer than 2 replicas may experience a short service interruption during the rollout. If you want to avoid this, run at least 2 replicas.

  5. investigating Oct 22, 2026, 11:51 AM UTC

    Dockerfile Deploio: All Dockerfile apps on Deploio have been triggered for a rebuild. Please check that your application still works as intended. The rebuild only fixes the CVE if your Dockerfile references the "latest" tag. If you pin a specific PHP version, please adjust it to a fixed version: 8.5.12, 8.4.27, 8.3.36 or 8.2.35.

  6. resolved Oct 26, 2026, 10:11 AM UTC

    All systems whose PHP versions received patches have been patched for CVE-2026-109618 and CVE-2026-109619. All PHP buildpacks have been patched, and a new build has been triggered for all Deploio apps. Please check that your application still works as intended after the rebuild. If you use a Dockerfile, the rebuild only fixes the CVE if it references the "latest" tag. If you pin a specific PHP version, please adjust it to a fixed version (8.5.12, 8.4.27, 8.3.36 or 8.2.35). Customers running versions that cannot be patched have been contacted directly.

Read the full incident report →

Major October 9, 2026 Intermittent Network Connectivity Issues CZ41 / Root 15m Network

Started Oct 09, 2026, 06:33 AM UTC· resolved Oct 09, 2026, 06:48 AM UTC

  1. identified Oct 09, 2026, 06:33 AM UTC

    We are currently experiencing a network incident that may cause connectivity issues and affect the availability of our services. Reason is an unexpected router restart triggered a failover, leading to intermittent availability.

  2. resolved Oct 09, 2026, 06:48 AM UTC

    All systems are up and running again.

Read the full incident report →

Major October 2, 2026 Intermittent Network Connectivity Issues ES34 / Colocation 12m Network

Started Oct 02, 2026, 08:22 AM UTC· resolved Oct 02, 2026, 08:35 AM UTC

  1. investigating Oct 02, 2026, 08:22 AM UTC

    We are currently experiencing a network incident that may cause connectivity issues and affect the availability of our services. Reason is an unexpected router restart triggered a failover, leading to intermittent availability. Services are recovering and we're validating that everything is back to normal. Affected is location NTT / ES34 for the segment Colocation.

  2. resolved Oct 02, 2026, 08:35 AM UTC

    All systems are up and running again.

Read the full incident report →

Major October 1, 2026 Intermittent Network Connectivity Issues 46m Managed Kubernetes, Network

Started Oct 01, 2026, 06:17 PM UTC· resolved Oct 01, 2026, 07:03 PM UTC

  1. investigating Oct 01, 2026, 06:32 PM UTC

    We are currently experiencing a network incident that may cause connectivity issues and affect the availability of our services. Our team is looking into it, and we will provide an update as soon as we know more. Thank you for your patience.

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

    We've identified the cause: an unexpected router restart triggered a failover, leading to intermittent availability. Services are recovering and we're validating that everything is back to normal. We'll confirm once fully resolved.

  3. resolved Oct 01, 2026, 07:03 PM UTC

    This incident is resolved. We no longer see any impact and all services are operating normally. Thanks for your patience.

Read the full incident report →

Major September 22, 2026 NKE: ControlPlane Issues 11h 42m Managed Kubernetes

Started Sep 22, 2026, 02:19 AM UTC· resolved Sep 22, 2026, 02:01 PM UTC

  1. investigating Sep 22, 2026, 02:19 AM UTC

    Due to some unforseen errors in the maintenance window, NKE Control clusters might not be reachable. If you are affected, you cannot log into your cluster, see the status of your cluster or schedule new workloads. However, existing workloads are still reachable. We are working on a fix.

  2. investigating Sep 22, 2026, 03:43 AM UTC

    New Worker nodes cannot be spawned currently we are still working the fix

  3. investigating Sep 22, 2026, 06:29 AM UTC

    The core issues have been identified, we are expecting all services to recover fully right now.

  4. resolved Sep 22, 2026, 02:01 PM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major September 15, 2026 Outage affecting deplo.io applications and NKE services 13h 5m

Started Sep 15, 2026, 07:23 PM UTC· resolved Sep 16, 2026, 08:29 AM UTC

  1. investigating Sep 15, 2026, 07:23 PM UTC

    Following the unexpected router reboot in one of our data centers, deplo.io applications and Managed Kubernetes (NKE) services are currently experiencing an outage. The cause has been identified and the systems are recovering. Availability is still impacted, applications and services may be unreachable or only intermittently reachable while recovery continues. No action is required on your side. We will post another update as soon as the situation changes. Thank you for your patience.

  2. investigating Sep 15, 2026, 09:47 PM UTC

    deplo.io applications and Managed Kubernetes (NKE) services are operating normally again. The unexpected router reboot left some ARP entries in a state we did not anticipate. Connectivity appeared healthy on every check we ran, which delayed identification of the network layer as the cause. The affected entries have been corrected and services have been stable since. We will investigate the underlying behaviour further to make sure a router failover cannot lead to this again. We apologize for the extended disruption and thank you for your patience.

  3. resolved Sep 16, 2026, 08:29 AM UTC

    We are confident that all issues have been resolved and therefore are closing the status.

Read the full incident report →

Major September 15, 2026 Network Router reboot 16h 13m

Started Sep 15, 2026, 05:38 PM UTC· resolved Sep 16, 2026, 09:51 AM UTC

  1. investigating Sep 15, 2026, 05:38 PM UTC

    One of our redundant routers in one of our data centers has had an issue and has been rebooted. The system has failed over to the redundant systems, recovery is underway.

  2. investigating Sep 15, 2026, 06:20 PM UTC

    We still see NKE nodes recovering from this incident.

  3. resolved Sep 16, 2026, 09:51 AM UTC

    We are confident that all issues have been resolved and therefore resolving this status.

Read the full incident report →

Major September 11, 2026 Outtage for CName apps 22m

Started Sep 11, 2026, 12:40 PM UTC· resolved Sep 11, 2026, 01:02 PM UTC

  1. investigating Sep 11, 2026, 12:40 PM UTC

    We are investigating the issue and will get back to you asap.

  2. resolved Sep 11, 2026, 01:02 PM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major September 7, 2026 Investigating availability issue for Root VServer on nvirt108 - CZ42 5h 18m

Started Sep 07, 2026, 05:36 AM UTC· resolved Sep 07, 2026, 10:54 AM UTC

  1. investigating Sep 07, 2026, 06:10 AM UTC

    The virtualization node nvirt108 (Colozueri.ch 4.2) is back online and all affected Root VServers are running again. We are currently monitoring the systems to ensure that everything remains stable Thank you for your patience.

  2. resolved Sep 07, 2026, 10:54 AM UTC

    The issue has been resolved. Since our last update, all affected Root VServers have been running continuously without any further interruption. We have migrated the Root VServers to another virtualization host without causing any additional downtime. We apologize for the disruption and thank you for your patience and understanding.

Read the full incident report →

Major August 20, 2026 Investigating network connectivity issues 35m

Started Aug 20, 2026, 10:21 AM UTC· resolved Aug 20, 2026, 10:56 AM UTC

  1. investigating Aug 20, 2026, 10:21 AM UTC

    We are currently investigating network-related issues that may cause intermittent availability of some services. Our team is looking into it, and we will provide an update as soon as we know more. Thank you for your patience.

  2. investigating Aug 20, 2026, 10:39 AM UTC

    We've identified the cause: an unexpected router restart triggered a failover, leading to intermittent availability. Services are recovering and we're validating that everything is back to normal. We'll confirm once fully resolved.

  3. resolved Aug 20, 2026, 10:56 AM UTC

    This incident is resolved. An unexpected router restart triggered a failover, causing intermittent availability. We no longer see any impact and all services are operating normally.

Read the full incident report →

Major August 12, 2026 Intermittent Network Connectivity Issues 7d 4h

Started Aug 12, 2026, 05:32 AM UTC· resolved Aug 19, 2026, 09:39 AM UTC

  1. investigating Aug 13, 2026, 10:51 AM UTC

    All customer applications and services are reachable and operating normally. Cockpit and Ticketing System may still show temporary limitations until fully recovered. We continue to monitor the situation closely and will provide further update accordingly. Thank you for your patience, and we apologize for any inconvenience caused.

  2. resolved Aug 19, 2026, 09:39 AM UTC

    The issue has been resolved and our network is operating normally. Traffic levels have been stable for a sustained period. We are continuing to monitor the network and are prepared to act immediately if the situation changes. We apologize for any inconvenience caused. Thank you for your patience during the disruption.

Read the full incident report →

Major August 11, 2026 Intermittent Network Connectivity Issues 31m

Started Aug 11, 2026, 08:41 PM UTC· resolved Aug 11, 2026, 09:12 PM UTC

  1. resolved Aug 11, 2026, 09:12 PM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major August 11, 2026 Network Connectivity Issues 1h 7m

Started Aug 11, 2026, 05:58 PM UTC· resolved Aug 11, 2026, 07:06 PM UTC

  1. resolved Aug 11, 2026, 07:06 PM UTC

    The issue has been resolved and our network is operating normally. Traffic levels have been stable for a sustained period. We are continuing to monitor the network and are prepared to act immediately if the situation changes. Thank you for your patience during the disruption.

Read the full incident report →

Major July 28, 2026 [NKE] new nodes are having issues being spawened 1h 8m

Started Jul 28, 2026, 08:08 AM UTC· resolved Jul 28, 2026, 09:16 AM UTC

  1. investigating Jul 28, 2026, 08:08 AM UTC

    New nodes currently cannot be spawned. Existing nodes are working. Autoscaling nodes, manual scaling nodes and new cluster nodes cannot be created right now.

  2. resolved Jul 28, 2026, 09:16 AM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major July 27, 2026 [Self-Service] New IP address / Static Egress reservations are stuck and not being provisioned. 3h 6m

Started Jul 27, 2026, 01:27 PM UTC· resolved Jul 27, 2026, 04:34 PM UTC

  1. investigating Jul 27, 2026, 01:28 PM UTC

    We've confirmed there is a problem, we're working to resolve it.

  2. investigating Jul 27, 2026, 04:33 PM UTC

    We've fixed the core issue, and are waiting for things to recover.

  3. resolved Jul 27, 2026, 04:34 PM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major July 15, 2026 [S3] Location es34 connection issues 7d

Started Jul 15, 2026, 11:59 AM UTC· resolved Jul 22, 2026, 12:35 PM UTC

  1. investigating Jul 15, 2026, 05:03 PM UTC

    Further investigation revealed an additional potential cause. We will apply a fix and closely monitor the situation. Once the systems remain stable over the next 24 hours, we will mark this incident as resolved.

  2. investigating Jul 17, 2026, 10:58 AM UTC

    Service availability has recovered. However, we are observing higher latency than usual. The incident remains open while we work with the vendor to identify the cause, and we will update once we know more.

  3. resolved Jul 22, 2026, 12:35 PM UTC

    Since our last update on 17. July 2026, the service has remained stable with no further issues regarding latency or availability. The systems have been running without anomalies for several days. We are therefore marking this incident as resolved. If you have any questions, please don't hesitate to reach out to us at [email protected].

Read the full incident report →

Major July 13, 2026 [S3 Buckets] Some custom host buckets certificates are stuck in "Pending" 3h 22m

Started Jul 13, 2026, 02:39 PM UTC· resolved Jul 13, 2026, 06:02 PM UTC

  1. investigating Jul 13, 2026, 02:39 PM UTC

    Custom host buckets might show a fake TLS cert. We identified a bug in the certificate provisioning and are working on a fix.

  2. investigating Jul 13, 2026, 05:59 PM UTC

    We've fixed the core issue, and are waiting for things to recover.

  3. resolved Jul 13, 2026, 06:02 PM UTC

    We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major June 5, 2026 Issues with provisioning in location nine-es34 4d 7h

Started Jun 05, 2026, 07:50 AM UTC· resolved Jun 09, 2026, 02:54 PM UTC

  1. investigating Jun 05, 2026, 07:50 AM UTC

    We will let you know with asap

  2. investigating Jun 05, 2026, 12:04 PM UTC

    We have added more resources to our nine-cz42 location. NKE clusters can now be created there via Cockpit.

  3. resolved Jun 09, 2026, 02:54 PM UTC

    We've now resolved the incident. Thanks for your patience. nine-es34 remains closed for new CloudVMs, KubernetesClusters and MySQL&Postgres Databases. Those resources can be created in nine-cz42. Existing resource will continue to work as expected. See the docs for a detailed view here: https://docs.nine.ch/docs/general/datacenter-locations/

Read the full incident report →

Major April 28, 2026 Build Issues on Deploio 7m

Started Apr 28, 2026, 08:05 AM UTC· resolved Apr 28, 2026, 08:13 AM UTC

  1. investigating Apr 28, 2026, 08:05 AM UTC

    We have identified an issue affecting new build generation for Deploio Apps and are currently investigating the root cause. At this time, running applications are not affected. However, new builds are currently failing. We will share an update as soon as we have more information.

  2. resolved Apr 28, 2026, 08:13 AM UTC

    The issue has been resolved, a preventive measurement identified, and we apologize for any inconvenience this may have caused.

Read the full incident report →

Major April 28, 2026 Low Disk IO Performance CloudVMs 7h 17m

Started Apr 28, 2026, 05:05 AM UTC· resolved Apr 28, 2026, 12:23 PM UTC

  1. investigating Apr 28, 2026, 05:05 AM UTC

    We are investigating low disk IO performance on CloudVMs

  2. resolved Apr 28, 2026, 12:23 PM UTC

    The incident has been resolved. Our engineering team identified the root cause as a fault within our distributed storage infrastructure that led to degraded service performance. The issue has been remediated and all systems are confirmed to be operating normally. We apologize for any inconvenience and appreciate your patience during this time.

Read the full incident report →

Major April 15, 2026 Degraded service connectivity on Deploio cluster 1d 18h

Started Apr 15, 2026, 12:39 PM UTC· resolved Apr 17, 2026, 06:39 AM UTC

  1. resolved Apr 17, 2026, 06:39 AM UTC

    All maintenance work has been done.

Read the full incident report →

Major April 14, 2026 Local Network Redundancy Degraded (NTT E Shelter) 4h 14m

Started Apr 14, 2026, 04:15 PM UTC· resolved Apr 14, 2026, 08:29 PM UTC

  1. resolved Apr 14, 2026, 08:29 PM UTC

    We've now resolved the incident by replacing the affected switch in the rack. Thanks for your patience.

Read the full incident report →

Major April 14, 2026 Instability with On Demand Services 25m

Started Apr 14, 2026, 03:36 PM UTC· resolved Apr 14, 2026, 04:02 PM UTC

  1. resolved Apr 14, 2026, 04:02 PM UTC

    The incident has been resolved and all services are back up and running. Thank you for your patience. Root cause: Underlying VM restarts triggered new service instances to be spawned, causing interruptions to non-HA services. Everything is fully operational again.

Read the full incident report →