Is Google Workspace down?

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.

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

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.

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.

Description: We are experiencing an issue with Google Drive beginning Tuesday, 2026-08-18 16:58 PDT. 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 22:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Affected customers may experience slowness while using Google Drive. Workaround: None at this time.

Description: We are experiencing an issue with Google Drive beginning Tuesday, 2026-08-18 16:58 PDT. Our engineering team is currently working on a potential fix while continuing to investigate the full root cause. We will provide an update by Wednesday, 2026-08-19 00:30 PDT with current details. Symptoms: Affected customers in Australia and New Zealand may experience slowness while using Google Drive. Workaround: None at this time.

Description: We are experiencing an issue with Google Drive beginning Tuesday, 2026-08-18 16:58 PDT. Our engineering team has identified the root cause of the issue and is actively working on a mitigation strategy. There is no ETA for full resolution. We will provide an update by Wednesday, 2026-08-19 01:30 PDT with current details. Symptoms: Affected customers in Australia and New Zealand may experience slowness or 502 errors, with some users briefly unable to access Drive. Workaround: None at this time.

Description: We are experiencing an issue with Google Drive beginning Tuesday, 2026-08-18 16:58 PDT. Our engineering team has identified the root cause of the issue and is actively working on a mitigation strategy. There is no ETA for full resolution. We will provide an update by Wednesday, 2026-08-19 02:00 PDT with current details. Symptoms: Affected customers in Australia and New Zealand may experience slowness or 502 errors, with some users briefly unable to access Drive. Workaround: None at this time.

Description: We are experiencing an issue with Google Drive beginning Tuesday, 2026-08-18 16:58 PDT. Our engineering team is actively working on a mitigation strategy. There is no ETA for full resolution. We will provide an update by Wednesday, 2026-08-19 03:00 PDT with current details. Symptoms: Affected customers in Australia and New Zealand may experience slowness or 502 errors, with some users briefly unable to access Drive. Workaround: None at this time.

Description: We are experiencing an issue with Google Drive beginning Tuesday, 2026-08-18 16:58 PDT. Our engineering team is actively working on a mitigation strategy. There is no ETA for full resolution. We will provide an update by Wednesday, 2026-08-19 04:30 PDT with current details. Symptoms: Affected customers in Australia and New Zealand may experience slowness or 502 errors, with some users briefly unable to access Drive. Workaround: None at this time.

Description: We are experiencing an issue with Google Drive beginning Tuesday, 2026-08-18 16:58 PDT. Our engineering team is actively working on a mitigation strategy. There is no ETA for full resolution. We will provide an update by Wednesday, 2026-08-19 06:00 PDT with current details. Symptoms: Affected customers in Australia and New Zealand may experience slowness or 502 errors, with some users briefly unable to access Drive. Workaround: None at this time.

Description: The issue with Google Drive has been resolved for all affected customers as of Wednesday, 2026-08-19 05:40 PDT. Our engineering teams determined the slowness was the result of a localized capacity and routing issue within our regional infrastructure. To restore service, we implemented a fix to alleviate the network congestion and accelerated a planned infrastructure upgrade in the affected region to ensure normal performance levels. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected customers in Australia and New Zealand may have experienced slowness or 502 errors, with some users briefly unable to access Drive. Workaround: The issue is now mitigated

Preliminary Incident Report We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Workspace, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in the future.  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 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 (https://support.google.com/a/answer/1047213). Date/Time of the Issue (All time US/Pacific) Incident Start: 18 August 2026 16:58 Incident End: 19 August 2026 05:40 Duration: 12 hours, 42 minutes  Summary On August 18, 2026 from 16:58 to August 19, 2026 05:40 US/Pacific, Drive customers in Australia, Philippines and New Zealand experienced degraded performance and slowness. During this period users also experienced 502 errors. Other Google Workspace services were not affected.  Preliminary Root Cause Google utilizes a multi-tiered global load balancing and network routing architecture to serve traffic efficiently. To ensure fair use and prevent congestion, bandwidth allocation is managed by attributing traffic to specific downstream services. A misconfiguration in the attribution of traffic caused the bandwidth usage to be incorrectly attributed to the frontend network load balancing tier itself, rather than to the Drive service. The sequence of events leading to customer impact was as follows: * Traffic from the regional load balancing tier was incorrectly attributed to the load balancing infrastructure rather than the Drive service. * Unrelated traffic caused network bandwidth usage attributed to the load balancing infrastructure in this region to exceed its quota. * Network bandwidth management systems applied throttling to this traffic to enforce quotas, causing severe network congestion affecting Drive traffic in this region. * This congestion led to increased latency, slowness, and error rates for users accessing Drive in the affected regions. Remediation  Google engineers were alerted to the issue via automated monitoring and an influx of customer support cases, with initial incident response teams engaged by 17:21 US/Pacific on August 18, 2026. Engineers initially attempted to alleviate the congestion by draining regional frontend traffic to an alternate geographic location, but this proved ineffective and was reverted. The team then mitigated the issue by migrating regional traffic to an upgraded internal network routing architecture, which correctly set the traffic attribution for Drive. Normal operations were fully restored once 100% of the regional traffic was migrated to the upgraded network architecture. Description of Impact Between August 18, 2026, at 16:58 US/Pacific and August 19, 2026, at 05:40 US/Pacific, Google Drive users in Australia, Philippines and New Zealand experienced severe latency, degraded performance and 502 errors. During this roughly 12-hour and 42-minute window, affected customers may have observed significant slowness or errors when attempting to access Google Drive or listing files through Editors (e.g. docs.google.com (http://docs.google.com)), with initial load times significantly delayed. The issue was fully mitigated as of August 19, 2026, at 05:40 US/Pacific, and normal service has been restored.

Google drive: * Elevated Latency: Users experienced extreme slowness when loading the Drive interface or accessing files, with initial data retrieval times heavily delayed. * Loading Failures and Errors: Many user requests timed out or returned HTTP 502 errors due to the aggressive network throttling dropping the connections. Scope exclusion: * Customers accessing Google Drive from outside the Australia, Philippines and New Zealand regions were largely unaffected by this localized throttling event. * Other Google Workspace applications not reliant on this specific routing path remained stable during the incident window.

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.

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.

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

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

Description: We are experiencing an issue with Google Cloud Support beginning on Tuesday, 2026-06-30 02:03 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-06-30 05:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: None at this time.

Description: We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 06:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: None at this time.

Description: We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 06:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: Customers can continue to use the portal to add comments / notes.

Description: We believe the issue with Google Support is mitigated. Our engineering team continues to investigate the root cause. Customers are being advised if they have an urgent issue to resend previous communication to Google Support. We will provide an update by Tuesday, 2026-06-30 08:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: Customers can continue to use the portal to add comments / notes.

Description: We are experiencing an issue with Google Cloud Support beginning on Tuesday, 2026-06-30 02:03 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-06-30 08:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation continues to work. Workaround: Customers can continue to use the portal to add comments / notes.

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 Tuesday, 2026-06-30 08:45 PDT. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Tuesday, 2026-06-30 09:45 PDT. We will provide more information by Tuesday, 2026-06-30 10:00 PDT. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

Description: The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineering teams have shifted focus to replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. While there is currently no specific ETA for the email replay to finish, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 11:00 PDT. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

Description: The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 12:15 PDT. Symptoms: Inbound emails from customers to Google Support are experiencing issues. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

Description: The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 17:00 PDT. Symptoms: Inbound emails from customers to Google Support after 09:00 AM PDT on 30 June 2026 are working as expected. The affected emails from the time of the issue are being replayed. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

Description: The mitigation rollout was completed as of 09:00 AM PDT on 30 June 2026, and all incoming emails are currently being processed without further disruption. Our engineers are continuing to work replaying the inbound messages that were impacted between 25 June 2026 and 09:00 AM PDT on 30 June 2026. We expect the email replays to take several hours, please be advised that this backlog processing may cause case statuses to update dynamically or cause certain closed cases to temporarily reopen. We will provide more information by Tuesday, 2026-06-30 21:30 PDT. Symptoms: Inbound emails from customers to Google Support after 09:00 AM PDT on 30 June 2026 are working as expected. The affected emails from the time of the issue are being replayed. Case creation and updates continues to work without any issues. Workaround: Customers can continue to use the portal to add comments / notes.

Description: The issue with inbound emails to Google Cloud Support has been resolved for all affected customers as of Tuesday, 2026-06-30 20:45 PDT. From preliminary analysis, the engineering team identified a recent change which was preventing incoming emails from being processed. We have successfully rolled back the change to mitigate the impact. Backlog processing of all the affected emails is now complete. We thank you for your patience while we worked on resolving the issue. Symptoms: Inbound emails from customers to Google Support were experiencing issues. Case creation and updates continued to work without any issues. Workaround: None as the issue is resolved.