Live / Neo4j Aura / Incident
Neo4j Aura: Some Aura operations impacted currently for a single Cloud Service Provider
Neo4j Aura · neo4j.ioMinor incidentResolved2026-10-29 16:45 UTC
Public — what happened
Summary
Neo4j Aura said some of its operations were affected by a problem at a cloud service provider, starting at 09:06 UTC on 2026-10-29. The company said the problem touched a limited number of regions, naming brazilsouth, centralus, canadacentral and northeurope, and noted that this list could change. At 13:34 UTC Neo4j Aura said the provider had found the cause and was working on a fix, and by 16:09 UTC the fix was being rolled out while the company watched the situation. The incident was marked resolved at 16:45 UTC.
Affected
Azure AKS, Azure Private Link, AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io), AuraDB Professional on Azure (*.databases.neo4j.io), AuraDB Business Critical (*.databases.neo4j.io) on Azure, Azure Cloud Services (Compute), Azure Storage Services, Aura API (api.neo4j.io)
Timeline
- Started — 2026-10-29 09:06 UTC
- Investigating — 2026-10-29 09:06 UTC (6 updates)
- Identified — 2026-10-29 13:34 UTC
- Monitoring — 2026-10-29 16:09 UTC
- Resolved — 2026-10-29 16:45 UTC · 7h 39m 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.