Abion incident

CNAME Flattening Service Disruption

Major Resolved View vendor source →

Abion experienced a major incident on August 28, 2026 affecting DNS Unicast Network and DNS Anycast Network, lasting 2h 27m. The incident has been resolved; the full update timeline is below.

Started
Aug 28, 2026, 11:40 AM UTC
Resolved
Aug 28, 2026, 02:07 PM UTC
Duration
2h 27m
Detected by Pingoru
Aug 28, 2026, 11:40 AM UTC

Affected components

DNS Unicast NetworkDNS Anycast Network

Update timeline

  1. investigating Aug 28, 2026, 11:40 AM UTC

    We are currently experiencing an issue with our CNAME flattening service, which is temporarily unavailable. This may affect DNS resolution for domains relying on this feature. Our engineering team is working on a solution, and we will post updates here as soon as we have more information. We apologize for any inconvenience this may cause.

  2. investigating Aug 28, 2026, 11:41 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Aug 28, 2026, 12:28 PM UTC

    We've identified the root cause of the disruption. An internal fault caused two of our system components to become stuck waiting on each other, which prevented the lookups needed for CNAME flattening from completing. As a result, affected zones were mistakenly republished without the expected address records, causing resolution failures. Our team has resolved the underlying fault and is now republishing the affected zones with the correct records. We expect all zones to be fully operational within the hour. We will post a final update once service is confirmed fully restored.

  4. resolved Aug 28, 2026, 02:07 PM UTC

    The underlying issue has been fixed, and all affected DNS zones have been correctly republished. CNAME flattening is now functioning normally. In some cases, resolvers may have cached the earlier incorrect (empty) result. Where this happened, it can take a little longer for the correct records to reappear. How long depends on the negative caching settings configured for that specific zone, but this should resolve on its own without any action needed. We apologize for the disruption this caused and thank you for your patience.