Exoscale Outage History
43 incidents recorded over the last 365 days, 43 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Exoscale Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | [CH-DK-2] Network Maintenance - VPN | 1h 29m | Resolved |
| Oct 15, 2026 | [CH-GVA-2] Network Maintenance - Edge Routers | Backup date | 9h 4m | Resolved |
| Oct 14, 2026 | [CH-GVA-2] Network Maintenance - Edge Routers | 5h 11m | Resolved |
| Oct 9, 2026 | [API] Increased Error Rates and Latencies | 35 min | Resolved |
| Oct 8, 2026 | [API] Increased Error Rates and Latencies | 2h 30m | Resolved |
| Oct 6, 2026 | [Compute API] Planned maintenance | 1h 4m | Resolved |
| Oct 6, 2026 | [API] Increased Error Rates and Latencies | 1h 32m | Resolved |
| Oct 6, 2026 | SKS control plane components migration to new deployment platform | 26h 3m | Resolved |
| Oct 2, 2026 | Network Load Balancer maintenance | 1h 32m | Resolved |
| Oct 2, 2026 | Network Load Balancer maintenance | 1h 33m | Resolved |
| Oct 1, 2026 | Concrete AI Dedicated Inference - Requests ending with 500 | 13h 34m | Resolved |
| Oct 1, 2026 | Concrete AI Dedicated Inference | 1h 0m | Resolved |
| Sep 30, 2026 | SKS pro clusters etcd Backend Migration | 2h 29m | Resolved |
| Sep 29, 2026 | Network Load Balancer maintenance | 2h 0m | Resolved |
| Sep 29, 2026 | Network Load Balancer maintenance | 1h 59m | Resolved |
| Sep 28, 2026 | Network Load Balancer maintenance | 2h 3m | Resolved |
| Sep 28, 2026 | Network Load Balancer maintenance | 1h 33m | Resolved |
| Sep 27, 2026 | Network Load Balancer maintenance | 41 min | Resolved |
| Sep 27, 2026 | Network Load Balancer maintenance | 1h 31m | Resolved |
| Sep 23, 2026 | Starter SKS clusters etcd Backend Migration | 1h 19m | Resolved |
| Sep 21, 2026 | NLB SOF maintenance takes more time than expected. | 19 min | Resolved |
| Sep 21, 2026 | Network Load Balancer maintenance | 1h 3m | Resolved |
| Sep 18, 2026 | Compute Managed Elastic IP issues | 44 min | Resolved |
| Sep 17, 2026 | SKS control plane components migration to new deployment platform | 2h 19m | Resolved |
| Sep 16, 2026 | SKS API operations are unavailable | 23 min | Resolved |
| Sep 10, 2026 | High API error rate | 41 min | Resolved |
| Sep 4, 2026 | SKS control plane components migration to new deployment platform | 2h 25m | Resolved |
| Sep 3, 2026 | [API] Increased Error Rates and Latencies | 19 min | Resolved |
| Sep 2, 2026 | Starter SKS clusters etcd Backend Migration | 2h 0m | Resolved |
| Sep 1, 2026 | [API] Increased Error Rates and Latencies | 59 min | Resolved |
| Sep 1, 2026 | Portal and API outage | 6h 19m | Resolved |
| Aug 27, 2026 | SKS Etcd Backend Migration | 1h 12m | Resolved |
| Aug 26, 2026 | Concrete AI Dedicated Inference | 1h 28m | Resolved |
| Aug 26, 2026 | SKS Etcd Backend Migration | 1h 54m | Resolved |
| Aug 26, 2026 | SKS control plane components migration to new deployment platform | 25h 9m | Resolved |
| Aug 24, 2026 | SKS control plane components migration to new deployment platform | 2h 17m | Resolved |
| Aug 20, 2026 | Increased latency and error rate on compute API in all zones | 1h 39m | Resolved |
| Aug 20, 2026 | SKS control plane components migration to new deployment platform | 1206h 39m | Resolved |
| Aug 19, 2026 | SKS Etcd Backend Migration | 24h 38m | Resolved |
| Aug 19, 2026 | [AT-VIE-1/2] IPv6 Transit Provider Connectivity Degradation | 3h 13m | Resolved |
| Aug 17, 2026 | SKS control plane components migration to new deployment platform | 1h 36m | Resolved |
| Aug 12, 2026 | SKS control plane components migration to new deployment platform | 1h 16m | Resolved |
| Jul 2, 2026 | SKS control plane components migration to new deployment platform | 2382h 9m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Exoscale incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Exoscale Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Exoscale acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Exoscale outage in this window ran 99d 6h, against a mean recovery of 3d 15h. If you depend on Exoscale in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.