We're performing planned maintenance on the traffic-routing layer of deplo.io. During the window, each application may experience a brief interruption (up to a few minutes) as its traffic is moved to the upgraded infrastructure. Connections are restored automatically — no action is required on your side.

Your application URLs, custom domains and TLS certificates remain unchanged.

This maintenance has been cancelled due to the DDoS attack from yesterday. We will move this maintenance a couple of weeks, you will get notified again when we schedule the new maintenance. Thank you for your patience.

We are currently experiencing a network incident that may cause connectivity issues and affect the availability of our services.

We're currently seeing increased traffic on a small number of IP addresses. We're monitoring the situation and will update here with further information.

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

We are currently experiencing a network incident that may cause connectivity issues and affect the availability of our services.

We are investigating the cause and working to resolve the issue. We apologize for any inconvenience caused and will provide further updates as soon as more information becomes available.

We are currently experiencing connection failures affecting access to our services. We have identified a large volume of malicious traffic saturating our network links and are working on mitigating the issue.

We will post another update when the situation changes.

We have started blocking the malicious traffic and our network is starting to recover. Some users may still see elevated latency or intermittent errors while capacity returns to normal. Our team is actively working to bring the situation fully under control.

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.

We will be performing scheduled maintenance on our CZ41 virtualization environment. No customer impact is expected during this maintenance window.

We appreciate your understanding and will inform you once the maintenance is complete.

The scheduled maintenance is now underway. We'll keep you updated on our progress.

The maintenance is now complete. Thanks for your patience.

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 will be performing scheduled maintenance on our ES34 virtualization environment. No customer impact is expected during this maintenance window.

We appreciate your understanding and will inform you once the maintenance is complete.

The scheduled maintenance is now underway. We'll keep you updated on our progress.

The maintenance is now complete. Thanks for your patience.

We are looking into the issue. Existing IPs will continue to work.

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.

To continuously operate our virtual infrastructure safely, a critical maintenance configuration change needs to be scheduled to apply a mitigation. This affects all Root VServers and CloudVMs with the product type "CloudVM C*" (newer CloudVMs, assignable to projects and which product names like nine-* are not affected).

During this maintenance, all virtual machines need to be stopped, including the virtualization host, and then started again. The individual downtime will be shorter than the scheduled window.

The scheduled maintenance is now underway.

The maintenance is now complete. Thanks for your patience.

All buckets in es34 are affected and all services that use S3 are affected. Including: Loki, Docker Registry

We are investigating and will get back to you

Buckets are reachable again. We are still investigating the root cause together with the vendor and monitoring the situation. Once we are confident the issue is fully resolved, we will post a final update. If you continue to experience issues, please reach out to support.

We have identified the root cause: a process [in the storage layer] got stuck, and a reboot was required to restore service. Together with the vendor, we are improving the monitoring for this component and have defined a playbook to resolve similar issues faster in the future. There is currently no indication that this issue will re-occur. We consider this incident resolved.

The issue arose again. We are in contact with the vendor.

Our deepest apologies. We are working hard to resolve the issue asap.

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 support@nine.ch.