🟢 Operational
RESOLVED: **Summary:** We experienced intermittent latency with Google Drive **Description:** The issue with Google Drive has been resolved for all affected customers as of Wednesday, 2026-09-16 07:41 PDT. We thank you for your patience while we worked on resolving the issue. **Customer Symptoms:** Users may have been unable to access Google Drive, experienced intermittent latency, or were unexpectedly prompted with CAPTCHAs when attempting to use the service. **Workaround:** Users were advised
Resolved
- Started
- 2026-09-16 16:36 UTC
5 days ago - Last update
- 2026-09-18 10:06 UTC
3 days ago - Duration
- 0s
Timeline
-
18 Sep · 10:06 UTC
🟠 Resolved
atom
Incident began at 2026-09-16 14:04 and ended at 2026-09-16 14:41 (times are in Coordinated Universal Time (UTC)).
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 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: 16 September 2026 07:03
Incident End: 16 September 2026 07:51
Duration: 0 hours, 47 minutes
Summary
On Wednesday, 16 September 2026, Google Workspace (specifically Google Drive) experienced an issue where a subset of traffic was dropped for a duration of 48 minutes.
Preliminary Root Cause
This incident was triggered by a planned capacity test, which temporarily reduced Google Drive's serving capacity.
The sequence of events leading to the impact was as follows:
Engineers initiated a routine capacity test, causing Drive to operate with reduced capacity.
The remaining available capacity was insufficient to handle peak user traffic.
As traffic exceeded capacity, the capacity protection system was triggered and began blocking legitimate Drive requests.
Remediation
The issue was detected on Wednesday 16 September 2026 at 7:03 via automated outage detectors monitoring error rates and user queries.
To mitigate the symptoms, Google engineers initiated an immediate rollback of the capacity test to restore serving capacity. Additionally, engineers performed manual upsizing operations to provide mor -
18 Sep · 10:06 UTC
🟠 Resolved
atom
Incident began at 2026-09-16 14:04 and ended at 2026-09-16 14:41 (times are in Coordinated Universal Time (UTC)).
Incident Report
Summary
On Wednesday, 16 September 2026, Google Drive experienced an issue where a subset of traffic was dropped for a duration of 39 minutes.
We sincerely apologize for the disruption this incident caused to your business. We recognize the critical role Google Cloud plays in your operations and deeply regret the impact on your services. Our engineering teams have resolved the issue and have taken immediate measures to address the incident. Additionally, engineering teams are conducting a comprehensive review of the incident to fully address the root cause and prevent the recurrence of such an event.
Root Cause
This incident was triggered by a planned capacity test which temporarily reduced Google Drive's serving capacity.
The sequence of events leading to the impact was as follows:
Engineers initiated a routine capacity test, causing Drive to operate with reduced capacity.
The remaining available capacity was insufficient to handle peak user traffic.
As traffic exceeded capacity, the capacity protection system was triggered and began blocking legitimate Drive requests.
Remediation and Prevention
The issue was detected on Wednesday 16 September 2026 at 7:03 via our automated outage detector systems that monitor error rates and user queries.
To mitigate the symptoms, Google engineers initiated an immediate rollback of the capacity test to restore serving capacity. Additionally, engineers upsized available capacity and updated the system load limit threshold to add more capacity headroom.
Google is committed to preventing a repeat of this issue in the future and is completing the following immediate actions:
Resilience and Resourcing: Ensure sufficient buffer capacity is available globally during capacity tests.
Address the Root Cause: Engineering is conducting a comprehensive review of capacity modeling and protection thresholds to en -
16 Sep · 20:14 UTC
🟠 Resolved
atom
Incident began at 2026-09-16 14:04 and ended at 2026-09-16 14:41 (times are in Coordinated Universal Time (UTC)).
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 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: 16 September 2026 07:03
Incident End: 16 September 2026 07:51
Duration: 0 hours, 47 minutes
Summary
On Wednesday, 16 September 2026, Google Workspace (specifically Google Drive) experienced an issue where a subset of traffic was dropped for a duration of 48 minutes.
Preliminary Root Cause
This incident was triggered by a planned capacity test, which temporarily reduced Google Drive's serving capacity.
The sequence of events leading to the impact was as follows:
Engineers initiated a routine capacity test, causing Drive to operate with reduced capacity.
The remaining available capacity was insufficient to handle peak user traffic.
As traffic exceeded capacity, the capacity protection system was triggered and began blocking legitimate Drive requests.
Remediation
The issue was detected on Wednesday 16 September 2026 at 7:03 via automated outage detectors monitoring error rates and user queries.
To mitigate the symptoms, Google engineers initiated an immediate rollback of the capacity test to restore serving capacity. Additionally, engineers performed manual upsizing operations to provide mor -
16 Sep · 20:14 UTC
🟡 Resolved
atom
Incident began at 2026-09-16 14:04 and ended at 2026-09-16 14:41 (times are in Coordinated Universal Time (UTC)).
Summary:
We experienced intermittent latency with Google Drive
Description:
The issue with Google Drive has been resolved for all affected customers as of Wednesday, 2026-09-16 07:41 PDT.
We thank you for your patience while we worked on resolving the issue.
Customer Symptoms:
Users may have been unable to access Google Drive, experienced intermittent latency, or were unexpectedly prompted with CAPTCHAs when attempting to use the service.
Workaround:
Users were advised to retry actions.
Affected products: Google Drive -
16 Sep · 16:36 UTC
🟡 Resolved
atom
Incident began at 2026-09-16 14:04 and ended at 2026-09-16 14:41 (times are in Coordinated Universal Time (UTC)).
Summary:
We experienced intermittent latency with Google Drive
Description:
The issue with Google Drive has been resolved for all affected customers as of Wednesday, 2026-09-16 07:41 PDT.
We thank you for your patience while we worked on resolving the issue.
Customer Symptoms:
Users may have been unable to access Google Drive, experienced intermittent latency, or were unexpectedly prompted with CAPTCHAs when attempting to use the service.
Workaround:
Users were advised to retry actions.
Affected products: Google Drive
Source
Official Google Workspace status — view original incident ↗
IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.