Neo4j Aura incident

AuraDS affected by issues when attempting to restore from snapshot

Resolved after 5 hours 56 minutes, affecting AuraDS on AWS (*.databases.neo4j.io) and AuraDS Enterprise on AWS (*.databases.neo4j.io) and 1 more, on October 6, 2026.

monitoring Oct 06, 2026, 01:35 PM UTC

The fix is rolling out and affected customers should see the functionality restored progressively.

Started: Oct 06, 2026, 08:07 AM UTC
Resolved: Oct 06, 2026, 02:04 PM UTC
Duration: 5h 56m
Detected by Pingoru: Oct 06, 2026, 08:07 AM UTC

Affected components

AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDS Enterprise on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)

Update timeline

identified Oct 06, 2026, 08:07 AM UTC

We have identified an issue when attempting to restore from snapshots on AuraDS. We have a fix ready and will deploy this soon. In the meantime you can restore from a backup instead.
identified Oct 06, 2026, 09:07 AM UTC

We have clearly identified the root cause and continue to work on a fix for this issue.
identified Oct 06, 2026, 10:03 AM UTC

We continue to work on a fix for this issue.
identified Oct 06, 2026, 12:14 PM UTC

A fix is being deployed and will roll out to affected customers shortly.
monitoring Oct 06, 2026, 01:35 PM UTC

The fix is rolling out and affected customers should see the functionality restored progressively.
resolved Oct 06, 2026, 02:04 PM UTC

We have deployed the fix to all customers.

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.