Is Exoscale down?

Last checked 3m ago
Current status
Exoscale is up

No incidents right now.

Official status page: https://exoscalestatus.com · Polled every 5 minutes · 107 components tracked

Exoscale is operational right now. Last checked 3m ago; the most recent incident resolved 20d ago.

Real-time Exoscale status, recent outages, and incident history — pulled directly from Exoscale's official status page at https://exoscalestatus.com every 5 minutes. Pingoru tracks 107 Exoscale services and has captured 36 incidents in the last 90 days (98.62% uptime). Get email, Slack, Discord, or webhook alerts the moment Exoscale reports a new incident — free for 5 monitors, no credit card.

Users who monitor Exoscale also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Exoscale uptime 98.62% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 38m
    Started Aug 20, 2026, 09:56 AM UTC · Resolved Aug 20, 2026, 11:34 AM UTC
    CH-GVA-2CH-DK-2DE-FRA-1DE-MUC-1AT-VIE-1AT-VIE-2BG-SOF-1HR-ZAG-1API
    Timeline · 3 updates
    • investigating · Aug 20, 2026, 09:56 AM UTC

      We are seeing increased latency and timeouts on compute related API endpoints in all zones.

    • monitoring · Aug 20, 2026, 10:15 AM UTC

      Mitigations are in place and latency is within acceptable boundaries again. We will continue to monitor the situation.

    • resolved · Aug 20, 2026, 11:34 AM UTC

      Error rate and latency have remained stable. Closing the incident.

    Latest: Error rate and latency have remained stable. Closing the incident.

  2. Resolved 3h 11m
    Started Aug 19, 2026, 07:08 AM UTC · Resolved Aug 19, 2026, 10:19 AM UTC
    AT-VIE-1AT-VIE-2APIBlock StorageComputeManaged Database service DBaaSManaged Kubernetes SKSManaged Private NetworksNetwork Internet Transit ConnectivityNetwork Load Balancer NLB
    Timeline · 4 updates
    • investigating · Aug 19, 2026, 07:08 AM UTC

      IPv4 is not affected. One of our transit providers is currently no longer advertising our IPv6 prefixes. IPv6 traffic is operating through our remaining transit provider. We have opened a ticket with the affected provider and are awaiting their response. During this time, some users may experience higher-than-normal latency due to traffic being routed through a single transit provider.

    • investigating · Aug 19, 2026, 07:49 AM UTC

      Our transit provider has acknowledge the issue and they are investigating.

    • monitoring · Aug 19, 2026, 08:50 AM UTC

      Issue has been fixed by the upstream provider.

    • resolved · Aug 19, 2026, 10:19 AM UTC

      The situation is stable so we are closing the incident. The issue seems to have been caused by a “software” not working as expected in our Transit provider network.

    Latest: The situation is stable so we are closing the incident. The issue seems to have been caused by a “software” not working as expected in our Transit provider network.

  3. Resolved 45m
    Started Aug 18, 2026, 12:45 PM UTC · Resolved Aug 18, 2026, 01:30 PM UTC
    AT-VIE-2APINetwork Load Balancer NLB
    Timeline · 3 updates
    • investigating · Aug 18, 2026, 12:45 PM UTC

      We are investigating increased error rate with our NLB API in vie2

    • monitoring · Aug 18, 2026, 01:12 PM UTC

      We have resolved the increased error rate, but will keep monitoring the situation for a while.

    • resolved · Aug 18, 2026, 01:30 PM UTC

      Situation is stable.

    Latest: Situation is stable.

  4. Resolved 1h 1m
    Started Aug 14, 2026, 01:58 PM UTC · Resolved Aug 14, 2026, 03:00 PM UTC
    BG-SOF-1API
    Timeline · 7 updates
    • investigating · Aug 14, 2026, 01:58 PM UTC

      NLB API operations are currently not available in sof1. Traffic and functionality of existing NLBs is not affected.

    • investigating · Aug 14, 2026, 02:20 PM UTC

      Our engineers are actively investigating the issue. They found the root cause of the issue and are working to recover the service.

    • investigating · Aug 14, 2026, 02:26 PM UTC

      Our engineers are actively working on recovering the service.

    • investigating · Aug 14, 2026, 02:33 PM UTC

      Our engineers are actively working on recovering the service.

    • monitoring · Aug 14, 2026, 02:38 PM UTC

      The service has recovered, we are monitoring the situation to ensure all work as expected.

    • monitoring · Aug 14, 2026, 02:54 PM UTC

      Service is operational again.

    • resolved · Aug 14, 2026, 03:00 PM UTC

      Service recovered and is fully operational.

    Latest: Service recovered and is fully operational.

  5. Resolved 2h
    Started Jul 23, 2026, 10:54 PM UTC · Resolved Jul 24, 2026, 12:55 AM UTC
    DE-FRA-1APIBlock StorageComputeManaged Database service DBaaSManaged Kubernetes SKSManaged Private NetworksNetwork Internet Transit ConnectivityNetwork Load Balancer NLBObject Storage SOS
    Timeline · 3 updates
    • investigating · Jul 23, 2026, 10:54 PM UTC

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

    • investigating · Jul 23, 2026, 11:41 PM UTC

      Network latency issue is now resolved.

    • investigating · Jul 24, 2026, 12:54 AM UTC

      Network latency issue is now resolved.

    Latest: Network latency issue is now resolved.

See the full Exoscale outage history

5 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Exoscale outage history →

Or sign up free to get alerts when Exoscale breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 10 incidents View full outage history →