AuraDS snapshot restore failures

Affected Components

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

Updates

Resolved

October 6, 2026 at 02:04 PM UTC

The fix for AuraDS snapshot restore failures has been deployed to all customers, and the incident is resolved.

Monitoring

October 6, 2026 at 01:35 PM UTC

A fix for AuraDS snapshot restore failures is rolling out and affected customers should see functionality restored progressively.

Monitoring

October 6, 2026 at 12:14 PM UTC

A fix for AuraDS snapshot restore failures is being deployed and will roll out to affected customers shortly.

Identified

October 6, 2026 at 10:03 AM UTC

Fix for AuraDS snapshot restore failures is still in progress; teams continue working on the issue.

Identified

October 6, 2026 at 09:07 AM UTC

Root cause identified for AuraDS snapshot restore failures; fix is in progress.

Identified

October 6, 2026 at 08:07 AM UTC

A fix is ready for AuraDS snapshot restore issues and will be deployed soon; use backup restore meanwhile.