Live / Azion / Incident
Azion: Performance Issues in Edge Orchestration
Azion · azion.comMinor incidentResolved2026-10-08 19:40 UTC
Public — what happened
Summary
Azion said its Edge Orchestration platform ran into performance problems starting at 17:49 UTC on 2026-10-08, which could make changes to Azion products through the Console, CLI or API slow down or fail. The company stated that services reached by end users kept working normally and that only the handling of new configuration changes was affected. Azion reported finding the problem the same minute it began investigating, put a fix in place by 19:11 UTC, and marked the incident resolved at 19:40.
Affected
Orchestrator
Timeline
- Started — 2026-10-08 17:49 UTC
- Investigating — 2026-10-08 17:49 UTC
- Identified — 2026-10-08 17:49 UTC
- Monitoring — 2026-10-08 19:11 UTC
- Resolved — 2026-10-08 19:40 UTC · 1h 51m 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.