Live / CorityOne / Incident
CorityOne: GX2 - Partial Interruption (AU2-0)
CorityOne · cority.comMajor incidentResolved2026-10-08 02:19 UTC
Public — what happened
Summary
CorityOne reported a major partial interruption to its GX2 service in the AU2-0 cluster, which it began looking into at 22:33 UTC on October 7, 2026. The company did not say which customers were affected or what caused the problem. By 01:15 UTC on October 8, CorityOne said it had put a fix in place and was watching how it performed, and the incident was marked resolved at 02:19.
Affected
GX2-AU2-0
Timeline
- Started — 2026-10-07 22:33 UTC
- Investigating — 2026-10-07 22:33 UTC
- Monitoring — 2026-10-08 01:15 UTC
- Resolved — 2026-10-08 02:19 UTC · 3h 45m 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 CorityOne 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 CorityOne: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the CorityOne report →
More from CorityOne
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.