Exoscale Outage History

Exoscale is up right now

Exoscale had 10 outages in the last 2 years totaling 44h 48m of downtime — averaging 0.4 incidents per month.

There were 10 Exoscale outages since March 31, 2026 totaling 44h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://exoscalestatus.com

Minor May 20, 2026

Network instability on a BGP transit link

Detected by Pingoru
May 20, 2026, 11:10 PM UTC
Resolved
May 21, 2026, 06:54 AM UTC
Duration
7h 44m
Affected: HR-ZAG-1Network Internet Transit Connectivity
Timeline · 2 updates
  1. investigating May 21, 2026, 01:27 AM UTC

    We are currently experiencing network instability on a link with one of our BGP transit providers. Redundancy measures are actively routing traffic, so we do not expect any impact on service availability.

  2. resolved May 21, 2026, 06:54 AM UTC

    The situation is nominal again. All transit links in the zone are routing traffic.

Read the full incident report →

Minor May 10, 2026

[API] Increased Error Rates and Latencies

Detected by Pingoru
May 10, 2026, 09:03 AM UTC
Resolved
May 10, 2026, 10:23 AM UTC
Duration
1h 19m
Affected: DE-FRA-1Managed Kubernetes SKSNetwork Load Balancer NLB
Timeline · 4 updates
  1. investigating May 10, 2026, 09:03 AM UTC

    We are investigating an increased error rates and latencies on the API. We’ll post an update as soon as we have more information.

  2. investigating May 10, 2026, 09:13 AM UTC

    We have found the roo cause and are applying a mitigation to solve the problem.

  3. monitoring May 10, 2026, 10:03 AM UTC

    The mitigation was deployed and we are now back to a normal state. We are now in monitoring mode.

  4. resolved May 10, 2026, 10:23 AM UTC

    We are back in a normal state.

Read the full incident report →

Major May 4, 2026

Network Connectivity Issues in SOF1

Detected by Pingoru
May 04, 2026, 10:16 AM UTC
Resolved
May 04, 2026, 11:07 AM UTC
Duration
51m
Affected: BG-SOF-1APIBlock StorageComputeManaged Database service DBaaSManaged Kubernetes SKSManaged Private NetworksNetwork Internet Transit ConnectivityNetwork Load Balancer NLBObject Storage SOS
Timeline · 9 updates

Read the full incident report →

Minor April 15, 2026

[AT-VIE-1] Degraded Network Redundancy

Detected by Pingoru
Apr 15, 2026, 10:46 AM UTC
Resolved
Apr 16, 2026, 07:43 AM UTC
Duration
20h 57m
Affected: AT-VIE-1APIBlock StorageComputeManaged Database service DBaaSManaged Kubernetes SKSManaged Private NetworksNetwork Internet Transit ConnectivityNetwork Load Balancer NLBObject Storage SOS
Timeline · 2 updates
  1. investigating Apr 15, 2026, 10:46 AM UTC

    We are currently experiencing a degradation of network redundancy in AT-VIE-1 due to an ongoing incident affecting one of our transit providers. Following a maintenance operation on their side, the provider encountered a hardware failure on a router serving our connectivity in Vienna. The device could not be recovered remotely and requires a full replacement. At this time, services in the zone remain operational. However, redundancy is reduced, which may increase sensitivity to additional network events. The transit provider has dispatched a replacement device, with an estimated arrival on-site on April 16 at 03:00 CEST. Restoration of full redundancy will occur after the hardware is installed and services are fully recovered. We are closely monitoring the situation and will provide updates as more information becomes available. Impact: Reduced network redundancy in VIE1 (no current service disruption)

  2. resolved Apr 16, 2026, 07:43 AM UTC

    The incident affecting one of our transit providers in AT-VIE-1 has been resolved. Following the hardware issue that occurred after a maintenance operation, the provider has restored the affected router and services are now functioning normally. Network redundancy in AT-VIE-1 has been fully restored. We will continue to monitor the situation closely, but no further impact is expected. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor April 12, 2026

[DE-MUC-1] Elevated error rate for SOS

Detected by Pingoru
Apr 12, 2026, 09:08 AM UTC
Resolved
Apr 12, 2026, 10:30 AM UTC
Duration
1h 21m
Affected: DE-MUC-1Object Storage SOS
Timeline · 4 updates
  1. investigating Apr 12, 2026, 09:08 AM UTC

    We’re seeing degraded performance of our object storage stack in entire DE-MUC-1 zone.

  2. investigating Apr 12, 2026, 09:47 AM UTC

    We’re currently applying a mitigation. We’ll update the incident as soon as we have new information.

  3. monitoring Apr 12, 2026, 09:54 AM UTC

    We’ve applied a mitigation - we’re seeing improvement across entire zone.

  4. resolved Apr 12, 2026, 10:30 AM UTC

    Incident resolved.

Read the full incident report →

Minor April 8, 2026

[Network] Increased internet network latencies and packet loss

Detected by Pingoru
Apr 08, 2026, 11:08 AM UTC
Resolved
Apr 08, 2026, 07:10 PM UTC
Duration
8h 1m
Affected: HR-ZAG-1Network Internet Transit Connectivity
Timeline · 4 updates
  1. investigating Apr 08, 2026, 11:08 AM UTC

    We are investigating Increased internet network latencies and packet loss. We’ll post an update as soon as we have more information.

  2. monitoring Apr 08, 2026, 11:09 AM UTC

    One of our internet transit provider is experiencing routing issues. Traffic has been re-routed to alternate paths. We are monitoring the situation

  3. monitoring Apr 08, 2026, 11:24 AM UTC

    Our transit provider has confirmed an outage on their end. Situation is stable while traffic is routed to alternate paths

  4. resolved Apr 08, 2026, 07:10 PM UTC

    Issue with our transit provider has been resolved

Read the full incident report →

Minor April 6, 2026

Increased Error Rates and Latencies

Detected by Pingoru
Apr 06, 2026, 12:49 PM UTC
Resolved
Apr 06, 2026, 02:04 PM UTC
Duration
1h 14m
Affected: CH-DK-2Network Load Balancer NLB
Timeline · 3 updates
  1. investigating Apr 06, 2026, 12:49 PM UTC

    We’re experiencing increased error rate on some NLBs in CH-DK-2.

  2. monitoring Apr 06, 2026, 01:17 PM UTC

    We have applied a mitigation and we’re no longer seeing dropped traffic. We’ll keep monitoring the situation and update accordingly.

  3. resolved Apr 06, 2026, 02:04 PM UTC

    Issue has been resolved.

Read the full incident report →

Minor April 1, 2026

Increased Latency on Object Storage

Detected by Pingoru
Apr 01, 2026, 08:52 AM UTC
Resolved
Apr 01, 2026, 09:19 AM UTC
Duration
27m
Affected: CH-GVA-2Object Storage SOS
Timeline · 2 updates
  1. investigating Apr 01, 2026, 08:52 AM UTC

    We are experiencing increased latency on Object Storage in ch-gva-2

  2. resolved Apr 01, 2026, 09:19 AM UTC

    The issue seems to be resolved, latency is back to normal.

Read the full incident report →

Minor March 31, 2026

[NLB] Increased Error Rates and Latencies

Detected by Pingoru
Mar 31, 2026, 04:54 PM UTC
Resolved
Mar 31, 2026, 05:30 PM UTC
Duration
35m
Affected: DE-FRA-1Network Load Balancer NLB
Timeline · 5 updates
  1. investigating Mar 31, 2026, 04:54 PM UTC

    We’re experiencing increased error rate on some NLBs in DE-FRA-1.

  2. monitoring Mar 31, 2026, 05:12 PM UTC

    We have applied a mitigation and are currently monitoring the situation.

  3. investigating Mar 31, 2026, 05:18 PM UTC

    We do still experience increased error rate, and continue to investigate

  4. monitoring Mar 31, 2026, 05:25 PM UTC

    Further mitigation has been applied, we are monitoring the situation which seems to be back to normal.

  5. resolved Mar 31, 2026, 05:30 PM UTC

    Issue has been resolved.

Read the full incident report →