Dialpad Outage History
23 incidents recorded over the last 365 days, 23 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Dialpad Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 4, 2026 | Some customers may be experiencing degraded performance with AI agents.This incident has been resolved. | 27 min | Resolved |
| Nov 2, 2026 | Service degradation affecting Dialpad AI Voice and Text AgentsThis incident has been resolved. | 1h 31m | Resolved |
| Oct 20, 2026 | Some customers may be experiencing issues with devices.This incident has been resolved. | 6h 5m | Resolved |
| Oct 20, 2026 | Some customers may be experiencing issues making or receiving calls.This incident has been resolved. | 7h 36m | Resolved |
| Sep 23, 2026 | Service degradation affecting some IVR CustomersThis incident has been resolved. | 45 min | Resolved |
| Sep 15, 2026 | Some users with US toll-free or midwest toll numbers may have had trouble with new or ongoing callsThis incident has been resolved. | 18 min | Resolved |
| Sep 3, 2026 | Investigating degraded calling performance for some EU numbers and destinationsThis incident has been resolved. | 42 min | Resolved |
| Sep 1, 2026 | Partial service disruptionThis incident has been resolved. | 4h 36m | Resolved |
| Aug 21, 2026 | Some contact center agents may be experiencing issues with being unable to complete a call wrap-upThis incident has been resolved. | 48 min | Resolved |
| Jul 28, 2026 | Some customers may be experiencing errors using the fax APIThis incident has been resolved. | 28 min | Resolved |
| Jul 7, 2026 | Some customers may be experiencing degraded performance with IVR callsThis incident has been resolved. | 1h 24m | Resolved |
| Jun 30, 2026 | Inbound/Outbound Calling Potentially ImpactedThis incident has been resolved. | 6h 15m | Resolved |
| Jun 11, 2026 | Some customers in the US and Canada may be experience issues with delays in message deliveryThis incident has been resolved. | 2h 46m | Resolved |
| Jun 9, 2026 | Some customers in the US and Canada may be experiencing issues with MMS messagingThis incident has been resolved. | 40 min | Resolved |
| Jun 8, 2026 | Some customers may be experiencing issues receiving inbound SMS messagesThis incident has been resolved. | 3h 10m | Resolved |
| May 20, 2026 | Some customers may be experiencing issues with IVRThis incident has been resolved. | 5h 28m | Resolved |
| May 4, 2026 | Customers using Salesforce CTI with Dialpad may be experiencing issues with logging inThis incident has been resolved. | 3h 6m | Resolved |
| Apr 8, 2026 | We are investigating potential issues with callingThis incident has been resolved. | 2h 1m | Resolved |
| Mar 10, 2026 | Some customers may be experiencing issues making or receiving calls.This incident has been resolved. | 54h 23m | Resolved |
| Feb 13, 2026 | Some customers may be experiencing sporadic issues with placing or receiving callsThis incident has been resolved. | 52 min | Resolved |
| Feb 12, 2026 | Some customers may be experiencing sporadic issues with placing or receiving callsThis incident has been resolved. | 1h 4m | Resolved |
| Jan 13, 2026 | Some customers may be experiencing delays in platform functionsThis incident has been resolved. | 3h 1m | Resolved |
| Nov 18, 2025 | Accessing www.dialpad.com shows an errorThe service is fully recovered. | 4h 21m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Dialpad incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Dialpad Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Dialpad acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Dialpad outage in this window ran 2d 6h, against a mean recovery of 4h 52m. If you depend on Dialpad in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.