nine Outage History

nine is up right now

nine had 28 outages in the last 2 years totaling 2067h 16m of downtime — averaging 1.2 incidents per month.

There were 28 nine outages since October 7, 2025 totaling 2067h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.nine.ch

Major September 15, 2026

Outage affecting deplo.io applications and NKE services

Detected by Pingoru
Sep 15, 2026, 07:23 PM UTC
Resolved
Sep 16, 2026, 08:29 AM UTC
Duration
13h 5m
Timeline · 3 updates
  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

Detected by Pingoru
Sep 15, 2026, 05:38 PM UTC
Resolved
Sep 16, 2026, 09:51 AM UTC
Duration
16h 13m
Timeline · 3 updates
  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

Detected by Pingoru
Sep 11, 2026, 12:40 PM UTC
Resolved
Sep 11, 2026, 01:02 PM UTC
Duration
22m
Timeline · 2 updates
  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

Detected by Pingoru
Sep 07, 2026, 05:36 AM UTC
Resolved
Sep 07, 2026, 10:54 AM UTC
Duration
5h 18m
Timeline · 2 updates
  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

Detected by Pingoru
Aug 20, 2026, 10:21 AM UTC
Resolved
Aug 20, 2026, 10:56 AM UTC
Duration
35m
Timeline · 3 updates
  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

Detected by Pingoru
Aug 12, 2026, 05:32 AM UTC
Resolved
Aug 19, 2026, 09:39 AM UTC
Duration
7d 4h
Timeline · 2 updates
  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

Network Connectivity Issues

Detected by Pingoru
Aug 11, 2026, 05:58 PM UTC
Resolved
Aug 11, 2026, 07:06 PM UTC
Duration
1h 7m
Timeline · 1 update
  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

Detected by Pingoru
Jul 28, 2026, 08:08 AM UTC
Resolved
Jul 28, 2026, 09:16 AM UTC
Duration
1h 8m
Timeline · 2 updates
  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.

Detected by Pingoru
Jul 27, 2026, 01:27 PM UTC
Resolved
Jul 27, 2026, 04:34 PM UTC
Duration
3h 6m
Timeline · 3 updates
  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

Detected by Pingoru
Jul 15, 2026, 11:59 AM UTC
Resolved
Jul 22, 2026, 12:35 PM UTC
Duration
7d
Timeline · 3 updates
  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"

Detected by Pingoru
Jul 13, 2026, 02:39 PM UTC
Resolved
Jul 13, 2026, 06:02 PM UTC
Duration
3h 22m
Timeline · 3 updates
  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

Detected by Pingoru
Jun 05, 2026, 07:50 AM UTC
Resolved
Jun 09, 2026, 02:54 PM UTC
Duration
4d 7h
Timeline · 3 updates
  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

Detected by Pingoru
Apr 28, 2026, 08:05 AM UTC
Resolved
Apr 28, 2026, 08:13 AM UTC
Duration
7m
Timeline · 2 updates
  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

Detected by Pingoru
Apr 28, 2026, 05:05 AM UTC
Resolved
Apr 28, 2026, 12:23 PM UTC
Duration
7h 17m
Timeline · 2 updates
  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 14, 2026

Instability with On Demand Services

Detected by Pingoru
Apr 14, 2026, 03:36 PM UTC
Resolved
Apr 14, 2026, 04:02 PM UTC
Duration
25m
Timeline · 1 update
  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 →

Major April 13, 2026

Instability with On-Demand Services

Detected by Pingoru
Apr 13, 2026, 10:31 AM UTC
Resolved
Apr 13, 2026, 12:31 PM UTC
Duration
1h 59m
Timeline · 1 update
  1. resolved Apr 13, 2026, 12:31 PM UTC

    We've now resolved the incident. Thanks for your patience. We are monitoring the situation further.

Read the full incident report →

Major February 24, 2026

Deploio Apps Build Issue

Detected by Pingoru
Feb 24, 2026, 09:26 AM UTC
Resolved
Feb 24, 2026, 09:49 AM UTC
Duration
23m
Timeline · 1 update
  1. resolved Feb 24, 2026, 09:49 AM UTC

    We've now resolved the incident. Thanks for your patience. The incident has been caused by a expired certificate, we adjusted our monitoring accordingly.

Read the full incident report →

Major February 10, 2026

NKE Storage Backend Issues

Detected by Pingoru
Feb 10, 2026, 09:12 AM UTC
Resolved
Apr 13, 2026, 12:31 PM UTC
Duration
62d 3h
Timeline · 1 update
  1. resolved Apr 13, 2026, 12:31 PM UTC

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

Read the full incident report →

Major February 10, 2026

Managed Grafana issues

Detected by Pingoru
Feb 10, 2026, 06:43 AM UTC
Resolved
Feb 10, 2026, 07:49 PM UTC
Duration
13h 6m
Timeline · 1 update
  1. resolved Feb 10, 2026, 07:49 PM UTC

    The issue has been resolved, and any pending tasks that could not complete have been worked through. According to our monitoring, everything is back to normal. We will keep a close eye on the situation and will close the status tomorrow morning if it remains stable.

Read the full incident report →

Major January 6, 2026

Issue Affecting Dockerfile-Based Applications

Detected by Pingoru
Jan 06, 2026, 04:21 AM UTC
Resolved
Jan 06, 2026, 03:40 PM UTC
Duration
11h 18m
Timeline · 1 update
  1. resolved Jan 06, 2026, 03:40 PM UTC

    The root cause of the issue has been identified and a fix has been applied. All affected systems are now back up and running normally. We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Major January 5, 2026

Connectivity issues

Detected by Pingoru
Jan 05, 2026, 02:45 AM UTC
Resolved
Jan 05, 2026, 04:17 AM UTC
Duration
1h 32m
Timeline · 1 update
  1. resolved Jan 05, 2026, 04:17 AM UTC

    The system is currently stable. We will continue investigating the root cause during the day.

Read the full incident report →