Live / Azion / Incident
Azion: Increased latency for some domains using ANAME records
Azion · azion.comMinor incidentResolved2026-10-11 00:30 UTC
Public — what happened
Summary
Azion said that starting at 21:26 UTC on October 10, 2026, some domains relying on ANAME records at the root of their zone saw slower response times, with certain requests possibly handled by edge locations outside the region they should have come from. The company noted that other kinds of DNS records were unaffected and its edge locations were otherwise working normally. Azion reported finding the problem at 22:02 UTC without describing a cause, put a fix in place by 00:15 UTC on October 11, and marked the incident resolved at 00:30.
Affected
Edge DNS
Timeline
- Started — 2026-10-10 21:26 UTC
- Investigating — 2026-10-10 21:26 UTC
- Identified — 2026-10-10 22:02 UTC
- Monitoring — 2026-10-11 00:15 UTC
- Resolved — 2026-10-11 00:30 UTC · 3h 04m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Azion against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Azion: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Azion report →
More from Azion
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.