The fix is rolling out and affected customers should see the functionality restored progressively.
Posted Oct 06, 2026 - 13:35 UTC
Update
A fix is being deployed and will roll out to affected customers shortly.
Posted Oct 06, 2026 - 12:14 UTC
Update
We continue to work on a fix for this issue.
Posted Oct 06, 2026 - 10:03 UTC
Update
We have clearly identified the root cause and continue to work on a fix for this issue.
Posted Oct 06, 2026 - 09:07 UTC
Identified
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.
Posted Oct 06, 2026 - 08:07 UTC
This incident affected: AuraDS (*.databases.neo4j.io) (AuraDS on AWS (*.databases.neo4j.io), AuraDS on Azure (*.databases.neo4j.io), AuraDS on GCP (*.databases.neo4j.io)) and AuraDS Enterprise (*.databases.neo4j.io) (AuraDS Enterprise on AWS (*.databases.neo4j.io), AuraDS Enterprise on Azure (*.databases.neo4j.io), AuraDS Enterprise on GCP (*.databases.neo4j.io)).
