Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Google Workspace Outage History

Every past Google Workspace outage tracked by IsDown, with detection times, duration, and resolution details.

There were 181 Google Workspace outages since January 2022. The 50 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 31, 2026

May 2026: Multiple Workspace Products experiencing Issues.

Detected May 31, 2026 12:59 AM EDT · Resolved May 31, 2026 1:11 AM EDT · Duration 13 minutes

Google Workspace experienced a service disruption affecting multiple core products including Gmail, Google Calendar, Google Chat, Google Docs, Google Drive, Google Meet, and Google Voice starting on May 30, 2026 at 20:28 PDT. Users encountered application loading issues, intermittent high latency, and errors while using these services. The incident was resolved after 13 minutes with Google's engineering team investigating and addressing the underlying issue.

Minor May 19, 2026

May 2026: NotebookLM customers are experiencing an issue where account tiers are being incorrectly downgraded. Affected Ultra & Pro tier users are seeing Free tier features.

Detected May 19, 2026 9:07 PM EDT · Resolved May 20, 2026 12:40 AM EDT · Duration about 4 hours

NotebookLM experienced an issue where premium account tiers (Ultra & Pro) were incorrectly downgraded to free tier status due to a recent software update. Users encountered reduced resource limits, restricted source counts per notebook, and loss of premium features like advanced sharing and analytics, with only basic functionality remaining available. The engineering team identified the root cause and worked on a mitigation plan over the 3.6-hour incident duration.

Minor May 15, 2026

May 2026: Gmail Android users using Microsoft Exchange Online may fail to log in due to authentication issues.

Detected May 15, 2026 10:05 PM EDT · Resolved May 22, 2026 3:00 PM EDT · Duration 7 days

Gmail Android users experienced authentication and sync failures when accessing Microsoft Exchange Online accounts for approximately 160 hours starting May 6, 2026. The issue prevented users from logging in and syncing their Exchange accounts through the Gmail Android app. Google resolved the problem by releasing Gmail Android app version 2026.05.11 with a fix, requiring affected users to update their app from the Google Play Store.

Minor May 5, 2026

May 2026: Investigating elevated error rates with Gemini conversations.

Detected May 5, 2026 7:35 PM EDT · Resolved May 8, 2026 3:01 PM EDT · Duration 3 days

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.

Minor April 29, 2026

April 2026: Investigating issues with Classroom.

Detected Apr 29, 2026 3:17 PM EDT · Resolved Apr 29, 2026 5:09 PM EDT · Duration about 2 hours

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.

Minor April 28, 2026

April 2026: Investigating issues with slow loading of AppSheet

Detected Apr 28, 2026 11:20 AM EDT · Resolved Apr 28, 2026 12:52 PM EDT · Duration about 2 hours

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.

Minor April 10, 2026

April 2026: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys.

Detected Apr 10, 2026 6:07 AM EDT · Resolved Apr 10, 2026 11:10 AM EDT · Duration about 5 hours

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.

Minor April 10, 2026

April 2026: Admin Console customers are unable to sign into their accounts using security keys and hardware based passkeys.

Detected Apr 10, 2026 6:07 AM EDT · Resolved Apr 10, 2026 6:33 AM EDT · Duration 26 minutes

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.

Minor April 8, 2026

April 2026: AppSheet customers are experiencing redirection to asia-southeast.appsheet.com instead of their intended application URLs.

Detected Apr 8, 2026 6:22 PM EDT · Resolved Apr 8, 2026 7:25 PM EDT · Duration about 1 hour

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.