**Summary** Some customers may experience slowness while using Google Drive. **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.

# Incident Report ## Summary On Tuesday, 18 August 2026 at 16:58 US/Pacific, an incident affecting Google Drive occurred for a duration of 12 hours and 42 minutes. Customers located in Australia, Philippines and New Zealand experienced severe latency, sporadic loading failures, and errors when accessing Google Drive.  To our valued Google Workspace customers, we are deeply sorry for the service interruption you experienced. We are taking immediate and decisive action to address the issue and strengthen our systems against future incidents. Other Google Workspace services were not affected. ## 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 and Prevention 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 18 August , 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 at 05:40 once 100% of the regional traffic was migrated to the upgraded network architecture. To prevent a recurrence of this issue, our engineering teams are undertaking the following structural preventative actions: * **Resilient Network Protocol Migration:** We are expediting the complete migration of all regional frontend traffic to the newer, resilient network routing protocol to ensure accurate bandwidth attribution under all congestion scenarios. * **Delegation Root Cause Remediation:** We are addressing the underlying mechanism that caused the incorrect delegation and analyzing similar cases across the fleet to ensure it does not reoccur. ## Detailed Description of Impact From 18 August 2026, 16:58 to 19 August 2026, 05:40 US/Pacific for a duration of 12 hours, 42 minutes, Google Drive users in Australia, Philippines and New Zealand experienced severe performance degradation, including high latency and errors accessing Drive or listing files via Editors. Service was fully restored as of 19 August, 05:40 US/Pacific. **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. (Affected: Google Drive)