OpenGov incident

TLS 1.2 Sign-in Errors

Resolved after 1 day 23 hours, affecting Budgeting & Performance and Reporting & Transparency and 1 more, on October 26, 2026.

resolved Oct 28, 2026, 11:51 AM UTC

This has been resolved, and users are able to sign in normally. The errors involved a third-party service OpenGov uses for sign-in, and we are working with that provider to help prevent a recurrence.

Started
Oct 26, 2026, 12:02 PM UTC
Resolved
Oct 28, 2026, 11:51 AM UTC
Duration
1d 23h
Detected by Pingoru
Oct 26, 2026, 12:02 PM UTC

Affected components

Budgeting & PerformanceReporting & TransparencyFinancialsOpenGov PlatformProcurementTax & Revenue (formerly iGovServices)Permitting & LicensingAsset Management (formerly Cartegraph)Open DataCommunity Feedback (formerly Open Town Hall)

Update timeline

  1. investigating Oct 26, 2026, 12:02 PM UTC

    Some users may see an error mentioning "TLS 1.2" when signing in to OpenGov products, including Control Panel, Permitting & Licensing, Government App Builder, and Procurement. Our team is actively investigating and working on a fix. We will post updates here as we learn more.

  2. investigating Oct 26, 2026, 01:05 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 26, 2026, 02:30 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Oct 26, 2026, 02:51 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Oct 26, 2026, 03:38 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Oct 28, 2026, 11:51 AM UTC

    This has been resolved, and users are able to sign in normally. The errors involved a third-party service OpenGov uses for sign-in, and we are working with that provider to help prevent a recurrence.

Your product runs on more than OpenGov

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →