Live / CorityOne / Incident
CorityOne: Incident
CorityOne · cority.comMinor incidentResolved2026-11-02 17:26 UTC
Public — what happened
Summary
CorityOne reported a minor incident beginning at 16:46 UTC on 2026-11-02 that affected its Core product (previously called GX2), specifically the US2-2 environment. The company said its team was looking into the problem and had not yet determined a cause. The incident is now marked resolved as of 17:26, though the text provided does not say what was done to fix it.
Affected
GX2-US2-2
Timeline
- Started — 2026-11-02 16:46 UTC
- Investigating — 2026-11-02 16:46 UTC
- Resolved — 2026-11-02 17:26 UTC · 40 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.