Live / CorityOne / Incident
CorityOne: Core (GX2) - Degraded Performance
CorityOne · cority.comMinor incidentResolved2026-11-09 15:40 UTC
Public — what happened
Summary
CorityOne said it began investigating a minor problem with its GX2 Core service in the EU1-0 cluster at 10:46 UTC on 2026-11-09. By 13:41 UTC the company said all GX2 Core environments were affected, and customers could see slowness, timeouts or errors in the application. It reported at 14:51 UTC that the issue had been identified and that it was working on a fix, and at 15:13 UTC said performance was back to expected levels while it monitored. The incident was marked resolved at 15:40 UTC.
Affected
GX2-US2-1, GX2-US2-2, GX2-US2-0, GX2-CA1-0, GX2-CA1-1, GX2-CA1-2, GX2-EU1-0, GX2-EU1-1, GX2-UK2-0, GX2-AU2-0, GX2-US1-0, GX2-EUW2-0
Timeline
- Started — 2026-11-09 10:46 UTC
- Investigating — 2026-11-09 10:46 UTC (3 updates)
- Identified — 2026-11-09 14:51 UTC
- Monitoring — 2026-11-09 15:13 UTC
- Resolved — 2026-11-09 15:40 UTC · 4h 54m 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 47, 2026, our weekly internet health report.