Live / CorityOne / Incident
CorityOne: GX2 - Degraded Performance (US2-0)
CorityOne · cority.comMinor incidentResolved2026-10-26 20:53 UTC
Public — what happened
Summary
CorityOne said its GX2 service in the US2-0 cluster was running with degraded performance, which it classed as a minor issue. The company began investigating at 18:26 UTC on 2026-10-26. By 19:22 UTC it said the problem had been identified and that its team was working on steps to restore normal service. The incident was marked resolved at 20:53 UTC.
Affected
GX2-US2-0
Timeline
- Started — 2026-10-26 18:26 UTC
- Investigating — 2026-10-26 18:26 UTC
- Identified — 2026-10-26 19:22 UTC
- Resolved — 2026-10-26 20:53 UTC · 2h 27m 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 45, 2026, our weekly internet health report.