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

Exoscale incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 3, 2026[CH-DK-2] Network Maintenance - VPN1h 29mResolved
Oct 15, 2026[CH-GVA-2] Network Maintenance - Edge Routers | Backup date9h 4mResolved
Oct 14, 2026[CH-GVA-2] Network Maintenance - Edge Routers5h 11mResolved
Oct 9, 2026[API] Increased Error Rates and Latencies35 minResolved
Oct 8, 2026[API] Increased Error Rates and Latencies2h 30mResolved
Oct 6, 2026[Compute API] Planned maintenance1h 4mResolved
Oct 6, 2026[API] Increased Error Rates and Latencies1h 32mResolved
Oct 6, 2026SKS control plane components migration to new deployment platform26h 3mResolved
Oct 2, 2026Network Load Balancer maintenance1h 32mResolved
Oct 2, 2026Network Load Balancer maintenance1h 33mResolved
Oct 1, 2026Concrete AI Dedicated Inference - Requests ending with 50013h 34mResolved
Oct 1, 2026Concrete AI Dedicated Inference1h 0mResolved
Sep 30, 2026SKS pro clusters etcd Backend Migration2h 29mResolved
Sep 29, 2026Network Load Balancer maintenance2h 0mResolved
Sep 29, 2026Network Load Balancer maintenance1h 59mResolved
Sep 28, 2026Network Load Balancer maintenance2h 3mResolved
Sep 28, 2026Network Load Balancer maintenance1h 33mResolved
Sep 27, 2026Network Load Balancer maintenance41 minResolved
Sep 27, 2026Network Load Balancer maintenance1h 31mResolved
Sep 23, 2026Starter SKS clusters etcd Backend Migration1h 19mResolved
Sep 21, 2026NLB SOF maintenance takes more time than expected.19 minResolved
Sep 21, 2026Network Load Balancer maintenance1h 3mResolved
Sep 18, 2026Compute Managed Elastic IP issues44 minResolved
Sep 17, 2026SKS control plane components migration to new deployment platform2h 19mResolved
Sep 16, 2026SKS API operations are unavailable23 minResolved
Sep 10, 2026High API error rate41 minResolved
Sep 4, 2026SKS control plane components migration to new deployment platform2h 25mResolved
Sep 3, 2026[API] Increased Error Rates and Latencies19 minResolved
Sep 2, 2026Starter SKS clusters etcd Backend Migration2h 0mResolved
Sep 1, 2026[API] Increased Error Rates and Latencies59 minResolved
Sep 1, 2026Portal and API outage6h 19mResolved
Aug 27, 2026SKS Etcd Backend Migration1h 12mResolved
Aug 26, 2026Concrete AI Dedicated Inference1h 28mResolved
Aug 26, 2026SKS Etcd Backend Migration1h 54mResolved
Aug 26, 2026SKS control plane components migration to new deployment platform25h 9mResolved
Aug 24, 2026SKS control plane components migration to new deployment platform2h 17mResolved
Aug 20, 2026Increased latency and error rate on compute API in all zones1h 39mResolved
Aug 20, 2026SKS control plane components migration to new deployment platform1206h 39mResolved
Aug 19, 2026SKS Etcd Backend Migration24h 38mResolved
Aug 19, 2026[AT-VIE-1/2] IPv6 Transit Provider Connectivity Degradation3h 13mResolved
Aug 17, 2026SKS control plane components migration to new deployment platform1h 36mResolved
Aug 12, 2026SKS control plane components migration to new deployment platform1h 16mResolved
Jul 2, 2026SKS control plane components migration to new deployment platform2382h 9mResolved

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.