Dialpad incident

Some customers may be experiencing issues making or receiving calls.

Major Resolved View vendor source →

Dialpad experienced a major incident on October 20, 2026 affecting Telephony Infrastructure: Inbound Calls and Telephony Infrastructure: Outbound Calls, lasting 7h 36m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2026, 01:44 AM UTC
Resolved
Oct 20, 2026, 09:21 AM UTC
Duration
7h 36m
Detected by Pingoru
Oct 20, 2026, 01:44 AM UTC

Affected components

Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls

Update timeline

  1. investigating Oct 20, 2026, 01:44 AM UTC

    We are investigating a potential outage for some customers.

  2. investigating Oct 20, 2026, 02:18 AM UTC

    We are continuing to investigate the issue. Next update in 30 minutes.

  3. investigating Oct 20, 2026, 02:45 AM UTC

    We are continuing to investigate this issue. Our engineering team is actively working on a resolution. Next update within 30 minutes.

  4. investigating Oct 20, 2026, 03:16 AM UTC

    We are continuing to investigate this issue. Our engineering team is actively working on a resolution. Next update within 30 minutes.

  5. investigating Oct 20, 2026, 03:46 AM UTC

    Our engineering team is currently testing a potential fix. We will provide an update within the next 30 minutes.

  6. investigating Oct 20, 2026, 04:16 AM UTC

    We are continuing to test the fix. Next update within 30 minutes.

  7. identified Oct 20, 2026, 04:54 AM UTC

    The issue has been identified and service is starting to recover with the fix. We are currently working on full recovery. Next update in 30 minutes.

  8. monitoring Oct 20, 2026, 05:17 AM UTC

    A fix has been implemented and we are monitoring the results.

  9. investigating Oct 20, 2026, 07:28 AM UTC

    Customers are still experiencing issues on some types of devices and the engineering team is continuing their investigation.

  10. monitoring Oct 20, 2026, 08:57 AM UTC

    A fix has been implemented and we are monitoring the results.

  11. resolved Oct 20, 2026, 09:21 AM UTC

    This incident has been resolved.