Live  /  CorityOne  /  Incident

CorityOne: Incident

CorityOne · cority.comMinor incidentResolved2026-10-20 15:10 UTC
Public — what happened

Summary

CorityOne reported a minor incident affecting its Core GX2 (US2-0) environment, which it began investigating at 14:13 UTC on 2026-10-20. The company said its team was working to find the cause. By 14:37 UTC it said service performance was back to expected levels and it was monitoring to make sure things stayed stable. The incident was marked resolved at 15:10, and CorityOne did not state a cause in the text provided.

Affected

GX2-US2-0

As listed on CorityOne’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the CorityOne status & history page.

Related: CorityOne status & history. SquidGrid is not affiliated with CorityOne.