- Detected by Pingoru
- Jun 30, 2026, 11:23 PM UTC
- Resolved
- Jul 01, 2026, 05:38 AM UTC
- Duration
- 6h 15m
Affected: Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound Calls
Timeline · 3 updates
-
investigating Jun 30, 2026, 11:23 PM UTC
We are investigating a potential impairment with calling.
-
monitoring Jun 30, 2026, 11:54 PM UTC
A fix has been applied. Calling operations returned to normal.
-
resolved Jul 01, 2026, 05:38 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jun 11, 2026, 08:55 PM UTC
We are currently investigating this issue.
-
identified Jun 11, 2026, 09:01 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 11, 2026, 09:40 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 11, 2026, 11:42 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jun 09, 2026, 04:34 PM UTC
We are currently investigating this issue.
-
monitoring Jun 09, 2026, 05:03 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 09, 2026, 05:14 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jun 08, 2026, 10:43 PM UTC
We are currently investigating the issue.
-
monitoring Jun 09, 2026, 01:02 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 09, 2026, 01:53 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating May 20, 2026, 06:58 PM UTC
We are currently investigating this issue.
-
investigating May 20, 2026, 07:36 PM UTC
We are continuing to investigate this issue.
-
investigating May 20, 2026, 08:26 PM UTC
We are currently investigating this issue.
-
investigating May 20, 2026, 09:42 PM UTC
We are currently investigating this issue.
-
investigating May 20, 2026, 10:18 PM UTC
We are currently investigating this issue.
-
identified May 20, 2026, 11:33 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 20, 2026, 11:55 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 21, 2026, 12:26 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating May 04, 2026, 03:11 PM UTC
We are currently investigating this issue.
-
identified May 04, 2026, 03:19 PM UTC
The issue has been identified and a fix is being implemented.
-
identified May 04, 2026, 04:28 PM UTC
We are continuing to work on a fix for this issue.
-
identified May 04, 2026, 05:29 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring May 04, 2026, 05:39 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 04, 2026, 06:17 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Apr 08, 2026, 07:17 PM UTC
We are currently investigating this issue.
-
monitoring Apr 08, 2026, 07:44 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 08, 2026, 09:18 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Mar 10, 2026, 03:47 PM UTC
We are investigating a potential outage for some customers.
-
investigating Mar 10, 2026, 04:30 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 10, 2026, 05:29 PM UTC
We are continuing to investigate this issue.
-
monitoring Mar 10, 2026, 05:31 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 12, 2026, 10:11 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Feb 13, 2026, 04:39 PM UTC
We are currently investigating this issue.
-
monitoring Feb 13, 2026, 04:46 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 13, 2026, 05:31 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
identified Jan 13, 2026, 05:52 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jan 13, 2026, 05:58 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 13, 2026, 08:38 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
monitoring Nov 18, 2025, 02:01 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 18, 2025, 06:03 PM UTC
The service is fully recovered.
Read the full incident report →
- 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
-
investigating Sep 30, 2025, 07:28 PM UTC
We are currently investigating this issue.
-
investigating Sep 30, 2025, 07:29 PM UTC
We are continuing to investigate this issue.
-
monitoring Sep 30, 2025, 08:33 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 30, 2025, 09:27 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2025, 09:42 PM UTC
- Resolved
- Aug 06, 2025, 11:10 PM UTC
- Duration
- 1h 28m
Affected: Google Cloud Platform
Timeline · 2 updates
-
identified Aug 06, 2025, 09:42 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Aug 06, 2025, 11:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2025, 02:07 AM UTC
- Resolved
- Jul 07, 2025, 03:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 22, 2025, 02:07 AM UTC
We are currently investigating this issue.
Read the full incident report →
- 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
-
investigating Jul 02, 2025, 04:56 PM UTC
We are currently investigating this issue.
-
investigating Jul 02, 2025, 04:56 PM UTC
We are continuing to investigate this issue.
-
identified Jul 02, 2025, 05:01 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 02, 2025, 05:16 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 02, 2025, 05:41 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jul 02, 2025, 03:39 PM UTC
We are currently investigating this issue.
-
investigating Jul 02, 2025, 03:45 PM UTC
We are continuing to investigate this issue.
-
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
-
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.
-
monitoring Jul 02, 2025, 04:54 PM UTC
Our mitigation has completed and operator status has recovered. We will continue to monitor.
-
resolved Jul 02, 2025, 05:56 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jul 01, 2025, 04:43 PM UTC
We are currently investigating this issue.
-
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.
-
investigating Jul 01, 2025, 05:53 PM UTC
We have not seen recurrence of the issue, but are continuing to investigate the root cause.
-
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.
-
resolved Jul 01, 2025, 11:37 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jun 30, 2025, 06:16 PM UTC
We are currently investigating this issue.
-
identified Jun 30, 2025, 06:22 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 30, 2025, 09:36 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 30, 2025, 09:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2025, 08:51 PM UTC
- Resolved
- Jun 26, 2025, 09:37 PM UTC
- Duration
- 46m
Affected: Carrier Networks: Messaging
Timeline · 4 updates
-
investigating Jun 26, 2025, 08:51 PM UTC
We are currently investigating this issue.
-
investigating Jun 26, 2025, 08:56 PM UTC
We are continuing to investigate this issue.
-
monitoring Jun 26, 2025, 09:21 PM UTC
We believe the issue occurred earlier in the day with a certain numbers and was resolved by 18:00 UTC. We are continuing to investigate the underlying cause with our carrier partner.
-
resolved Jun 26, 2025, 09:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2025, 10:20 PM UTC
- Resolved
- Jun 19, 2025, 04:01 AM UTC
- Duration
- 5h 40m
Affected: Integrations
Timeline · 2 updates
-
monitoring Jun 18, 2025, 10:20 PM UTC
A fix has been rolled out, and refreshing the CTI will resolve the issue.
-
resolved Jun 19, 2025, 04:01 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 06:09 PM UTC
- Resolved
- Jun 12, 2025, 09:57 PM UTC
- Duration
- 3h 47m
Affected: Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound CallsApplicationContact CenterMeetingsMessagingGoogle Cloud Platform
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 03:19 PM UTC
- Resolved
- Jun 12, 2025, 06:07 PM UTC
- Duration
- 2h 48m
Affected: Analytics
Timeline · 3 updates
-
investigating Jun 12, 2025, 03:19 PM UTC
We are currently investigating this issue.
-
monitoring Jun 12, 2025, 04:01 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 12, 2025, 06:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2025, 06:36 PM UTC
- Resolved
- Jun 10, 2025, 10:22 PM UTC
- Duration
- 3h 45m
Affected: Workforce Management
Timeline · 4 updates
-
investigating Jun 10, 2025, 06:36 PM UTC
We are currently investigating this issue.
-
investigating Jun 10, 2025, 07:23 PM UTC
We are continuing to investigate this issue.
-
monitoring Jun 10, 2025, 09:10 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 10, 2025, 10:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2025, 12:19 PM UTC
- Resolved
- Jun 10, 2025, 01:22 PM UTC
- Duration
- 1h 3m
Affected: Ai Agent
Timeline · 4 updates
-
identified Jun 10, 2025, 12:19 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Jun 10, 2025, 12:20 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Jun 10, 2025, 12:58 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 10, 2025, 01:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2025, 02:17 AM UTC
- Resolved
- Jun 05, 2025, 03:51 AM UTC
- Duration
- 1h 34m
Affected: Telephony Infrastructure: Inbound CallsTelephony Infrastructure: Outbound CallsMeetings
Timeline · 3 updates
-
investigating Jun 05, 2025, 02:17 AM UTC
We are currently investigating this issue.
-
investigating Jun 05, 2025, 02:18 AM UTC
We are continuing to investigate this issue.
-
resolved Jun 05, 2025, 03:51 AM UTC
This incident has been resolved.
Read the full incident report →