Live / CorityOne / Incident
CorityOne: GX2 - Degraded Performance (US2-0)
CorityOne · cority.comMinor incidentResolved2026-11-02 21:39 UTC
Public — what happened
Summary
CorityOne said its GX2 service in the US2-0 cluster was running with degraded performance, and it classed the issue as minor. The company began investigating at 20:14 UTC on 2026-11-02, marked the issue as identified at 20:32, and moved to monitoring at 21:18. Its updates repeated the same wording about investigating and did not name a cause. CorityOne marked the incident resolved at 21:39 UTC.
Affected
GX2-US2-0
Timeline
- Started — 2026-11-02 20:14 UTC
- Investigating — 2026-11-02 20:14 UTC
- Identified — 2026-11-02 20:32 UTC
- Monitoring — 2026-11-02 21:18 UTC
- Resolved — 2026-11-02 21:39 UTC · 1h 25m 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.