Google Workspace Outage History
Google Workspace is up right nowGoogle Workspace had 46 outages in the last 2 years totaling 872h 38m of downtime — averaging 1.9 incidents per month.
There were 46 Google Workspace outages since July 2, 2025 totaling 872h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.
Multiple Workspace Products experiencing Issues.
Timeline · 4 updates
Gmail users are experiencing delayed delivery of messages sent from the bank.in domains.
Timeline · 2 updates
- 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.
- 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.
Incident affecting NotebookLM
Timeline · 3 updates
- 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
- 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.
- 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.
Incident affecting Cameyo by Google
Timeline · 1 update
- 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.
Gmail Android users using Microsoft Exchange Online may fail to log in due to authentication issues.
Timeline · 5 updates
Investigating elevated error rates with Gemini conversations.
Timeline · 10 updates
Investigating issues with 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.
Investigating issues with slow loading of 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.
Incident affecting Admin Console
Timeline · 4 updates
Incident affecting 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.
Customers may experience delays in receiving and sending emails.
Timeline · 7 updates
Incident affecting 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.
Incident affecting Apps Script, Google Calendar and Google Docs
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
Google Chat is experiencing Issue with creating a new conversations
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.
Gmail users might see banners indicating missing spam checks.
Timeline · 9 updates
Google Voice customers may experience MMS messages not being delivered to recipients.
Timeline · 4 updates
- monitoring Jan 13, 2026, 11:10 PM UTC
Description: We are experiencing an issue with sending MMS messages via Google Voice beginning on Thursday, 2026-01-08 05:00 PST. Our engineering team continues to investigate the issue with a 3rd party vendor. We will provide an update by Tuesday, 2026-01-13 20:30 PST with current details. We apologize to all who are affected by the disruption. Customer symptoms: Google Voice customers may experience issues while sending MMS messages where the messages may appear to be successfully sent but recipients may not receive them. Workaround: SMS messages can be sent successfully, so the users can send 1-to-1 messages or messages without attachments instead of MMS messages.
- monitoring Jan 14, 2026, 04:16 AM UTC
Description: We are experiencing an issue with sending MMS messages via Google Voice beginning on Thursday, 2026-01-08 05:00 PST. Our engineering team continues to investigate the issue with a 3rd party vendor to mitigate the issue. We will provide an update by Wednesday, 2026-01-14 10:30 PST with current details. Customer symptoms: Google Voice customers may experience issues while sending MMS messages where the messages may appear to be successfully sent but recipients may not receive them. Workaround: SMS messages can be sent successfully, so the users can send 1-to-1 messages or messages without attachments instead of MMS messages.
- monitoring Jan 14, 2026, 06:33 PM UTC
Description: We are experiencing an issue with sending MMS messages via Google Voice beginning on Thursday, 2026-01-08 05:00 PST. Our engineering team continues to investigate the issue with a 3rd party vendor to mitigate the issue. We will provide an update by Thursday, 2026-01-15 10:30 PST with current details. Customer symptoms: Google Voice customers may experience issues while sending MMS messages where the messages may appear to be successfully sent but recipients may not receive them. Workaround: SMS messages can be sent successfully, so the users can send 1-to-1 messages or messages without attachments instead of MMS messages.
- resolved Jan 14, 2026, 09:30 PM UTC
The issue with Google Voice has been resolved for all affected users as of Wednesday, 2026-01-14 13:00 PST. We thank you for your patience while we worked on resolving the issue.
Some Google Meet customers may experience an issue with ‘Continuous meeting chat’ feature
Timeline · 3 updates
Google Meet customers are experiencing issues loading meet.google.com in the Asia region.
Timeline · 6 updates
Google Chat users might not be able to open chat while connecting from Europe.
Timeline · 4 updates
Incident affecting Google Workspace Support
Timeline · 2 updates
- monitoring Nov 17, 2025, 02:29 AM UTC
Description: We are experiencing an intermittent issue with Google Workspace Chat Support beginning at Friday, 2025-11-14 10:05 PST. Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2025-11-16 20:30 PST with current details. We apologize to all who are affected by the disruption. Symptoms: A subset Customers using Chat to Google Workspace Support might encounter a UI issue where uploaded files appear as a blank message instead of showing the file directly in the chat interface. Despite this UI issue, files are successfully uploaded and accessible by clicking on the blank message. Workaround: None at this time.
- resolved Nov 17, 2025, 04:11 AM UTC
Description: The issue with Google Cloud Support has been resolved for all affected users as of Sunday, 2025-11-16 19:10 PST. The issue was due to a recent code change. Our engineers have mitigated the issue by rolling back the system to a previous version. We thank you for your patience while we worked on resolving the issue. Symptoms: A subset of customers using Chat to Google Support might have encountered a UI issue where uploaded files appeared as a blank message instead of showing the file directly in the chat interface. Despite this UI issue, files were successfully uploaded and accessible by clicking on the blank message. Workaround: Not applicable as the issue has been resolved. None at this time.
We are investigating access issues with multiple workspace products.
Timeline · 9 updates
Gmail is experiencing an issue with images not loading properly.
Timeline · 3 updates
- monitoring Nov 10, 2025, 03:50 PM UTC
Description: We are experiencing an issue with Gmail beginning at Monday, 2025-11-10 06:19 PST. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2025-11-10 09:00 PST with current details. Symptoms: Customers may experience issues with images not loading in Gmail. This might appear as broken images in the emails. Workaround: None at this time.
- monitoring Nov 10, 2025, 04:43 PM UTC
Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We are seeing significant improvement and the error rates have subsided. We will provide an update by Monday, 2025-11-10 10:00 US/Pacific with current details. Symptoms: Customers may experience issues with images not loading in Gmail. This might appear as broken images in the emails. Workaround: None at this time.
- resolved Nov 10, 2025, 05:26 PM UTC
Description: The issue with Gmail has been resolved for all affected users as of Monday, 2025-11-10 08:58 US/Pacific. The issue was due to network latency which eventually translated into errors. Our engineers have mitigated the issue by diverting the traffic to other regions. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may experience issues with images not loading in Gmail. This might appear as broken images in the emails. Workaround: None at this time.