Live / Azion / Incident
Azion: Delayed configuration propagation to edge nodes
Azion · azion.comMinor incidentResolved2026-10-05 21:05 UTC
Public — what happened
Summary
Azion reported that changes to configurations were taking longer than usual to reach its edge nodes, starting at 19:46 UTC on 2026-10-05, and rated the issue as minor. The company said content delivery was unaffected and that previously set configurations kept being served as normal. Azion said it found the problem by 19:53 UTC, had a fix in place by 19:57 UTC, and marked the incident resolved at 21:05 after a period of monitoring; it did not describe the cause.
Affected
Orchestrator
Timeline
- Started — 2026-10-05 19:46 UTC
- Investigating — 2026-10-05 19:46 UTC
- Identified — 2026-10-05 19:53 UTC
- Monitoring — 2026-10-05 19:57 UTC
- Resolved — 2026-10-05 21:05 UTC · 1h 19m 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.