Issue for some customers with instance metrics (endpoint and in Console)

Update timeline

1. investigating Oct 13, 2026, 09:15 AM UTC

   We are investigating an issue impacting metrics in the Aura Console and via the metric endpoint.

2. identified Oct 13, 2026, 10:13 AM UTC

   We have identified that a Cloud Service Provider related issue is impacting the current issue. We have opened a support case with the Cloud Service Provider and will update further once we have more detail.

3. monitoring Oct 13, 2026, 11:01 AM UTC

   We believe that the Cloud Service Provider issue has been resolved, as we are no longer seeing issues from our internal systems. We will continue to monitor the situation, while we wait for confirmation from the Cloud Service provider.

4. resolved Oct 13, 2026, 12:08 PM UTC

   We have had confirmation from the Cloud Service Provider that the issue has now been fully resolved.

5. postmortem Oct 16, 2026, 05:06 PM UTC

   _**Errors when sending metrics from GCP europe-west1**_ _**What happened**_ _On Tuesday, October 13, 2026 at 08:54 UTC, metrics for instances in GCP europe-west1 stopped being delivered and could not be read. The cause was an issue on the Google Cloud side, where a capacity reduction in its monitoring service led to valid requests being incorrectly rejected. Metrics returned to normal at 10:49 UTC after Google Cloud applied a fix, and we resolved the incident at 12:08 UTC once Google Cloud confirmed full resolution._ _Instances remained available throughout this event, with no impact to query performance or data integrity. Only metrics visibility was affected._ _**How the service was affected**_ _Customers saw some short gaps in instance metrics:_ * _**Console metrics:** Instances in GCP europe-west1 may have shown incomplete or missing metric data during the incident window._ * _**Cloud Monitoring Integration \(CMI\):** Metrics forwarded to your own monitoring systems from this region may also have had gaps._ _Not all instances in the region were impacted, and other cloud providers and regions were unaffected. Metrics generated during the incident were not recorded, so the gap will remain in historical charts for affected instances._ _**What we are doing now**_ _The fix came from Google Cloud on this occasion, but our metrics pipeline relied on a single-region path, so we are taking steps to reduce that exposure:_ * _**Regional resilience:** We are evaluating cross-region routing so metrics traffic can fail over to a healthy region._ * _**Traffic routing:** We are exploring options in our cloud networking layer to reroute both reads \(Console and CMI\) and writes \(ingestion\) away from an impacted region._