Live / CorityOne / Incident
CorityOne: GX2 - Degraded Performance (CA1-0, EU1-1, US2-2)
CorityOne · cority.comMinor incidentResolved2026-11-02 21:57 UTC
Public — what happened
Summary
CorityOne reported degraded performance affecting its GX2 service in the CA1-0, EU1-1 and US2-2 clusters, which it classed as minor. The company said it began investigating at 21:26 UTC on 2026-11-02 and that its team was working to find the root cause. The incident was marked resolved at 21:57, and the text provided does not say what caused it or what was done to fix it.
Affected
GX2-US2-2
Timeline
- Started — 2026-11-02 21:26 UTC
- Investigating — 2026-11-02 21:26 UTC
- Resolved — 2026-11-02 21:57 UTC · 32 min 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 46, 2026, our weekly internet health report.