nine had 20 outages in the last 2 years totaling 1881h 33m of downtime — averaging 0.8 incidents per month.
There were 20 nine outages since October 7, 2025 totaling 1881h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.
New nodes currently cannot be spawned. Existing nodes are working. Autoscaling nodes, manual scaling nodes and new cluster nodes cannot be created right now.
We've now resolved the incident. Thanks for your patience.
We've confirmed there is a problem, we're working to resolve it.
We've fixed the core issue, and are waiting for things to recover.
We've now resolved the incident. Thanks for your patience.
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.
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.
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].
Custom host buckets might show a fake TLS cert. We identified a bug in the certificate provisioning and are working on a fix.
We've fixed the core issue, and are waiting for things to recover.
We've now resolved the incident. Thanks for your patience.
We will let you know with asap
We have added more resources to our nine-cz42 location. NKE clusters can now be created there via Cockpit.
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/
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.
The issue has been resolved, a preventive measurement identified, and we apologize for any inconvenience this may have caused.
We are investigating low disk IO performance on CloudVMs
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.
All maintenance work has been done.
We've now resolved the incident by replacing the affected switch in the rack. Thanks for your patience.
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.
We've now resolved the incident. Thanks for your patience. We are monitoring the situation further.
We've now resolved the incident. Thanks for your patience. The incident has been caused by a expired certificate, we adjusted our monitoring accordingly.
We've now resolved the incident. Thanks for your patience.
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.
We've now resolved the incident together with our vendors TAC. Thanks for your patience.
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.
The system is currently stable. We will continue investigating the root cause during the day.
Unser E-Mail-Dienstleister hat das Problem, das seine E-Mail-Systeme beeinträchtigt hat, erfolgreich behoben. Die E-Mail-Kommunikation über unser Ticket-System funktioniert nun wieder einwandfrei. Wir bedanken uns herzlich für Ihre Geduld und Ihr Verständnis während der Störung. Sollten Sie weiterhin Probleme haben, zögern Sie bitte nicht, uns zu kontaktieren. ---- Our mail service provider has successfully resolved the issue affecting their mail systems. Email communication through our ticket system is now fully operational again. We sincerely thank you for your patience and understanding during the disruption. If you experience any remaining issues, please don’t hesitate to contact us.
This incident has been resolved.
We've now resolved the incident. Thanks for your patience. The issue was caused by an update of the underlying system.