Live / OpenGov / Incident
OpenGov: TLS 1.2 Sign-in Errors
OpenGov · opengov.comMajor incidentResolved2026-10-28 11:51 UTC
Public — what happened
Summary
OpenGov reported an incident on its status page (rated major). It has been resolved.
Affected
Budgeting & Performance, #311, Reporting & Transparency, Government App Builder, Financials, OpenGov Platform, Grants Management, Procurement, Tax & Revenue (formerly iGovServices), Permitting & Licensing, Asset Management (formerly Cartegraph), Open Data, Community Feedback (formerly Open Town Hall), OpenGov Help Center, Utility Billing
Timeline
- Started — 2026-10-26 12:02 UTC
- Investigating — 2026-10-26 12:02 UTC (2 updates)
- Identified — 2026-10-26 14:30 UTC
- Monitoring — 2026-10-26 14:51 UTC (2 updates)
- Resolved — 2026-10-28 11:51 UTC · 47h 49m 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 OpenGov 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 OpenGov: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the OpenGov report →
More from OpenGov
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.