Google Workspace outage history

Users worldwide faced Google Drive connectivity issues with files not loading and errors across Drive and Docs. Reports described apps not loading, internal errors, and 500 errors, with shared drives intermittently affected. The incident ramped mid-afternoon, with a surge in reports around 2:15 PM UTC and lasting about a half hour before easing around 3:00 PM UTC. StatusGator detected an Early Warning Signal at Oct 21, 2026 2:29 PM UTC, indicating the issue was observed before any provider acknowledgment.

Users of Google Drive within Google Workspace experienced intermittent latency and access issues, with some attempting to use Drive encountering CAPTCHA prompts. The disruption began around 4:00 PM UTC, and Google subsequently marked Google Drive as degraded at 4:37 PM UTC as engineers investigated the impact.

Google Drive was later returned to an operational state, with status updates showing a recovery around 4:42 PM UTC. The issue affected only Google Drive within Google Workspace, and a small set of user reports during the window indicated a brief degradation before service returned to normal.

Impact began around Sep 16, 2026 1:45 PM UTC as Google Drive and Google Docs stopped loading or opening files for many users. The disruption affected core Google Workspace apps, including Drive, Docs, and Sheets, with pages stuck on loading screens, missing files, and captcha prompts. StatusGator detected an Early Warning Signal at Sep 16, 2026 1:48 PM UTC based on user reports, indicating the issue ahead of any provider acknowledgment. The incident persisted into the afternoon, with restoration steps taking place over the next couple of hours and the issue being resolved by Sep 16, 2026 3:29 PM UTC.

Users of Google Workspace across multiple regions experienced degraded messaging as Google Chat suffered widespread delays and messages failed to load. Reports described lag in delivering messages and delayed notifications, with users in North America, Europe, and Asia affected. Impact began around 5:30 PM UTC and intensified through the evening, with StatusGator detecting the issue at Aug 28, 2026 6:04 PM UTC, ahead of any official acknowledgment. The Early Warning Signal remained active until 9:23 PM UTC. There were no concurrent updates on Google's Apps Status Dashboard during this window, so many users relied on alerts and external reports for context. The primary disruption was to Google Chat, though a few users noted intermittent issues with related Workspace tools; overall, the event appeared global rather than regional, with activity gradually stabilizing after the EW window.

Google Drive and Docs experienced loading errors and slow performance starting around Aug 18, 2026 11:58 PM UTC, with many users unable to load files or access Drive for extended periods. The disruption appeared global, with reports of sheets not loading, documents taking long to render, and pervasive load times across web and mobile clients.

StatusGator’s Early Warning Signal captured the issue at Aug 19, 2026 1:34 AM UTC (ending Aug 19, 2026 7:22 AM UTC), roughly five hours before Google acknowledged the problem on its status page at Aug 19, 2026 6:50 AM UTC. Google’s updates indicated the root cause had been identified and mitigation was under way, though there was no ETA for full resolution. The Drive component remained in a degraded state until it was restored to normal at Aug 19, 2026 1:07 PM UTC.

Customers contacting Google Support by email faced delays as Google Workspace Support experienced an inbound-email disruption. The issue began at Jun 30, 2026 12:02 PM UTC and was listed as a degraded intake on Google’s status page, with engineers investigating an issue affecting inbound messages from customers worldwide. The disruption slowed responses and case handling for affected users and appeared to have a global reach given the regional reports.

Google Workspace Gemini Web and Gemini mobile apps experienced an outage where chat histories were not visible. Users reported an empty sidebar, missing saved conversations, and failed searches/listings, though new conversations could still be created. The issue began on Feb 18, 2026 4:30 PM UTC and was tied to a background process that was removing missing user conversation metadata; engineers stopped the process to prevent further impact. Mitigation efforts were underway and Google had not provided an ETA for full recovery at that time.

Two official status updates were posted during the incident. The Gemini component progressed from normal to a degraded state, with ongoing mitigation and no estimated restoration time as of the latest update. The updates were issued on Feb 19, 2026 11:02 AM UTC and Feb 21, 2026 7:42 PM UTC.

The Gmail component of Google Workspace experienced a brief degraded state in which banners appeared indicating that emails hadn’t been scanned for spam, unverified senders, or harmful software. This affected Gmail users by prompting extra caution when handling messages, though core Gmail access remained available. The issue began at Jan 24, 2026 1:02 PM UTC and a small volume of user reports emerged as the banners appeared in the Gmail interface.

Google’s status page documented the incident with two official updates. The Gmail component moved from up to warn at Jan 24, 2026 4:37 PM UTC and then returned to up at Jan 24, 2026 4:42 PM UTC. The incident lasted about 3 hours and 40 minutes, and affected Gmail broadly within Google Workspace.

Two Google Workspace components were affected: Admin Console and the Directory API. Administrators attempting to view or search for users could see empty or missing primary email addresses and account creation times, and applications using the Directory API might receive responses without expected metadata. The incident began at 11:32 AM UTC and lasted until 5:12 PM UTC, a total duration of about 5 hours and 40 minutes. The service issued two status updates during the incident describing ongoing mitigation and the eventual recovery.

Google Meet users experienced issues with the Continuous meeting chat feature, preventing hosts from disabling it and making the disable option invisible in Host Controls within Google Calendar invites. The result was ongoing chat during meetings and hampered moderation for affected sessions.

Google Workspace reported an investigation on the Google Meet status page and provided updates as the incident progressed. The issue began at 4:22 AM UTC and the service remained degraded until it was restored at 3:27 PM UTC. The provider issued multiple updates during the event, and a large volume of user reports indicated widespread impact across regions. The outage lasted roughly 2 days and 11 hours.