Google Workspace outage, 31 May 2026
**Title** Multiple Workspace Products experiencing Issues. **Description** We are experiencing an issue with Google Voice, Google Meet, Google Drive, Google Cha...
- Started
- Resolved
- 31 May 2026, 04:24 UTC (after 56 min)
- Impact
- Minor
- Affected
- Gmail, Google Calendar, Google Chat, Google Docs, Google Drive, Google Meet, Google Voice
Is this still happening?
No. Google Workspace marked this incident resolved on 31 May 2026, 04:24 UTC, 56 min after it began.
Right now: Google Workspace reports all systems operational. (as of 5 Nov, 00:11 UTC) Live Google Workspace status
What caused it: Google Workspace's root cause analysis
# Incident Report Summary Starting at 20:15 US/Pacific on Saturday, 30 May 2026, various Google Workspace services encountered service-level disruptions lasting approximately 75 minutes. The scope of impact spanned several products, specifically affecting Gmail, Google Docs, Drive, Calendar, Chat, Meet, and Google Voice. Throughout the duration of this event, users faced obstacles while attempting to initialize applications, in addition to experiencing sporadic instances of elevated latency and request failures. Google offers a sincere apology for the operational interference this issue introduced to your organization. Recognizing the critical nature of Google Cloud to your daily operations, we deeply regret any resulting loss in productivity. Engineering efforts are currently focused on remediating the underlying cause to ensure future stability. Root Cause The disruption originated from failures in a critical cluster infrastructure component responsible for Google's service discovery and configuration management systems. This system facilitates resource synchronization, manages shared data access, and coordinates background tasks for numerous Google services. A high volume of rapid configuration changes triggered the regional failure in Workspace Services, preventing Workspace servers from reliably processing traffic. To mitigate the impact, Google Workspace traffic was redirected to alternative regions. Remediation and Prevention Google engineers were alerted to the issue via automated monitoring on Saturday, 30 May 2026 at 20:28 US/Pacific and immediately began an investigation. The investigation identified elevated error rates and high latency affecting multiple Google Workspace backend services. Upon investigation our engineering team confirmed errors were primarily originating from some regional servers due to coordination service failures in the region. To mitigate the impact, Google engineers redirected traffic away from the affected servers. Google is committed preventing a repeat of this issue in the future and is completing the following actions: - Prevent recurrence of this incident by rolling out the fix for the latent encryption library issue, which improves the handling of internal log compaction compactions during active file writes, to prevent recurrence of the cluster instability. - Investigating additional resilience in our database layer. Detailed Description of Impact On 30 May 2026 from 20:15 to 21:30 US/Pacific, affected customers e...
Last update from Google Workspace
# Incident Report Summary Starting at 20:15 US/Pacific on Saturday, 30 May 2026, various Google Workspace services encountered service-level disruptions lasting approximately 75 minutes. The scope of impact spanned several products, specifically affecting Gmail, Google Docs, Drive, Calendar, Chat, Meet, and Google Voice. Throughout the duration of this event, users faced obstacles while attempting to initialize applications, in addition to experiencing sporadic instances of elevated latency and request failures. Google offers a sincere apology for the operational interference this issue introduced to your organization. Recognizing the critical nature of Google Cloud to your daily operations,...
Read the full incident on the official Google Workspace status page
Similar Google Workspace incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 2 h 30 min
-
, resolved after 5 h 16 min
-
, resolved after 6 days
-
, resolved after 37 min
-
, resolved after 12 h 42 min