Live / CorityOne / Incident
CorityOne: Incident
CorityOne · cority.comMinor incidentResolved2026-10-21 20:32 UTC
Public — what happened
Summary
CorityOne reported a minor incident affecting its Core service in the CA1-1 environment, which it began investigating at 18:27 UTC on 2026-10-21. The company said its team was working to find the cause, and it did not say who was affected or give any further details in the text provided. The incident is marked resolved as of 20:32 UTC the same day, though CorityOne did not state a cause or describe a fix.
Affected
GX2-CA1-1
Timeline
- Started — 2026-10-21 18:27 UTC
- Investigating — 2026-10-21 18:27 UTC
- Resolved — 2026-10-21 20:32 UTC · 2h 05m 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 44, 2026, our weekly internet health report.