- Level
- confirmed
- Worst impact
- Major outage
- Components
- Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls, Application, Contact Center, Meetings, Messaging, Google Cloud Platform
- Down Index
- 50of 100
What to do
Check whether you use Dialpad Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls, Application, Contact Center and 3 more. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 48m it lasted.
Anything that failed between 2025-06-12 18:09 UTC and 2025-06-12 21:57 UTC may need a replay.Subscribe to Dialpad's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=dialpad works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Dialpad 9
- investigating
We are currently investigating this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are currently investigating this issue. If you are having difficulty contacting Dialpad Support, please visit https://help.dialpad.com and follow the instructions in the banner at the top of the page.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We are aware of a widespread Google Cloud outage that began on June 12, 2025. As Dialpad relies on Google Cloud for certain functionalities, this outage is currently impacting our services, and you may experience issues such as login failures or disruptions in call and messaging capabilities. What’s Happening? According to reports from Downdetector and other sources, this global outage is affecting numerous platforms that depend on Google’s infrastructure, including Dialpad, due to issues with Google’s Identity and Access Management services. This has caused widespread disruptions for businesses worldwide. Our Response Our team is actively monitoring the situation and working closely with Google to ensure services are restored as quickly as possible. Google is addressing the issue, and we are committed to keeping you informed as updates become available. Please check our Dialpad Status Page for real-time updates on service status. What You Can Do Stay updated on the outage via Dialpad's Status Page at https://status.dialpad.com, Downdetector (https://downdetector.com/status/google) or Google’s Cloud Service Health Dashboard (https://status.cloud.google.com). We understand how critical our services are to your business, and we sincerely apologize for the inconvenience caused by this outage. Our team is doing everything possible to minimize disruption and restore full functionality as soon as Google resolves the issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-5e2416ed29
Is Dialpad still down?
No, this incident was resolved 2025-06-12 21:57 UTC. For Dialpad's live state, see https://down.guide/dialpad.
How long did it last?
3h 48m, from 2025-06-12 18:09 UTC to 2025-06-12 21:57 UTC, by the times Dialpad posted.
What was affected?
Dialpad named Telephony Infrastructure: Inbound Calls, Telephony Infrastructure: Outbound Calls, Application, Contact Center and 3 more.
What caused it?
Dialpad hasn't published a root cause. If it does, it shows here.
Where does this come from?
Dialpad's official status page, https://status.dialpad.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.