Live / Neo4j Aura / Incident
Neo4j Aura: Issue impacting certain database operations for Aura customers on Azure
Neo4j Aura · neo4j.ioMinor incidentResolved2026-10-26 19:14 UTC
Public — what happened
Summary
Neo4j Aura said that customers running Aura on Azure had trouble downloading snapshots of their database instances, and it began looking into the problem at 14:50 UTC on 2026-10-26. By 15:09 UTC the company said it had identified the issue and was preparing a fix, which it then tested in lower environments before release, with testing still ongoing at 17:43 UTC. Neo4j Aura marked the incident, which it rated minor, as resolved at 19:14 UTC.
Affected
AuraDB 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, Aura API (api.neo4j.io)
Timeline
- Started — 2026-10-26 14:50 UTC
- Investigating — 2026-10-26 14:50 UTC
- Identified — 2026-10-26 15:09 UTC (3 updates)
- Resolved — 2026-10-26 19:14 UTC · 4h 23m 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 45, 2026, our weekly internet health report.