Google Workspace Outage History

Google Workspace's Gemini service experienced elevated error rates for 49.5 hours, causing users to encounter "Something went wrong(13)" error messages during conversations. The engineering team conducted ongoing mitigation work and investigation throughout the incident. The incident status remained as ongoing investigation with no available workaround for affected users.

Google Workspace experienced a Classroom service disruption lasting 1.9 hours, beginning at 11:30 PDT on April 29, 2026, where users encountered issues accessing the platform. The engineering team identified the root cause and deployed a fix that resolved the issue for most users, though a small subset continued experiencing errors requiring additional remediation. The incident was classified as minor severity with full resolution expected by 14:00 PDT the same day.

Google Workspace experienced an AppSheet service disruption lasting 1.5 hours starting at 00:30 PDT on April 28, 2026. Users encountered slow loading times and internal server errors when accessing AppSheet applications. The engineering team implemented a fix and confirmed that latency and error rates returned to normal levels through system telemetry monitoring.

Google Workspace users using Google IdP experienced a 5.1-hour outage where they could not sign into their accounts using security keys and hardware-based passkeys, affecting the Admin Console. A workaround was provided requiring administrators to revoke affected keys, generate verification codes for users to sign in with backup codes, and then re-enroll the security keys.

Google Workspace Admin Console experienced an authentication issue where users with security keys and hardware-based passkeys as their 2FA method were unable to sign into their accounts. The incident affected Dasher users using Google as their identity provider, preventing normal login workflows. A workaround was provided requiring administrators to revoke affected keys, generate verification codes for users to sign in, and then have users re-enroll their security keys.

AppSheet customers were experiencing incorrect redirections to asia-southeast.appsheet.com instead of their intended application URLs, resulting in "Not Found" or 403 errors when trying to access their apps. The issue was caused by a recent change that engineers identified and reverted. The incident lasted 1.1 hours with full service recovery expected within an hour of identification.

Gmail users experienced delays in receiving and sending emails for approximately 4.6 hours starting on April 8, 2026 at 06:30 PDT. Google's engineering team applied mitigation measures and internal monitoring indicated that delays and errors subsided by the end of the incident.

Google Keep experienced a major outage lasting 4 hours where users were unable to access keep.google.com through web browsers, encountering connection timeouts and 502 Bad Gateway errors. While Google stated that mobile apps remained operational, at least one user reported that the mobile app also failed to open. Google's engineering team implemented mitigations and reported signs of recovery, with users able to work around the issue by using the Android or iOS mobile apps when they functioned properly.

Google Workspace experienced intermittent errors affecting Google Docs, Apps Script, Google Slides, Google Drive, and Google Calendar starting March 13, 2026 at 05:00 PDT. A subset of customers in the US region encountered elevated error rates when accessing these services. Google Drive issues were resolved first, while engineering teams continued working to mitigate the remaining affected products, with the incident lasting approximately 1 hour.

Google Chat experienced a 40-minute service disruption where users encountered errors when attempting to create new Direct Messages or chat spaces. Existing conversations and messaging functionality remained unaffected, allowing users to continue sending and receiving messages in established chats. Google's engineering team actively worked on mitigation efforts to restore the conversation creation feature.