Granicus Issue Notification: govDelivery Communications Cloud

Update timeline

1. investigating Apr 22, 2026, 12:23 PM UTC

   Granicus Engineering teams are currently investigating an issue impacting govDelivery Communications Cloud. Our teams are working on this issue as priority and further updates will be provided as soon as possible. Product: govDelivery Communications Cloud 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

2. investigating Apr 22, 2026, 12:57 PM UTC

   We are currently experiencing degraded bulletin delivery performance, and customers may encounter delays in bulletin sending. The Granicus Engineering team is actively investigating the issue and working to restore normal service. Further updates will be provided as additional information becomes available.

3. investigating Apr 22, 2026, 01:44 PM UTC

   The Granicus Engineering team continues to investigate the bulletin delivery issue. We are monitoring closely and working to restore normal service. Additional updates will be provided as progress is made.

4. identified Apr 22, 2026, 03:17 PM UTC

   We have identified the cause of the bulletin delivery degradation and are actively implementing a fix. Our teams are closely monitoring progress and will provide further updates as remediation continues.

5. identified Apr 22, 2026, 09:25 PM UTC

   We have identified a likely primary cause of the bulletin delivery delays and, through continued review, found additional contributing factors. Our teams are actively addressing these items while working toward a permanent solution to restore and stabilize normal service. Progress is being closely monitored, and further updates will be provided as remediation continues.

6. investigating Apr 22, 2026, 10:55 PM UTC

   Our Incident response team has upgraded this incident from a sev2 to a sev1. After further investigation and deeper inspection of system logs, we understand that this issue is affecting a broader group of customers than initially anticipated. We sincerely apologize for the impact this has caused. Our teams are continuing to work on this issue with urgency toward a full and lasting resolution. We will continue to provide updates as progress is made.

7. investigating Apr 23, 2026, 02:46 AM UTC

   The scheduled maintenance has been completed but did not resolve the issue. We continue to treat this matter with the highest priority and are working closely with our engineering teams and vendor to identify a permanent solution. We sincerely apologize for the continued impact this has caused. Our teams remain fully engaged and are working with urgency toward a full and lasting resolution. Additional updates will be provided as progress is made.

8. identified Apr 23, 2026, 09:26 AM UTC

   We are currently operating within an emergency maintenance window, during which the application has been temporarily taken offline to facilitate required recovery activities. Our teams are actively coordinating with the vendor to restore services at the earliest possible opportunity. We will continue to share updates on progress, with the next update expected in approximately one hour.

9. identified Apr 23, 2026, 10:31 AM UTC

   Our teams are actively engaged and working closely with the vendor to progress resolution and restore services as quickly and safely as possible. While full service has not yet been restored, efforts are ongoing and closely monitored. We will provide the next update in approximately one hour. We sincerely apologize for the continued disruption and appreciate your continued cooperation during this time.

10. identified Apr 23, 2026, 11:29 AM UTC

    Our teams have identified a fix, and recovery efforts are progressing at a good pace. Implementation is currently underway and being closely monitored. We are hopeful to share a positive update within the next hour and will continue to keep you informed. We apologize for the continued disruption and appreciate your cooperation during this time.

11. monitoring Apr 23, 2026, 12:18 PM UTC

    The identified fix has been successfully implemented, and services are functioning as expected. Our teams will continue to closely monitor the application to ensure stability and address any residual issues. We appreciate your cooperation and understanding during this time.

12. resolved Apr 23, 2026, 10:10 PM UTC

    This incident has been resolved.