Live / Dialpad / Incident
Dialpad: Some customers may be experiencing issues making or receiving calls.
Dialpad · dialpad.comMajor incidentResolved2026-10-20 09:21 UTC
Public — what happened
Summary
Dialpad said some customers might have trouble making or receiving calls, and it began investigating a possible outage at 01:44 UTC on 2026-10-20. Over the next few hours the company said its engineers worked on the problem and tested a fix, and at 04:54 UTC it said the issue had been identified and service was starting to recover. After reporting a fix at 05:17 UTC, Dialpad said at 07:28 UTC that customers on some types of devices were still affected and investigation continued. The incident is marked resolved as of 09:21 UTC.
Affected
Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls
Timeline
- Started — 2026-10-20 01:44 UTC
- Investigating — 2026-10-20 01:44 UTC (6 updates)
- Identified — 2026-10-20 04:54 UTC
- Monitoring — 2026-10-20 05:17 UTC
- Investigating — 2026-10-20 07:28 UTC
- Resolved — 2026-10-20 09:21 UTC · 7h 37m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Dialpad against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Dialpad: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Dialpad report →
More from Dialpad
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.