Neo4j Aura incident

Limited set of queries impacted by Cypher 25 issue

Neo4j Aura experienced a minor incident on January 26, 2026 affecting AuraDB Professional on AWS (*.databases.neo4j.io) and AuraDS on AWS (*.databases.neo4j.io) and 1 more component, lasting 20h 31m. The incident has been resolved; the full update timeline is below.

Started: Jan 26, 2026, 07:26 PM UTC
Resolved: Jan 27, 2026, 03:58 PM UTC
Duration: 20h 31m
Detected by Pingoru: Jan 26, 2026, 07:26 PM UTC

Affected components

AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Professional on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)AuraDB Free (*.databases.neo4j.io)

Update timeline

identified Jan 26, 2026, 07:26 PM UTC

We have identified an issue that may affect a limited set of Cypher 25 queries for AuraDB Free, Professional and AuraDS. This may affect: - Queries using the conditional query WHEN in combination with a non-grouping aggregation over null values result in an incorrect number of rows returned. - Queries using NEXT can produce an unexpected variable not defined error in some instances. We are actively working on a fix and will update this page as more information becomes available.
identified Jan 27, 2026, 01:37 AM UTC

We have identified a solution for this issue and will be rolling out in Aura. Once the update has been deployed we will update this tatus page.
identified Jan 27, 2026, 09:50 AM UTC

We are rolling out the fix and will update you when this is completed.
monitoring Jan 27, 2026, 11:10 AM UTC

The fix has rolled out to the affected components, we are now monitoring the situation at this time.
monitoring Jan 27, 2026, 02:51 PM UTC

We are continuing to monitor the situation at this time.
resolved Jan 27, 2026, 03:58 PM UTC

The fix has been fully deployed to all impacted instances. This incident is now resolved.