Live / CorityOne / Incident
CorityOne: GX2 - Degraded Performance (US2-2)
CorityOne · cority.comMinor incidentResolved2026-11-05 18:28 UTC
Public — what happened
Summary
CorityOne said it began looking into a problem on 5 November 2026 at 16:11 UTC that was causing degraded performance for its GX2 service in the US2-2 cluster, which it classed as minor. The company said its team was working to find the underlying reason, and the text it provided did not name a cause. The incident is marked resolved as of 18:28 UTC the same day.
Affected
GX2-US2-2
Timeline
- Started — 2026-11-05 16:11 UTC
- Investigating — 2026-11-05 16:11 UTC
- Resolved — 2026-11-05 18:28 UTC · 2h 16m 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.