We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.
Last update on
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun 15, 2026 - 18:00 UTC
Last update on
We are continuing to work on a fix for this issue.
Last update on
We are performing maintenance in our Tokyo PoP. All announcements will be withdrawn from Tokyo and traffic will be rerouted to nearby PoPs for the duration of this maintenance event. This event will cause no disruption in service, however additional latency may be encountered for traffic normally attracted to Tokyo.
Last update on
**Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** A fire at a third-party data center facility required an emergency power shutdown of networking equipment, isolating a non-compute local Point of Presence (POP) in Delhi and reducing available network capacity in the metro area. We rerouted significant traffic from the impacted facility in Delhi to address reduced local serving capabilities. As a result, a subset of Hybrid Connectivity and Virtual Private Cloud (VPC) customers may be impacted by the routing changes made to address reduced local, latency-optimized serving capabilities in Delhi. Affected customers may experience intermittent latency spikes due to demand exceeding capacity across Indian metros and regional ISPs. Initial traffic mitigations have yielded positive results for some Cloud customers. In parallel, we are pursuing additional Internet Edge peering capacity to reduce latency in the local Delhi metropolitan area. Further, we are augmenting out-of-region Internet Edge regional peering capacity in Chennai to provide additional load-balancing and redundancy to large ISPs in India (expected to be done by Wednesday, 2026-06-17 PDT). We have optimized capacity across network backbones to increase available headroom. Additionally, we are further augmenting our Delhi backbone capacity (expected to be complete by Monday, 2026-06-15 PDT). We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Monday, 2026-06-15 17:00 PDT. **Symptoms** Customers may experience slightly elevated latency and non-optimal network routing into Google Cloud until the affected facility is fully restored. **Workaround** There is no workaround at this time.
Last update on
We have identified that users are experiencing an error when attempting to create an account using Google OAuth for the impacted services. We are working on implementing a mitigation.
Last update on
Monitors
Amazon Web Services
Cloudflare
MANDATORY MAINTENANCE: Server Restart Required
DNS Made Easy
Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss.
Google Cloud
VPS and Dedi Hosting
Adobe Creative Cloud
** Brochure Site - BYDP Alberta OneCall (Customer Owned)
Google Maps Platform
Jira Product Discovery
Jira Service Management
Microsoft 365 suite
[PelicanCorp] Mail Array Console