Granicus incident

Granicus Issue Notification: govDelivery Communications Cloud-Communications Cloud 2FA Voice Authentication Issues

Major Resolved View vendor source →

Granicus experienced a major incident on September 16, 2026 affecting Communications Cloud, lasting 8h 38m. The incident has been resolved; the full update timeline is below.

Started
Sep 16, 2026, 04:53 PM UTC
Resolved
Sep 17, 2026, 01:31 AM UTC
Duration
8h 38m
Detected by Pingoru
Sep 16, 2026, 04:53 PM UTC

Affected components

Communications Cloud

Update timeline

  1. investigating Sep 16, 2026, 04:53 PM UTC

    We are currently investigating an issue affecting customers who use voice-call based two-factor authentication (2FA) within Communications Cloud. Impacted users may not receive their authentication phone call and could be unable to complete the login process. At this time, the issue appears to be limited to voice-call authentication. Users who authenticate using SMS-based 2FA are not expected to be impacted. Our engineering teams are actively investigating the issue and working to identify the root cause and restore normal service as quickly as possible.

  2. investigating Sep 16, 2026, 04:54 PM UTC

    We are currently investigating an issue affecting voice call delivery within Communications Cloud. Customers may experience delays or failures when receiving automated voice calls, including voice-based two-factor authentication (2FA) calls and other voice notification services. Our engineering teams are actively investigating the issue and working to identify the root cause and restore normal service as quickly as possible. Impact: Some customers may experience delayed or failed voice call delivery, which may affect voice-based authentication and other voice communication workflows.

  3. monitoring Sep 16, 2026, 07:34 PM UTC

    The issue affecting Communications Cloud voice-call delivery has been resolved. Customers may have experienced delays or failures receiving automated voice calls, including voice-based two-factor authentication (2FA) calls and other voice communication workflows. Our engineering teams investigated the issue, implemented corrective actions, and validated that voice-call delivery has been restored. Customers using voice-based 2FA should now be able to authenticate successfully. SMS-based authentication remained available throughout the incident. We will continue to monitor the service to ensure stability. We apologize for the inconvenience and appreciate your patience while we worked to resolve the issue.

  4. resolved Sep 17, 2026, 01:31 AM UTC

    This incident has been resolved.