Resolved after 54 minutes, affecting BG-SOF-1 and Managed Kubernetes SKS, on June 25, 2026.
Due to a wrong manipulation, we had to stop the SKS service in SOF1 while restoring the database. In the meantime, all Clusters and NodePools stay reachable and work as expected.
Affected components
BG-SOF-1Managed Kubernetes SKS
Update timeline
- investigating Jun 25, 2026, 12:00 PM UTC
Due to a wrong manipulation, we had to stop the SKS service in SOF1 while restoring the database. In the meantime, all Clusters and NodePools stay reachable and work as expected.
- resolved Jun 25, 2026, 12:54 PM UTC
SKS service is back to its nominal state.
Your product runs on more than Exoscale
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services