Live / CorityOne / Incident
CorityOne: GX2 - Degraded Performance (US2-2)
CorityOne · cority.comResolved2026-10-15 17:22 UTC
Public — what happened
Summary
CorityOne reported slower-than-normal performance in its GX2 service on the US2-2 cluster starting at 15:39 UTC on October 15, 2026. The company said it was looking into the problem but did not share a cause. By 16:39 UTC, CorityOne said performance was back to normal and it was watching the system for stability, and the incident was marked resolved at 17:22.
Affected
GX2-US2-2
Timeline
- Started — 2026-10-15 15:39 UTC
- Investigating — 2026-10-15 15:39 UTC
- Monitoring — 2026-10-15 16:39 UTC
- Resolved — 2026-10-15 17:22 UTC · 1h 43m 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 43, 2026, our weekly internet health report.