Granicus experienced a major incident on May 27, 2026 affecting Vision CMS, lasting 2h 11m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 27, 2026, 04:39 PM UTC
We are currently experiencing an intermittent issue affecting access to some sites. The Granicus Engineering team is actively working on mitigation and implementing fixes to stabilize the experience. As a helpful step, we recommend clearing your browser’s cache to avoid loading any previously cached error pages. This can often improve access while we continue working on a permanent fix. We understand the importance of reliable access and apologize for any inconvenience caused. We will continue to provide updates as progress is made.
- identified May 27, 2026, 05:00 PM UTC
Granicus engineering teams have implemented initial stabilization measures, and we are seeing positive improvements across affected services. Some users may still experience intermittent slowness or delays as mitigation efforts continue and systems fully stabilize. We remain actively engaged in resolving this issue and will provide further updates as progress is made. Thank you for your continued patience and understanding.
- monitoring May 27, 2026, 05:58 PM UTC
Granicus engineering teams have successfully implemented mitigation and stabilization measures, and services are now operating in a stable state. We have observed significant improvements across the previously impacted sites, with performance returning to normal and our monitoring indicates that the fix has been effective and the platform is stable. We will continue to closely monitor the environment to ensure sustained performance and quickly address any residual or emerging issues. Thank you for your patience and understanding while we worked through this.
- resolved May 27, 2026, 06:51 PM UTC
Monitoring confirms stability, and services have now returned to normal operation. We apologize for any inconvenience caused and thank you for your patience while we worked to resolve this issue.