Dialpad change history

Dialpad reported a major partial service disruption affecting Telephony Infrastructure: Inbound Calls, starting 2026-09-01 15:25 UTC and resolved at 2026-09-01 20:02 UTC, lasting 4 h 36 min. Dialpad stated that a fix was implemented but did not specify the cause or fix details.

Some Dialpad customers in the US and Canada experienced MMS messaging issues in a major-impact incident from 2026-06-09 16:34 UTC to 2026-06-09 17:14 UTC, lasting 40 min. Dialpad implemented a fix and confirmed resolution.

Dialpad reported a major Omnichannel incident affecting IVR for some customers, starting 2026-05-20 18:58 UTC and resolved 2026-05-21 00:26 UTC, lasting 5 h 28 min. A fix was implemented and monitored; no cause was stated.

Dialpad reported a major incident affecting inbound and outbound calls starting 2026-04-08 19:17 UTC. A fix was implemented by 2026-04-08 19:44 UTC, and the incident was resolved at 2026-04-08 21:18 UTC after 2 h 1 min.

Dialpad reported a major website outage showing errors at www.dialpad.com, starting 2025-11-18 13:41 UTC and resolved 2025-11-18 18:03 UTC (4 h 21 min). Dialpad attributed it to a worldwide CloudFlare service incident; a fix was implemented and service fully recovered. Calling and messaging were unaffected, and users could sign in directly at https://dialpad.com/login.

Dialpad reported a major Workforce Management outage from 2025-07-02 16:56 UTC to 2025-07-02 17:41 UTC, lasting 45 min. Customers may have experienced issues with workforce management; a fix was implemented at 17:16 UTC, and the incident was subsequently resolved.

Dialpad reported a major Contact Center incident affecting some customers and operator status, starting 2025-07-02 15:39 UTC and resolved at 2025-07-02 17:56 UTC (2 h 16 min). Dialpad advised disabling post-call wrap-up and manually setting affected agents to Available; a mitigation restored operator status.

Dialpad reported a critical outage affecting calls, meeting access, messaging and logins, citing a widespread Google Cloud outage. It started at 2025-06-12 18:09 UTC and was resolved at 2025-06-12 21:57 UTC, lasting 3 h 47 min; Dialpad reported implementing a fix and monitoring recovery.

Dialpad reported a major Analytics degradation causing delays in some dashboards for some customers, from 2025-06-12 15:19 UTC to 2025-06-12 18:07 UTC, lasting 2 h 48 min. A fix was implemented by 2025-06-12 16:01 UTC, followed by monitoring and resolution.

Some Dialpad customers had trouble accessing the Workforce Management administration page during a major-impact incident from 2025-06-10 18:36 UTC to 2025-06-10 22:22 UTC, lasting 3 h 45 min. Dialpad implemented a fix and monitored results before resolving the incident.

Some Dialpad customers experienced calling and messaging issues in a major-impact Application incident starting 2025-05-21 14:42 UTC and lasting 48 min, resolved at 2025-05-21 15:30 UTC. Dialpad implemented a fix and confirmed normal Support contact channels were operational at resolution.

Dialpad reported a major outage affecting calling, messaging and meetings for some customers, starting 2025-05-20 15:32 UTC and resolved at 2025-05-20 16:51 UTC; the reported duration was 1 h 18 min. A fix was implemented at 16:06 UTC, and normal support channels were confirmed operational at 16:15 UTC.

Dialpad reported a major degradation affecting some inbound and outbound calls in North America. The incident started at 2025-05-09 17:31 UTC and was resolved at 2025-05-09 17:50 UTC, lasting 19 min; Dialpad stated calls were impacted between 16:20 and 16:46 UTC and a fix had been implemented.

Dialpad reported a major incident affecting calls or meetings for some customers in Australia and New Zealand, including inbound and outbound calls. It started at 2025-04-11 06:26 UTC and was resolved at 2025-04-11 07:11 UTC; the computed duration was 44 min. A fix was implemented, but no cause was stated.