- Level
- confirmed
- Worst impact
- Degraded
- Components
- Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls
- Regions
- us
What to do
Check whether you use Dialpad Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls in us. 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 19m it lasted.
Anything that failed between 2026-09-15 16:08 UTC and 2026-09-15 16:27 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 3
- monitoring
Network issue in the midwest US impacted some new and existing calls in the region. The incident lasted approximately 6 minutes and traffic has been successfully rerouted.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-c2f85c8a12
Is Dialpad still down?
No, this incident was resolved 2026-09-15 16:27 UTC. For Dialpad's live state, see https://down.guide/dialpad.
How long did it last?
19m, from 2026-09-15 16:08 UTC to 2026-09-15 16:27 UTC, by the times Dialpad posted.
What was affected?
Dialpad named Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls in us.
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.