Live / Neo4j Aura / Incident
Neo4j Aura: AuraDS affected by issues when attempting to restore from snapshot
Neo4j Aura · neo4j.ioMinor incidentResolved2026-10-06 14:04 UTC
Public — what happened
Summary
Neo4j Aura reported a minor problem on October 6, 2026, starting at 08:07 UTC, in which restoring AuraDS databases from snapshots was not working, and it suggested using a backup as a workaround in the meantime. The company said it had pinned down the underlying cause but did not describe what it was. A fix began deploying at 12:14 UTC, and from 13:35 UTC the company said affected customers would gradually regain the ability to restore. The incident was marked resolved at 14:04.
Affected
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)
Timeline
- Started — 2026-10-06 08:07 UTC
- Identified — 2026-10-06 08:07 UTC (4 updates)
- Monitoring — 2026-10-06 13:35 UTC
- Resolved — 2026-10-06 14:04 UTC · 5h 57m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Neo4j Aura against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Neo4j Aura: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Neo4j Aura report →
More from Neo4j Aura
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.