Live / CorityOne / Incident
CorityOne: GX2 - Degraded Performance
CorityOne · cority.comMinor incidentResolved2026-11-03 18:39 UTC
Public — what happened
Summary
CorityOne said its GX2 service was running with degraded performance, which it rated as a minor issue. The company began investigating at 15:35 UTC on 2026-11-03 and reported at 15:46 UTC that it had identified the problem and was working on fixes. By 15:48 UTC it said performance was back to expected levels and it was monitoring for stability, and the incident was marked resolved at 18:39. CorityOne did not describe the cause or say which customers were affected.
Affected
GX2-CA1-2
Timeline
- Started — 2026-11-03 15:35 UTC
- Investigating — 2026-11-03 15:35 UTC (2 updates)
- Identified — 2026-11-03 15:46 UTC
- Monitoring — 2026-11-03 15:48 UTC
- Resolved — 2026-11-03 18:39 UTC · 3h 03m 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.