Google Workspace Outage History

There were 9 Google Workspace outages since February 18, 2026 totaling 143h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

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

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.
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.
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.
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

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.
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.
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 10, 2026

Incident affecting Admin Console

Detected by Pingoru: Apr 10, 2026, 02:08 AM UTC
Resolved: Apr 10, 2026, 02:50 PM UTC
Duration: 12h 42m

Affected: Admin Console

Timeline · 4 updates

investigating Apr 10, 2026, 10:07 AM UTC

Description: We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 04:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.
investigating Apr 10, 2026, 10:55 AM UTC

Description: We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 05:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.
investigating Apr 10, 2026, 11:27 AM 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-04-10 09:00 PDT. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.
resolved Apr 10, 2026, 03:06 PM UTC

Description: The issue with Admin Console has been resolved for all affected users as of Friday, 2026-04-10 07:50 PDT. Suspected CL have been rolled back and we are seeing in our graphs errors rate have gone down. Customers also confirmed that issues have been mitigated. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Google Workspace users using Google IdP were unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: * Admin should revoke the key. * Admin to create the verification code to sign-in. * The user should sign-in using Backup verification code and then re-enrolls the security key.

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

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.
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 →

Minor April 8, 2026

Customers may experience delays in receiving and sending emails.

Detected by Pingoru: Apr 08, 2026, 01:30 PM UTC
Resolved: Apr 08, 2026, 09:40 PM UTC
Duration: 8h 10m

Affected: Gmail

Timeline · 7 updates

investigating Apr 08, 2026, 06:22 PM UTC

Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 12:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.
investigating Apr 08, 2026, 07:02 PM UTC

Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 13:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.
investigating Apr 08, 2026, 08:03 PM UTC

Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 15:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.
investigating Apr 08, 2026, 09:49 PM UTC

Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning on Wednesday, 2026-04-08 06:30 PDT. Our engineering team has applied the mitigation, and our internal monitoring indicates that delays and errors have subsided. We will continue to monitor for service stability to ensure full recovery. We will provide an update by Wednesday, 2026-04-08 16:00 PDT with current details. Symptoms: Customers may have experienced delays in receiving and sending emails. Workaround: None at this time.
resolved Apr 08, 2026, 10:54 PM UTC

Description: The issue with Gmail has been resolved for all affected users as of Wednesday, 2026-04-08 14:49 PDT. Our engineering team identified a potential issue with a noisy neighbour and has successfully mitigated impact. A full root cause analysis is in progress and further details will be shared through a subsequent incident report. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have experienced delays in receiving and sending emails. Workaround: None at this time.
resolved Apr 10, 2026, 02:32 AM UTC

Preliminary Incident Report We apologize for the inconvenience this Gmail service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced an impact outside of what is listed below, please reach out to Google Workspace Support using the help article https://support.google.com/a/answer/1047213. Date/Time of the Issue (All time US/Pacific) - Incident Start: 08 April 2026 06:30 - Incident End: 08 April 2026 14:40 - Duration: 8 hours, 10 minutes Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Preliminary Root Cause The preliminary root cause was identified as increased connection errors to some external mail services. Google engineers have begun a full root cause analysis and will provide additional information once it is available. Remediation The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: Account Suspension: One of the domains responsible for spamming was identified, resulting in the suspension of the abusive account after review. Traffic Blocking: A block rule was implemented to specifically address and stop traffic originating from an abusive sending domain. Teams monitored rejection rates until they returned to normal levels, confirming that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. A comprehensive Incident Report that will be published to provide further details and outline preventative measures. Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".
resolved Apr 17, 2026, 09:10 AM UTC

Incident Report Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Root Cause The root cause was identified as increased connection errors to external mail services hosted by a specific 3rd party provider. Remediation and Prevention The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: External Mail Provider Reachout: Google worked with the external mail provider to unblock connections and prevent similar issues in the future. Teams monitored rejection rates until they returned to normal levels, verifying that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. Google is committed to preventing a repeat of this issue in the future and is completing the following actions: - Deploy systems to proactively track external blocklists and alert on degradation before users are impacted. - Improve monitoring and alerting systems to proactively detect errors related to external email recipient communication. Detailed Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30 PDT, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

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

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.
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.
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.
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

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.
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.
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

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
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
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 →

Minor February 18, 2026

Incident affecting Gemini

Detected by Pingoru: Feb 18, 2026, 04:30 PM UTC
Resolved: Feb 22, 2026, 08:08 PM UTC
Duration: 4d 3h

Affected: Gemini

Timeline · 5 updates

investigating Feb 19, 2026, 10:57 AM UTC

Description: We are investigating an issue where chat histories are not visible on Gemini Web (gemini.google.com) and the Gemini mobile apps on Wednesday, 2026-02-18 08:30 PST. Our engineering team has identified a background process that was causing the missing user conversation metadata and has successfully stopped the process to prevent further impact. Mitigation efforts are underway, and we do not have an ETA for completion at this time. We will provide an update by Thursday, 2026-02-19 09:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms: * Users may find that their sidebar is empty or that previously saved conversations are missing. * Users may receive an empty response when attempting to list or search for existing conversations. * New conversations can still be created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.
investigating Feb 19, 2026, 04:49 PM UTC

Description: We are investigating an issue where chat histories are not visible on Gemini Web (gemini.google.com) and the Gemini mobile apps on Wednesday, 2026-02-18 08:30 PST. Our engineering team has identified a background process that was causing the missing user conversation metadata and has successfully stopped the process to prevent further impact. Mitigation efforts are underway, and our engineers are working to restore the missing chat histories. We do not have an ETA for completion at this time. We will provide an update by Thursday, 2026-02-19 15:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms: * Users may find that their sidebar is empty or that previously saved conversations are missing. * Users may receive an empty response when attempting to list or search for existing conversations. * New conversations can still be created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.
investigating Feb 20, 2026, 03:02 AM UTC

Description: We are investigating an issue where chat histories are not visible on Gemini Web (gemini.google.com) and the Gemini mobile apps on Wednesday, 2026-02-18 08:30 PST. Our engineering team has identified a background process that was causing the missing user conversation metadata and has successfully stopped the process to prevent further impact. Mitigation efforts are underway, and our engineers are working to restore the missing chat histories. We do not have an ETA for completion at this time. We will provide an update by Thursday, 2026-02-19 18:00 PST with current details. Symptoms: ** Users may find that their sidebar is empty or that previously saved conversations are missing. ** Users may receive an empty response when attempting to list or search for existing conversations. ** New conversations can still be created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.
investigating Feb 20, 2026, 03:03 AM UTC

Description: We are investigating an issue where chat histories are not visible on Gemini Web (gemini.google.com) and the Gemini mobile apps on Wednesday, 2026-02-18 08:30 PST. Our engineering team has identified a background process that was causing the missing user conversation metadata and has successfully stopped the process to prevent further impact. Mitigation efforts are underway, and our engineers are working to restore the missing chat histories. We do not have an ETA for completion at this time. We will provide an update by Friday, 2026-02-20 20:00 PST with current details. Symptoms: ** Users may find that their sidebar is empty or that previously saved conversations are missing. ** Users may receive an empty response when attempting to list or search for existing conversations. ** New conversations can still be created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.
resolved Feb 23, 2026, 01:20 AM UTC

Description: The issue with Gemini has been resolved for all affected users as of Sunday, 2026-02-22 12:08 PST. Based on our initial analysis, the incident was caused by an internal job that caused some valid conversation metadata to be deleted, which resulted in the conversations from the side navigation to be hidden. Users could still access the hidden conversations requests and responses from the activity section. Our engineering team mitigated the impact by restoring the data from the appropriate backups. We thank you for your patience while we worked on resolving the issue. Symptoms: * Users may have found that their sidebar was empty or that previously saved conversations were missing. * Users may have received an empty response when attempting to list or search for existing conversations. * New conversations were still created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.

Read the full incident report →

Looking to track Google Workspace downtime and outages?

Pingoru polls Google Workspace's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when Google Workspace reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Google Workspace alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring Google Workspace for free

5 free monitors · No credit card required