While this situation continues, you must reconfigure your backups to a different region. To provision a new storage location and reconfigure your backups, reach out to the Support team. Our team will provide any additional assistance needed during the temporary relocation. Please feel free to contact the Druva support team at support.druva.com. Druva Support
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. Media CDN customers may have experienced higher latencies than normal. Initial traffic mitigations have yielded positive results for some Cloud customers. We have restored a portion of 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 have augmented our Delhi backbone capacity over the weekend. We will continue to closely monitor latency deviations and packet drops. We will provide our next update by Wednesday, 2026-06-17 at 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 detected a possible outage with Microsoft Teams that is not officially acknowledged.
Last update on
We’ve verified a fix for this issue and are progressing through the Emergency Release process to obtain the necessary approvals for deployment. The fix requires a code change, which we are developing and validating in a test environment before deploying to production. This validation ensures the fix resolves the issue without introducing additional impact and will take some time to complete. Upon further investigation, we've determined that the start time of impact is different than initially understood. We’ve now aligned the start time to the recent release that went out during the weekend to more accurately reflect on Trust. We'll provide an update in 60 minutes or sooner if additional information becomes available.
Last update on
Monitors
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
Possible outage: Status and availability not updating correctly
Microsoft Teams
Salesforce
Adobe Creative Cloud
Amazon Web Services
Tungsten Automation/Printix