Exoscale incident

[AT-VIE-1/2] IPv6 Transit Provider Connectivity Degradation

Minor Resolved View vendor source →

Exoscale experienced a minor incident on August 19, 2026 affecting AT-VIE-1 and AT-VIE-2 and 1 more component, lasting 3h 11m. The incident has been resolved; the full update timeline is below.

Started
Aug 19, 2026, 07:08 AM UTC
Resolved
Aug 19, 2026, 10:19 AM UTC
Duration
3h 11m
Detected by Pingoru
Aug 19, 2026, 07:08 AM UTC

Affected components

AT-VIE-1AT-VIE-2APIBlock StorageComputeManaged Database service DBaaSManaged Kubernetes SKSManaged Private NetworksNetwork Internet Transit ConnectivityNetwork Load Balancer NLB

Update timeline

  1. 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.

  2. investigating Aug 19, 2026, 07:49 AM UTC

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

  3. monitoring Aug 19, 2026, 08:50 AM UTC

    Issue has been fixed by the upstream provider.

  4. 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.