Live / FCDC / Incident
FCDC: PingOne Issues
FCDC · franklincountyohio.govMajor incidentResolved2026-10-06 22:48 UTC
Public — what happened
Summary
FCDC said it began looking into reports of problems with PingOne at 16:20 UTC on October 6, 2026, and rated the incident as major. About 17 minutes later, the company said the trouble came from its provider, PingOne, and affected every global region. By 18:00 UTC FCDC reported that PingOne's US region appeared to be coming back and that its own tests looked good, but at 19:03 UTC it said some disruption had returned in the US. FCDC marked the incident resolved at 22:48 on the same day.
Affected
Ping Identity PingID Authenticator
Timeline
- Started — 2026-10-06 16:20 UTC
- Investigating — 2026-10-06 16:20 UTC
- Identified — 2026-10-06 16:37 UTC (2 updates)
- Monitoring — 2026-10-06 18:00 UTC (2 updates)
- Resolved — 2026-10-06 22:48 UTC · 6h 28m 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 FCDC 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 FCDC: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the FCDC report →
More from FCDC
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.