Investigating degraded calling performance for some EU numbers and destinations

What to do

• Check whether you use Dialpad Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls, Carrier Networks: Local Numbers in eu. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 42m it lasted.

  Anything that failed between 2026-09-03 09:54 UTC and 2026-09-03 10:36 UTC may need a replay.

• Subscribe to Dialpad's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=dialpad works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Dialpad 6

1. investigatingSep 3, 2026, 9:54 AM UTC

   We are currently investigating this issue.

   provider

2. investigatingSep 3, 2026, 10:06 AM UTC

   We are continuing to investigate this issue.

   provider

3. investigatingSep 3, 2026, 10:12 AM UTC

   We are continuing to investigate this issue.

   provider

4. identifiedSep 3, 2026, 10:19 AM UTC

   The issue has been identified with a telephony carrier. Outbound calling has been routed around the problematic carrier, but inbound calls could still be impacted.

   provider

5. monitoringSep 3, 2026, 10:27 AM UTC

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

   provider

6. resolvedSep 3, 2026, 10:36 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.