After consulting our network vendor's TAC, we will upgrade the firmware on all devices in the NTT ES34 Managed Segment. The new release should fix the root cause of the crashes we have seen on one of the routers in this network fabric.

During the upgrade we expect a temporary loss of redundancy, short traffic disruptions and possibly higher latency.

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.

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

We still see NKE nodes and therefore also Deploio Services still recovering from this incident.

deplo.io applications and Managed Kubernetes (NKE) services are operating normally again.

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

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.

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.

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

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

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

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.

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

The maintenance is now complete. Thanks for your patience.

Still underway should resolve soon

The maintenance is now complete. Thanks for your patience.

We are currently investigating an availability issue affecting Root VServers hosted on the virtualization node nvirt108 (Colozueri.ch 4.2). The node is currently unavailable and our team is working to restore service as quickly as possible. We will provide a further update as soon as we have more information.

Thank you for your patience.

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.

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.

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.

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.

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.