Live / Neo4j Aura / Incident
Neo4j Aura: Issue for some customers with instance metrics (endpoint and in Console)
Neo4j Aura · neo4j.ioMinor incidentResolved2026-10-13 12:08 UTC
Public — what happened
Summary
Neo4j Aura reported a minor problem affecting instance metrics for some customers, both in the Aura Console and through its metrics endpoint, beginning at 09:15 UTC on 2026-10-13. About an hour later, the company said it had traced the problem to an issue at its cloud service provider and had raised a support case with that provider. By 11:01 UTC, Neo4j Aura said its internal systems no longer showed problems and it was watching while awaiting confirmation from the provider. The incident was marked resolved at 12:08.
Affected
Aura Console (console.neo4j.io), Aura Customer Metrics (customer-metrics-api.neo4j.io)
Timeline
- Started — 2026-10-13 09:15 UTC
- Investigating — 2026-10-13 09:15 UTC
- Identified — 2026-10-13 10:13 UTC
- Monitoring — 2026-10-13 11:01 UTC
- Resolved — 2026-10-13 12:08 UTC · 2h 53m 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 43, 2026, our weekly internet health report.