Neo4j Aura Status Page

Oct 13, 2026 · resolved Oct 13

_**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._

Oct 8, 2026 · resolved Oct 8

_**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._

Oct 6, 2026 · resolved Oct 6

A fix has been deployed; snapshot downloads now contain the appropriate data.

Oct 6, 2026 · resolved Oct 6

We have deployed the fix to all customers.

Sep 17, 2026 · resolved Sep 17

# What happened On Thursday, 17 September 2026 at 13:52 UTC, a deployment-time conflict between concurrent operations caused a credential used by a core Aura component to authenticate with Azure-hosted infrastructure to be removed. As existing authentication tokens expired, the component began returning errors for some Aura instances hosted on Azure, affecting certain database operations. We traced the errors to the missing credential, created a new one, stored it securely, and performed a rolling deployment of the affected component, which completed at 18:39 UTC. A small number of database creation requests that were in progress during the outage were left in an incomplete state and needed manual remediation. This was completed at 19:48 UTC, and the incident was marked resolved at 19:55 UTC. # How the service was affected The impact was limited to Aura instances hosted on Azure. Other cloud providers were not affected. * **Database operations:** Customers were unable to perform certain database operations, such as create, delete, and clone, on some Azure instances during the incident window. A small number of creates that were in progress became stuck and were recovered manually. * **Management visibility:** Some Azure-hosted instances were temporarily not visible or manageable in Aura Console. * **Metrics gaps:** Metrics endpoints for some Azure instances returned intermittent errors, leaving short gaps in metrics data for the affected period. This data will not be backfilled. Azure instances that were already running remained available and continued to serve workloads normally. # What we are doing now We are taking the following steps to help prevent a recurrence and improve our response: * **Earlier detection and communication:** We will improve monitoring and alerting, and evaluate automated credential checks, so issues are detected and customers are informed sooner. * **Recovery from incomplete database creation:** We will fix a defect that can leave a database creation stuck if an infrastructure call fails partway through, so the system recovers on its own. * **Authentication review:** We will review how this component authenticates with cloud providers, to remove single points of failure and reduce the risk of this type of conflict recurring.

Is Neo4j Aura down right now?

No — Neo4j Aura is up. All systems operational as of Oct 18, 1:14 AM UTC.

What is Neo4j Aura's current status?

Neo4j Aura: All Systems Operational. Alert24 checks Neo4j Aura's status page continuously and can notify you the moment it changes.

How do I get alerted when Neo4j Aura goes down?

Alert24 monitors Neo4j Aura and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.