Resolved -
This incident has been resolved.
Jun 12, 14:57 PDT
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 12, 13:35 PDT
Update -
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.
Jun 12, 12:32 PDT
Identified -
The issue has been identified and a fix is being implemented.
Jun 12, 12:03 PDT
Update -
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.
Jun 12, 11:27 PDT
Update -
We are continuing to investigate this issue.
Jun 12, 11:21 PDT
Update -
We are continuing to investigate this issue.
Jun 12, 11:16 PDT
Update -
We are continuing to investigate this issue.
Jun 12, 11:15 PDT
Investigating -
We are currently investigating this issue.
Jun 12, 11:09 PDT