Live / CorityOne / Incident
CorityOne: Core to MyCority - Certificate Update
CorityOne · cority.comMinor incidentResolved2026-11-12 21:24 UTC
Public — what happened
Summary
CorityOne said it carried out maintenance to renew an internal security certificate used to connect its Core and MyCority products, and rated the issue as minor. The company said users might briefly be interrupted when moving from Core to MyCority while the work was underway. The notice was posted at 20:51 UTC on 2026-11-12, and the company marked it resolved at 21:24.
Affected
GX2-AU2-0, MyCority-AU2-0
Timeline
- Started — 2026-11-12 20:51 UTC
- Identified — 2026-11-12 20:51 UTC
- Resolved — 2026-11-12 21:24 UTC · 33 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 47, 2026, our weekly internet health report.