Google Workspace Outage History

Google Workspace is up right now

Google Workspace had 37 outages in the last 2 years totaling 750h 40m of downtime — averaging 1.5 incidents per month.

There were 37 Google Workspace outages since September 29, 2025 totaling 750h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.google.com/appsstatus/dashboard/

Minor September 25, 2026

Mitigating elevated error rate with Google Workspace Studio web.

Detected by Pingoru
Sep 25, 2026, 03:47 PM UTC
Resolved
Sep 25, 2026, 04:40 PM UTC
Duration
53m
Affected: Google Workspace Studio
Timeline · 2 updates
  1. monitoring Sep 25, 2026, 04:29 PM UTC

    Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Friday, 2026-09-25 10:30 PDT. Symptoms: Customers may experience an endless loading screen when attempting to access Google Workspace Studio on the web. Workaround: None at this time.

  2. resolved Sep 25, 2026, 04:52 PM UTC

    Description: The issue with Google Workspace Studio has been resolved for all affected users as of Friday, 2026-09-25 09:40 PDT. From preliminary analysis, the root cause of the issue is a recent rollout. Our engineering team has rolled back which mitigated the issue. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have experienced an endless loading screen when attempting to access Google Workspace Studio on the web. Workaround: The issue is now mitigated.

Read the full incident report →

Minor September 11, 2026

Mitigated intermittent elevated error rates with Gemini 3.1 Pro models on Gemini Web and Gemini App.

Detected by Pingoru
Sep 11, 2026, 01:00 PM UTC
Resolved
Sep 11, 2026, 08:22 PM UTC
Duration
7h 22m
Affected: Gemini
Timeline · 1 update
  1. resolved Sep 11, 2026, 08:45 PM UTC

    Description: Between 6:00 PDT and 13:22 PDT on 11 September 2026, a subset of Gemini users may have experienced elevated error rates with Gemini 3.1 Pro models on Gemini Web and Gemini App. From preliminary analysis, the issue was triggered by a recent rollout. Our engineers identified the cause and mitigated it with a code change. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have encountered intermittent errors when using Gemini 3.1 Pro models on Gemini Web and Gemini App.

Read the full incident report →

Minor August 28, 2026

Incident affecting Google Chat

Detected by Pingoru
Aug 28, 2026, 05:50 PM UTC
Resolved
Aug 28, 2026, 08:34 PM UTC
Duration
2h 44m
Affected: Google Chat
Timeline · 3 updates
  1. monitoring Aug 28, 2026, 07:25 PM UTC

    Description: We are experiencing an intermittent issue with Google Chat Friday, 2026-08-28 10:25 PDT. Our engineering team has investigated the issue and are currently working on mitigating the issue. We will provide more information by Friday, 2026-08-28 14:15 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Users are experiencing an issue where they receive notifications for new messages, but the actual messages fail to appear in their chat application unless the user refreshes their view Workaround: Users can refresh to see new messages

  2. resolved Aug 28, 2026, 08:55 PM UTC

    Description: The issue with Google Chat has been resolved for all affected users as of Friday, 2026-08-28 13:45 PDT. From preliminary analysis the issue was triggered due to a recent change which was rolled back to mitigate the impact. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Users were experiencing an issue where they received notifications for new messages, but the actual messages failed to appear in their chat application unless the user refreshed their view. Workaround: None as the issue is resolved.

  3. resolved Sep 04, 2026, 03:43 AM UTC

    Google chat: * Delayed message rendering: New messages did not appear in active conversation streams automatically. Users were required to manually refresh their client or send a new message/react to force the stream to synchronize. * Stalled read states and inbox sorting: Background actions, such as updating unread badges and moving active spaces to the top of the inbox, experienced heavy internal error rates and were significantly delayed for users. * Search indexing delays: New messages sent during the outage window stalled in the indexing pipeline, experiencing delays in becoming searchable. Scope exclusions: * No Data Loss: At no point was customer data lost or compromised. All messages transmitted during the incident window were securely captured in primary storage and successfully delivered to conversation streams once the backlog cleared.

Read the full incident report →

Minor August 18, 2026

Investigating access issues with Classroom’s new web homepage.

Detected by Pingoru
Aug 18, 2026, 07:03 PM UTC
Resolved
Aug 18, 2026, 10:30 PM UTC
Duration
3h 27m
Affected: Classroom
Timeline · 4 updates
  1. monitoring Aug 18, 2026, 07:35 PM UTC

    Description: We are investigating increasing reports of access issues with Classroom’s new web homepage beginning on Thursday, 2026-08-13. Our engineering team is currently working on a potential fix while continuing to investigate the full root cause. We will provide an update by Tuesday, 2026-08-18 13:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Admins and some Teachers may experience permission errors when accessing Classroom’s new web homepage. Workaround: Users should still be able to navigate to other views from the left hand pane of the interface.

  2. monitoring Aug 18, 2026, 08:00 PM UTC

    Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Tuesday, 2026-08-18 14:00 PDT. We will provide more information by Tuesday, 2026-08-18 14:15 PDT. Symptoms: Admins and some Teachers may experience permission errors when accessing Classroom’s new web homepage. Workaround: Users should still be able to navigate to other views from the left hand pane of the interface.

  3. monitoring Aug 18, 2026, 08:27 PM UTC

    Description: Our engineering has identified the cause and mitigation work is currently underway. The mitigation rollout is expected to take several hours. We will provide more information by Wednesday, 2026-08-19 8:00 PDT. Symptoms: Workspace Admins may experience permission errors when accessing Classroom’s web homepage. Remaining Classroom functionality remains unaffected. The Classroom Mobile App and the Classroom API are unaffected by the issue. Workaround: All other pages are unaffected and admins can navigate to other pages using the left hand pane on the interface. Workspace Admins can still create classes without any issue. Workspace Admins can also view the courses that they are in by going to https://classroom.google.com/h/tv

  4. resolved Aug 18, 2026, 11:02 PM UTC

    Description: The issue with Classroom has been resolved for all affected users as of Tuesday, 2026-08-18 15:30 PDT. From preliminary analysis, the issue was triggered due to a recent change which caused the permission mismatch, our Engineering team has rolled out the fix to mitigate the impact. We thank you for your patience while we worked on resolving the issue. Symptoms: Workspace Admins may have experienced permission errors when accessing Classroom’s web homepage. Remaining Classroom functionality remained unaffected. The Classroom Mobile App and the Classroom API were unaffected by the issue. Workaround: None as the issue is resolved

Read the full incident report →

Minor June 22, 2026

Some consumer Google Voice users are experiencing account suspensions.

Detected by Pingoru
Jun 22, 2026, 07:30 PM UTC
Resolved
Jun 23, 2026, 12:46 AM UTC
Duration
5h 16m
Affected: Google Voice
Timeline · 3 updates
  1. monitoring Jun 22, 2026, 10:28 PM UTC

    Description: We are experiencing an issue with Google Voice beginning at Monday, 2026-06-22 12:30 PDT. Our engineering team has identified the root cause and is actively working to mitigate the issue. We will provide an update by Monday, 2026-06-22 17:30 PDT with current details. We apologize to all who are affected by the disruption. Diagnosis / customer symptoms: Some consumer Google Voice users are experiencing account suspensions

  2. monitoring Jun 23, 2026, 12:29 AM UTC

    Description: We are experiencing an issue with Google Voice beginning at Monday, 2026-06-22 12:30 PDT. Our engineering team has identified a mitigation strategy and is actively working on mitigation. We do not have an ETA for mitigation at this time. We will provide an update by Monday, 2026-06-22 22:30 PDT with current details. Symptoms: Some consumer Google Voice users are experiencing account suspensions Workaround: None at this time.

  3. resolved Jun 23, 2026, 01:08 AM UTC

    Description: The issue with Google Voice has been resolved for all affected users as of Monday, 2026-06-22 17:46 PDT Our engineers have mitigated the issue by rolling back to a previous version and reinstating suspended accounts. We thank you for your patience while we worked on resolving the issue. Symptoms: Some consumer Google Voice users experienced account suspensions Workaround: The issue is now mitigated.

Read the full incident report →

Minor May 21, 2026

Gmail users are experiencing delayed delivery of messages sent from the bank.in domains.

Detected by Pingoru
May 21, 2026, 07:00 AM UTC
Resolved
May 21, 2026, 03:47 PM UTC
Duration
8h 47m
Affected: Gmail
Timeline · 2 updates
  1. investigating May 21, 2026, 03:37 PM UTC

    Description: We are experiencing an issue with Gmail beginning on Thursday, 2026-05-21 at 00:00 PDT. Mitigation efforts are currently underway by our engineering team. We will provide the next update by Thursday, 2026-05-21 at 09:30 PDT. Diagnosis / customer symptoms: Gmail users are experiencing delayed delivery of messages sent from the bank.in domains. Workaround: None at this time.

  2. resolved May 21, 2026, 04:09 PM UTC

    Description: Our internal telemetry shows that the issue with Gmail has been resolved for all affected users as of Thursday, 2026-05-21 at 08:47 US/Pacific. Our engineering team is actively monitoring the system to ensure continued stability. Diagnosis / customer symptoms: Customers should expect new messages to be delivered normally, older emails could take some time as the senders continue to retry. Workaround: This issue is now mitigated.

Read the full incident report →

Minor May 19, 2026

Incident affecting Gemini Notebook

Detected by Pingoru
May 19, 2026, 10:29 PM UTC
Resolved
May 20, 2026, 04:04 AM UTC
Duration
5h 35m
Affected: Gemini Notebook
Timeline · 3 updates
  1. monitoring May 20, 2026, 01:07 AM UTC

    Description: We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 20:30 PDT with current details. Customer symtomps: Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time

  2. investigating May 20, 2026, 03:20 AM UTC

    Description: We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 22:00 PDT with current details. Symptoms: Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time.

  3. resolved May 20, 2026, 04:38 AM UTC

    Description: The issue with NotebookLM has been resolved for all affected users as of Tuesday, 2026-05-19 21:04 PDT. From preliminary analysis, the issue was triggered by a recent software update resulting in accounts on premium plans being incorrectly recognized as free accounts. The issue was mitigated by restoring the system to a previous stable state, which successfully reinstated the appropriate service tiers for all affected accounts. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have noticed lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time.

Read the full incident report →

Minor May 12, 2026

Incident affecting Cameyo by Google

Detected by Pingoru
May 12, 2026, 04:01 PM UTC
Resolved
May 12, 2026, 10:16 PM UTC
Duration
6h 15m
Affected: Cameyo by Google
Timeline · 1 update
  1. resolved May 13, 2026, 05:55 PM UTC

    Description: We were experiencing an issue with Cameyo by Google, beginning on Tuesday, 12 May 2026 09:01 US/Pacific. The issue was mitigated on Tuesday, 12 May 2026 15:16 US/Pacific by restarting the RAP system service, and performing full server reboots. From preliminary investigation, this was caused by a faulty code for logging improvement on the Player VMs. Log files were unexpectedly duplicated until the disk was full leading to the session failures. Some customers were recovered automatically after the channel binaries were rolled back, while the others were required to restart their VMs manually. Currently, the issue is fully mitigated and change is rolled back. We apologise to those who were impacted by this issue. Customer symptoms: The customers were experiencing an issue that couldn’t connect to the Player VMs normally. The disk utilization on the affected VMs reaches 99% or even 100%. Workaround: Not needed because all affected servers have been mitigated.

Read the full incident report →

Minor April 29, 2026

Investigating issues with Classroom.

Detected by Pingoru
Apr 29, 2026, 06:30 PM UTC
Resolved
Apr 29, 2026, 08:45 PM UTC
Duration
2h 15m
Affected: Classroom
Timeline · 4 updates
  1. investigating Apr 29, 2026, 07:17 PM UTC

    Description: We are experiencing an issue with Classroom beginning at Wednesday, 2026-04-29 11:30 PDT. Our engineering team continues to investigate the issue. We will provide more information by Wednesday, 2026-04-29 13:00 PDT. Symptoms: Affected users may experience issues accessing classroom. Workaround: No workarounds available at this time.

  2. monitoring Apr 29, 2026, 07:53 PM UTC

    Description: Our engineering team has identified the cause and working on mitigation of the issue . The mitigation is expected to complete by Wednesday, 2026-04-29 15:00 PDT. We will provide more information by Wednesday, 2026-04-29 15:15 PDT. Symptoms: Affected users may experience issues accessing classroom. Workaround: No workarounds available at this time.

  3. monitoring Apr 29, 2026, 08:13 PM UTC

    Description: A fix has been deployed, and services have stabilized for the majority of users. We are aware that a small subset of users may still encounter errors. Our engineering team is actively working on a secondary resolution to address these remaining users. Full resolution for remaining users is expected to complete by Wednesday, 2026-04-29 14:00 PDT. We will provide an update by Wednesday, 2026-04-29 14:15 PDT with current details. Symptoms: Affected users may experience issues accessing classroom. Workaround: No workarounds available at this time.

  4. resolved Apr 29, 2026, 09:07 PM UTC

    Description: A fix has been deployed, and services have stabilized for all users. The issue with Google Classroom has been resolved for all affected users as of Wednesday, 2026-04-29 13:45 PDT. The issue was due to an internal software migration. Our engineers have mitigated the issue by rolling back the migration for impacted users. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected users may have experienced issues accessing the classroom. Workaround: The issue is resolved.

Read the full incident report →

Minor April 28, 2026

Investigating issues with slow loading of AppSheet

Detected by Pingoru
Apr 28, 2026, 07:30 AM UTC
Resolved
Apr 28, 2026, 03:50 PM UTC
Duration
8h 20m
Affected: AppSheet
Timeline · 3 updates
  1. monitoring Apr 28, 2026, 03:20 PM UTC

    Description: We are experiencing an issue with AppSheet beginning at Tuesday, 2026-04-28 00:30 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-04-28 09:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Affected customers would experience slow loading times and internal server errors for AppSheet apps. Workaround: None at this time.

  2. monitoring Apr 28, 2026, 04:00 PM UTC

    Description: Our engineering team has implemented a fix and system telemetry indicates that latency and error rates have returned to normal levels. We are continuing to monitor the environment closely to ensure full stability. We will provide an update by Tuesday, 2026-04-28 10:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Affected customers would experience slow loading times and internal server errors for AppSheet apps. Workaround: None at this time.

  3. resolved Apr 28, 2026, 04:50 PM UTC

    Description: The issue with AppSheet has been resolved for all affected users as of Tuesday, 2026-04-28 08:50 PDT. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected customers would have experienced slow loading times and internal server errors for AppSheet apps.

Read the full incident report →

Minor April 8, 2026

Incident affecting AppSheet

Detected by Pingoru
Apr 08, 2026, 09:05 PM UTC
Resolved
Apr 08, 2026, 10:40 PM UTC
Duration
1h 35m
Affected: AppSheet
Timeline · 2 updates
  1. investigating Apr 08, 2026, 10:22 PM UTC

    Description: Beginning on Wednesday, 2026-04-08 14:05 PDT, we are experiencing an issue with AppSheet that caused users to be erroneously redirected to the asia-southeast region. Our engineers have identified the cause was due to a recent change and have reverted. Our internal telemetry shows the signs of recovery and are currently monitoring the recovery status. We expect full service recovery within an hour. We will provide an update by Wednesday, 2026-04-08 16:30 PDT with current details Customer symptoms: Users are automatically redirected to asia-southeast.appsheet.com, which may cause "Forbidden" or 403 errors when attempting to access their apps. Workaround: None at this time.

  2. resolved Apr 08, 2026, 11:27 PM UTC

    Description: The issue with AppSheet has been resolved for all the affected customers as of Wednesday, 2026-04-08 15:40 US/Pacific. As per the preliminary analysis, the issue was triggered by a recent change that caused the users to be erroneously redirected to the asia-southeast region. Our engineering team rolled back the change to mitigate the impact and verified the service stability. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Users may have experienced automatic redirection to asia-southeast.appsheet.com, resulting in errors when attempting to access their apps. Workaround: None at this time.

Read the full incident report →

Major March 20, 2026

Incident affecting Google Keep

Detected by Pingoru
Mar 20, 2026, 10:30 PM UTC
Resolved
Mar 21, 2026, 05:03 AM UTC
Duration
6h 33m
Affected: Google Keep
Timeline · 4 updates
  1. investigating Mar 21, 2026, 03:19 AM UTC

    Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

  2. investigating Mar 21, 2026, 03:46 AM UTC

    Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 23:00 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

  3. investigating Mar 21, 2026, 05:33 AM UTC

    Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our mitigation efforts are underway and we are seeing the signs of recovery. We do not have an ETA for full mitigation. We will provide the next update by Saturday, 2026-03-21 00:30 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

  4. resolved Mar 21, 2026, 07:17 AM UTC

    Description: The issue has been mitigated as of Friday, 2026-03-20 22:03 US/Pacific. The service issue which resulted in connection timeouts and 502 error pages, was caused by excess traffic impacting the keep.google.com. Our engineering team has implemented a mitigation and is continuing to work to ensure long-term service stability and prevent recurrence. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Minor March 13, 2026

Incident affecting Apps Script, Google Calendar and Google Docs

Detected by Pingoru
Mar 13, 2026, 12:00 PM UTC
Resolved
Mar 13, 2026, 02:30 PM UTC
Duration
2h 30m
Affected: Apps ScriptGoogle CalendarGoogle DocsGoogle DriveGoogle Slides
Timeline · 3 updates
  1. monitoring Mar 13, 2026, 01:58 PM UTC

    Description: We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. Our engineering teams are actively working to mitigate the impact. We will provide an update by Friday, 2026-03-13 08:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: A subset of customers may experience elevated error rates when accessing the impacted products in the US region. Workaround: Impacted users may re-attempt the unsuccessful action.

  2. monitoring Mar 13, 2026, 02:34 PM UTC

    Description: We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. We have confirmed that the issue affecting Google Drive is now mitigated. Users should no longer experience unavailability when accessing or interacting with Drive files. Our engineering teams continue to actively work on mitigating the remaining impacted products. We will provide an update by Friday, 2026-03-13 09:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: A subset of customers may experience elevated error rates when accessing the impacted products in the US region. Workaround: Impacted users may re-attempt the unsuccessful action.

  3. resolved Mar 13, 2026, 02:56 PM UTC

    Description: The issue with Google Workspace has been resolved for all affected users as of Friday, 2026-03-13 07:30 PDT. From preliminary analysis, the incident was triggered by resource contention in the impacted location, following a recent update. This led to elevated error rates and latency for several Workspace products. Our engineering teams mitigated the impact by increasing infrastructure capacity,performing traffic restarts, and rolling back the identified change We thank you for your patience while we worked to resolve this issue. Customer symptoms: A subset of customers may have experienced elevated error rates when accessing the impacted products in the US region. Workaround: NA. Issue is now mitigated

Read the full incident report →

Minor February 23, 2026

Google Chat is experiencing Issue with creating a new conversations

Detected by Pingoru
Feb 23, 2026, 06:32 AM UTC
Resolved
Feb 23, 2026, 08:35 AM UTC
Duration
2h 3m
Affected: Google Chat
Timeline · 3 updates
  1. investigating Feb 23, 2026, 08:17 AM UTC

    Description: Our engineering team continues to investigate the issue. We will provide an update by Monday, 2026-02-23 00:45 PST with current details. We apologize to all who are affected by the disruption. Customer symptoms: Users may experience errors when attempting to create new conversations or spaces in Google Chat. Existing conversations remain functional. Workaround: None at the moment

  2. investigating Feb 23, 2026, 08:34 AM UTC

    Description: Our engineering teams are actively working on mitigation efforts to restore the ability to create new conversations as quickly as possible. We do not have any ETA at the moment. We will provide an update by Monday, 2026-02-23 01:30 PST with current details. Customer symptoms: Users may experience errors when attempting to create new Direct Messages (DM) or new chat spaces in Google Chat. This issue specifically affects the creation of new conversations; however, users can continue to send and receive messages in existing conversations and spaces Workaround: None at the moment

  3. resolved Feb 23, 2026, 08:54 AM UTC

    The issue with Google Chat has been resolved for all affected users as of Monday, 2026-02-23 00:35 PST. As per our preliminary analysis, the incident was triggered by a recent configuration update. Our engineering team performed a rollback to mitigate the impact and verified the stability. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →