Dialpad: Some customers may be experiencing issues with devices.

What to do

Check whether you use Dialpad Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls. 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 6h 5m it lasted.
Anything that failed between 2026-10-20 15:49 UTC and 2026-10-20 21:54 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.

investigatingOct 20, 2026, 3:49 PM UTC
We believe the issue is primarily impacting customers whose networks have trouble with large DNS records or those using Grandstream ATA devices. Our team is working on a resolution. We will update when it is resolved.
provider
monitoringOct 20, 2026, 4:38 PM UTC
A fix has been implemented and we are monitoring the results.
provider
monitoringOct 20, 2026, 8:22 PM UTC
We've resolved issues for most customers by now.
provider
resolvedOct 20, 2026, 9:54 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Dialpad still down?

No, this incident was resolved 2026-10-20 21:54 UTC. For Dialpad's live state, see https://down.guide/dialpad.

How long did it last?

6h 5m, from 2026-10-20 15:49 UTC to 2026-10-20 21:54 UTC, by the times Dialpad posted.

What was affected?

Dialpad named Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls.

What caused it?

Dialpad hasn't published a root cause. If it does, it shows here.

Where does this come from?

Dialpad's official status page, https://status.dialpad.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.