Neo4j Aura incident
Issue for some customers with instance metrics (endpoint and in Console).
Resolved after 4 hours 13 minutes, affecting Aura Console (console.neo4j.io) and Aura Customer Metrics (customer-metrics-api.neo4j.io), on October 8, 2026.
_**Errors when sending metrics from GCP us-central1**_ _**What happened**_ _On Thursday, October 8, 2026 at 14:05 UTC, metrics from some instances in GCP us-central1 stopped being delivered. The cause was an issue on the Google Cloud side that incorrectly rejected valid metric requests. Metric delivery resumed at 18:00 UTC after Google Cloud applied a fix, and we resolved the incident at 18:48 UTC._ _Instances remained available throughout this event, with no impact to query performance or data integrity. Only metrics visibility was temporarily affected._ _**How the service was affected**_ _Customers saw gaps in instance metrics:_ * _**Console metrics:** Instances in GCP us-central1 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 affected, and other cloud providers and regions were unaffected._ _**What we are doing now**_ _The fix came from Google Cloud, but we are taking steps to catch and respond to similar events sooner:_ * _**Alerting on metric delivery errors:** We are adding alerting on metric forwarding error rates, so provider-side failures are detected earlier and distinguished from routine gaps._ * _**Continued monitoring:** We will keep monitoring the region with Google Cloud for any recurrence._
Affected components
Update timeline
- investigating Oct 08, 2026, 02:58 PM UTC
We are investigating an issue with metrics in the Aura Console and via the metric endpoint.
- identified Oct 08, 2026, 03:36 PM UTC
We continue to investigate the root cause. The issue is limited to customers on us-central1 on GCP Aura instances are running and no operation is affected.
- identified Oct 08, 2026, 04:30 PM UTC
We are working with the cloud service provider to investigate the nature of the issue. Our checks confirm that only a subset of customers running in the us-central1 regions are affected.
- identified Oct 08, 2026, 05:30 PM UTC
We continue to work with the cloud service provider to get a solution.
- identified Oct 08, 2026, 06:41 PM UTC
We continue to work with the cloud service provider to get a solution.
- resolved Oct 08, 2026, 07:11 PM UTC
This incident has now been resolved, metrics should now operate as normal.
- postmortem Oct 16, 2026, 05:04 PM UTC
_**Errors when sending metrics from GCP us-central1**_ _**What happened**_ _On Thursday, October 8, 2026 at 14:05 UTC, metrics from some instances in GCP us-central1 stopped being delivered. The cause was an issue on the Google Cloud side that incorrectly rejected valid metric requests. Metric delivery resumed at 18:00 UTC after Google Cloud applied a fix, and we resolved the incident at 18:48 UTC._ _Instances remained available throughout this event, with no impact to query performance or data integrity. Only metrics visibility was temporarily affected._ _**How the service was affected**_ _Customers saw gaps in instance metrics:_ * _**Console metrics:** Instances in GCP us-central1 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 affected, and other cloud providers and regions were unaffected._ _**What we are doing now**_ _The fix came from Google Cloud, but we are taking steps to catch and respond to similar events sooner:_ * _**Alerting on metric delivery errors:** We are adding alerting on metric forwarding error rates, so provider-side failures are detected earlier and distinguished from routine gaps._ * _**Continued monitoring:** We will keep monitoring the region with Google Cloud for any recurrence._
Your product runs on more than Neo4j Aura
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.