Dialpad Outage History

Dialpad is up right now

Dialpad had 17 outages in the last 2 years totaling 96h 48m of downtime — averaging 0.7 incidents per month.

There were 17 Dialpad outages since June 30, 2025 totaling 96h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.dialpad.com

Minor June 11, 2026

Some customers in the US and Canada may be experience issues with delays in message delivery

Detected by Pingoru
Jun 11, 2026, 08:55 PM UTC
Resolved
Jun 11, 2026, 11:42 PM UTC
Duration
2h 46m
Affected: Carrier Networks: Messaging
Timeline · 4 updates
  1. investigating Jun 11, 2026, 08:55 PM UTC

    We are currently investigating this issue.

  2. identified Jun 11, 2026, 09:01 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 11, 2026, 09:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 11, 2026, 11:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 9, 2026

Some customers in the US and Canada may be experiencing issues with MMS messaging

Detected by Pingoru
Jun 09, 2026, 04:34 PM UTC
Resolved
Jun 09, 2026, 05:14 PM UTC
Duration
40m
Affected: Messaging
Timeline · 3 updates
  1. investigating Jun 09, 2026, 04:34 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 09, 2026, 05:03 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 09, 2026, 05:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 8, 2026

Some customers may be experiencing issues receiving inbound SMS messages

Detected by Pingoru
Jun 08, 2026, 10:43 PM UTC
Resolved
Jun 09, 2026, 01:53 AM UTC
Duration
3h 10m
Affected: Messaging
Timeline · 3 updates
  1. investigating Jun 08, 2026, 10:43 PM UTC

    We are currently investigating the issue.

  2. monitoring Jun 09, 2026, 01:02 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 09, 2026, 01:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 20, 2026

Some customers may be experiencing issues with IVR

Detected by Pingoru
May 20, 2026, 06:58 PM UTC
Resolved
May 21, 2026, 12:26 AM UTC
Duration
5h 28m
Affected: Omnichannel
Timeline · 8 updates
  1. investigating May 20, 2026, 06:58 PM UTC

    We are currently investigating this issue.

  2. investigating May 20, 2026, 07:36 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 20, 2026, 08:26 PM UTC

    We are currently investigating this issue.

  4. investigating May 20, 2026, 09:42 PM UTC

    We are currently investigating this issue.

  5. investigating May 20, 2026, 10:18 PM UTC

    We are currently investigating this issue.

  6. identified May 20, 2026, 11:33 PM UTC

    The issue has been identified and a fix is being implemented.

  7. monitoring May 20, 2026, 11:55 PM UTC

    A fix has been implemented and we are monitoring the results.

  8. resolved May 21, 2026, 12:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 4, 2026

Customers using Salesforce CTI with Dialpad may be experiencing issues with logging in

Detected by Pingoru
May 04, 2026, 03:11 PM UTC
Resolved
May 04, 2026, 06:17 PM UTC
Duration
3h 6m
Affected: Integrations
Timeline · 6 updates
  1. investigating May 04, 2026, 03:11 PM UTC

    We are currently investigating this issue.

  2. identified May 04, 2026, 03:19 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified May 04, 2026, 04:28 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified May 04, 2026, 05:29 PM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring May 04, 2026, 05:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved May 04, 2026, 06:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 8, 2026

We are investigating potential issues with calling

Detected by Pingoru
Apr 08, 2026, 07:17 PM UTC
Resolved
Apr 08, 2026, 09:18 PM UTC
Duration
2h 1m
Affected: Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
Timeline · 3 updates
  1. investigating Apr 08, 2026, 07:17 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 08, 2026, 07:44 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 08, 2026, 09:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 10, 2026

Some customers may be experiencing issues making or receiving calls.

Detected by Pingoru
Mar 10, 2026, 03:47 PM UTC
Resolved
Mar 12, 2026, 10:11 PM UTC
Duration
2d 6h
Affected: Telephony Infrastructure: Outbound CallsApplicationOmnichannelAnalyticsMessaging
Timeline · 5 updates
  1. investigating Mar 10, 2026, 03:47 PM UTC

    We are investigating a potential outage for some customers.

  2. investigating Mar 10, 2026, 04:30 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 10, 2026, 05:29 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Mar 10, 2026, 05:31 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Mar 12, 2026, 10:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 13, 2026

Some customers may be experiencing sporadic issues with placing or receiving calls

Detected by Pingoru
Feb 13, 2026, 04:39 PM UTC
Resolved
Feb 13, 2026, 05:31 PM UTC
Duration
52m
Affected: Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
Timeline · 3 updates
  1. investigating Feb 13, 2026, 04:39 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 13, 2026, 04:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 13, 2026, 05:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 13, 2026

Some customers may be experiencing delays in platform functions

Detected by Pingoru
Jan 13, 2026, 05:37 PM UTC
Resolved
Jan 13, 2026, 08:38 PM UTC
Duration
3h 1m
Affected: Telephony Infrastructure: Inbound CallsApplicationContact CenterOmnichannelAPI PlatformMessagingGoogle Cloud Platform
Timeline · 4 updates
  1. investigating Jan 13, 2026, 05:37 PM UTC

    Some customers may be experiencing intermittent issues affecting various platform functions, including inbound/outbound calling, message delivery, and agent status synchronization. Our engineering team is actively working on a resolution. In the meantime, agents can manually update their status by clicking the 'Refresh' button within the application.

  2. identified Jan 13, 2026, 05:52 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 13, 2026, 05:58 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 13, 2026, 08:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025

Accessing www.dialpad.com shows an error

Detected by Pingoru
Nov 18, 2025, 01:41 PM UTC
Resolved
Nov 18, 2025, 06:03 PM UTC
Duration
4h 21m
Affected: Website
Timeline · 3 updates
  1. identified Nov 18, 2025, 01:41 PM UTC

    The issue is due to a worldwide CloudFlare service incident: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7. Users can go directly to https://dialpad.com/login to sign in. Calling and messaging are unaffected.

  2. monitoring Nov 18, 2025, 02:01 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 18, 2025, 06:03 PM UTC

    The service is fully recovered.

Read the full incident report →

Minor September 30, 2025

Multiple analytics features are experiencing issues with loading

Detected by Pingoru
Sep 30, 2025, 07:28 PM UTC
Resolved
Sep 30, 2025, 09:27 PM UTC
Duration
1h 58m
Affected: Analytics
Timeline · 4 updates
  1. investigating Sep 30, 2025, 07:28 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 30, 2025, 07:29 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 30, 2025, 08:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 30, 2025, 09:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 2, 2025

Customers may be experiencing issues with workforce management

Detected by Pingoru
Jul 02, 2025, 04:56 PM UTC
Resolved
Jul 02, 2025, 05:41 PM UTC
Duration
45m
Affected: Workforce Management
Timeline · 5 updates
  1. investigating Jul 02, 2025, 04:56 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 02, 2025, 04:56 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 02, 2025, 05:01 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Jul 02, 2025, 05:16 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jul 02, 2025, 05:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 2, 2025

Some customers may be experiencing issues with contact centers

Detected by Pingoru
Jul 02, 2025, 03:39 PM UTC
Resolved
Jul 02, 2025, 05:56 PM UTC
Duration
2h 16m
Affected: Contact Center
Timeline · 6 updates
  1. investigating Jul 02, 2025, 03:39 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 02, 2025, 03:45 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 02, 2025, 04:09 PM UTC

    The issue is identified and we are working on a fix. If you are affected, please try this potential workaround: 1) Disable post-call wrap-up: https://help.dialpad.com/docs/post-call-wrap-up-time#enable-postcall-wrapup-time 2) A contact center supervisor should select the relevant contact center in the app and manually set each affected agents' status to Available

  4. monitoring Jul 02, 2025, 04:33 PM UTC

    A mitigation has been applied and operator status will be recovering over time. We will provide an update when fully recovered.

  5. monitoring Jul 02, 2025, 04:54 PM UTC

    Our mitigation has completed and operator status has recovered. We will continue to monitor.

  6. resolved Jul 02, 2025, 05:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 1, 2025

Some customers may be experiencing issues with calling

Detected by Pingoru
Jul 01, 2025, 04:43 PM UTC
Resolved
Jul 01, 2025, 11:37 PM UTC
Duration
6h 53m
Affected: Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound CallsMeetings
Timeline · 5 updates
  1. investigating Jul 01, 2025, 04:43 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 01, 2025, 04:43 PM UTC

    The incident appears to have started at 16:30 UTC (9:30am Pacific) and ended 3 minutes later. We are investigating.

  3. investigating Jul 01, 2025, 05:53 PM UTC

    We have not seen recurrence of the issue, but are continuing to investigate the root cause.

  4. monitoring Jul 01, 2025, 06:40 PM UTC

    We have identified the issue and have not seen recurrence. We will continue to monitor and root cause.

  5. resolved Jul 01, 2025, 11:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 30, 2025

Some customers may be experiencing issues with Dialpad Ai

Detected by Pingoru
Jun 30, 2025, 06:16 PM UTC
Resolved
Jun 30, 2025, 09:49 PM UTC
Duration
3h 32m
Affected: Dialpad Ai
Timeline · 4 updates
  1. investigating Jun 30, 2025, 06:16 PM UTC

    We are currently investigating this issue.

  2. identified Jun 30, 2025, 06:22 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 30, 2025, 09:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 30, 2025, 09:49 PM UTC

    This incident has been resolved.

Read the full incident report →