Status
Scheduled maintenances
Maintenance Work
We will perform a major upgrade of OpenStack on our control and compute hosts in the LPG (Lupfig) region.
Expected Impact
Our Cloud Control Panel and API will remain active during this maintenance work. While in maintenance, the performance of the Cloud Control Panel and API may be degraded, and during short periods of time it may not be possible to make any changes (for each case, we measured around 3 minutes in our lab). Thanks to our redundant setup no further impact...
Complimentary information for transparency, no relevant service impact expected.
Maintenance Work
We will be performing a operating system upgrade on our storage hosts in the RMA (Rümlang) region.
Expected impact
During this maintenance window, we don’t expect any major impact on storage performance or availability. You may experience short latency spikes up to two seconds.
Our LPG (Lupfig) region is not affected by this maintenance.
We apologize for any inconvenience this may cause...
Complimentary information for transparency, no relevant service impact expected.
Maintenance Work
We will be performing a operating system upgrade on our storage hosts in the LPG (Lupfig) region.
Expected impact
During this maintenance window, we don’t expect any major impact on storage performance or availability. You may experience short latency spikes up to two seconds.
Our RMA (Rümlang) region is not affected by this maintenance.
We apologize for any inconvenience this may cause...
Past Incidents
The maintenance work in RMA is completed. Operations are all back to normal. It was a bit bumpier than expected between 21:16 and 22:50. We had to completely disable the backend DB several times to allow it to recover from a failure during a migration step. This caused several longer than expected API outages. Sorry for the inconvenience this caused.
On Friday, 2026-05-08, between 00:20 and 04:37 CEST, one of the redundant dark fiber connections between our cloud regions LPG and RMA faced an outage caused by the provider during a maintenance window which had not been announced to cloudscale. On automatic re-routing, when the connection was lost and when it came back up, the new routing table was not applied correctly. This routing issue subsequently caused failures in internet connectivity for specific source and destination pairings...