Neo4j Aura incident

Potential unexpected query failures.

Resolved after 1 day 22 hours, affecting AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io) and AuraDB Professional on AWS (*.databases.neo4j.io) and 1 more, on August 5, 2026.

resolved Aug 07, 2026, 03:34 PM UTC

We have monitored the fix and found the service to be stable. This incident is now considered resolved.

Started
Aug 05, 2026, 05:31 PM UTC
Resolved
Aug 07, 2026, 03:34 PM UTC
Duration
1d 22h
Detected by Pingoru
Aug 05, 2026, 05:31 PM UTC

Affected components

AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io)AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AWSAuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on Azure

Update timeline

  1. investigating Aug 05, 2026, 05:31 PM UTC

    We have identified an issue currently that could result in unexpected query failures when using the trim() Cypher function. Investigations into the cause are in progress.

  2. identified Aug 05, 2026, 07:27 PM UTC

    We have found the issue and are working on a fix. A small percentatge of queries using trim may still err. VDC customers with databases set to highest are not impacted at all unless they pause and start their instances.

  3. identified Aug 06, 2026, 12:58 AM UTC

    We are testing the fix for the trim() Cypher function issue. We will update before we begin our deployment into the Aura environment.

  4. identified Aug 06, 2026, 07:13 AM UTC

    We are actively validating the fix for the trim() Cypher function. Further updates will be provided before we begin deploying to Aura instances

  5. identified Aug 06, 2026, 07:39 AM UTC

    We continue to validate the fix for the trim() Cypher function. Further updates will be provided before we begin deploying it to Aura instances.

  6. identified Aug 06, 2026, 11:17 AM UTC

    We continue to validate the fix for the trim() Cypher function. Further updates will be provided before we begin deploying it to Aura instances.

  7. identified Aug 06, 2026, 02:54 PM UTC

    The fix for the trim() Cypher function is undergoing testing and validation before deployment. Further updates will be provided before we begin deploying it to Aura instances.

  8. identified Aug 07, 2026, 01:15 AM UTC

    Development has completed on the hot-fix for this issue, and we are finalizing the rollout plan for Aura.

  9. identified Aug 07, 2026, 01:16 AM UTC

    We are actively working on addressing the issue. The fix for the trim() Cypher function is undergoing testing and validation currently before deployment. Further updates will be provided before we begin deploying it to Aura instances.

  10. identified Aug 07, 2026, 09:44 AM UTC

    The fix to the trim() Cypher function has passed testing and validation and is now being deployed.

  11. monitoring Aug 07, 2026, 01:49 PM UTC

    The fix to resolve the issue has now completed deployment to the Aura service and we are monitoring the situation.

  12. resolved Aug 07, 2026, 03:34 PM UTC

    We have monitored the fix and found the service to be stable. This incident is now considered resolved.

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.

Add your stack →