Granicus incident
Granicus Issue Notification: govMeetings OneMeeting PrimeGov
Granicus experienced a major incident on September 29, 2026 affecting OneMeeting PrimeGov, lasting 2h 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 29, 2026, 04:29 PM UTC
Granicus Engineering teams are currently investigating an issue impacting govMeetings OneMeeting PrimeGov. Our teams are working on this issue as priority and further updates will be provided as soon as possible. Product: govMeetings OneMeeting PrimeGov 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.
- investigating Sep 29, 2026, 04:51 PM UTC
We are currently investigating a service disruption affecting portions of the OneMeeting platform. Customers may experience slow page loads, delays when accessing meeting content, or issues connecting to certain application features. Our Engineering, Infrastructure, and Support teams are actively working to identify the root cause and restore normal service as quickly as possible. We understand the impact this may have on your operations and will continue to provide updates through our Status Page as additional information becomes available. Thank you for your patience while we work to resolve the issue.
- monitoring Sep 29, 2026, 06:48 PM UTC
We have identified and mitigated the issue affecting portions of the OneMeeting platform. Customers may have experienced slow page loads, connection failures, prolonged loading screens, or difficulty accessing meeting-related functionality. Our teams identified a service capacity issue affecting backend connectivity and implemented corrective actions to restore normal operations. Service functionality has recovered and we are actively monitoring the environment to ensure stability. Users who continue experiencing loading issues may need to refresh their browser session. We will continue monitoring and provide additional updates as necessary.
- resolved Sep 29, 2026, 06:49 PM UTC
This incident has been resolved.