Live  /  Dialpad  /  Incident

Dialpad: Some customers may be experiencing issues with devices.

Dialpad · dialpad.comMinor incidentResolved2026-10-20 20:22 UTC
Public — what happened

Summary

Dialpad reported that some customers were having problems with their devices, starting at 15:49 UTC on 2026-10-20, which it rated as minor. The company said it believed the trouble mainly affected customers whose networks struggle with large DNS records, along with those using Grandstream ATA devices. At 16:38 UTC it said a fix had been put in place and was being watched, and by 20:22 UTC it said most customers' problems had been resolved. The incident was still listed as monitoring and not fully resolved.

Affected

Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls

As listed on Dialpad’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Dialpad status & history page.

Related: Dialpad status & history. SquidGrid is not affiliated with Dialpad.