Granicus experienced a major incident on October 9, 2026 affecting GovQA, lasting 9h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 09, 2026, 01:31 PM UTC
Granicus Engineering teams are currently investigating an issue impacting govService GovQA. Our teams are working on this issue as priority and further updates will be provided as soon as possible. Product: govService GovQA Updates on this issue will continue to be provided on Status.Granicus.com, for other issues or questions please contact us at Support.Granicus.com. Thank you, Granicus Customer Support
- investigating Oct 09, 2026, 02:07 PM UTC
Granicus Engineering teams remain engaged in investigating the issue impacting several GovQA Admin and Public Portal monitors, which continue to experience intermittent failures and recovery events. While some services have stabilised following workaround mitigation activities, intermittent portal outages are still being observed. The next update will be provided in an hour.
- identified Oct 09, 2026, 05:25 PM UTC
Recent mitigation and diagnostic efforts have resulted in improved application responsiveness, and teams are observing increased service stability across previously impacted environments. Customer-facing services are responding more consistently; however, intermittent latency and degraded performance may still occur while the investigation remains active. Engineering teams continue to monitor service health and analyze Azure infrastructure and platform components to identify the underlying cause and determine a permanent remediation.
- monitoring Oct 09, 2026, 06:22 PM UTC
Engineering teams have implemented corrective actions and are observing sustained improvement across GovQA Admin and Public Portal services. Service responsiveness has returned to expected levels, monitoring checks remain healthy, and customer impact has significantly reduced. Teams will continue monitoring the environment to confirm long-term stability before considering incident closure.
- resolved Oct 09, 2026, 10:35 PM UTC
This incident has been resolved.