Live / Neo4j Aura / Incident
Neo4j Aura: Issue for some customers with instance metrics (endpoint and in Console).
Neo4j Aura · neo4j.ioMinor incidentResolved2026-10-08 19:11 UTC
Public — what happened
Summary
Neo4j Aura reported a minor problem with instance metrics, affecting both the metrics endpoint and the metrics shown in the Aura Console, beginning at 14:58 UTC on 2026-10-08. The company said only a portion of customers in the GCP us-central1 region were affected, and that databases kept running with no other operations impacted. Neo4j Aura said it was working with its cloud provider to understand and fix the problem, though it did not publicly name a cause. The incident was marked resolved at 19:11 the same day.
Affected
Aura Console (console.neo4j.io), Aura Customer Metrics (customer-metrics-api.neo4j.io)
Timeline
- Started — 2026-10-08 14:58 UTC
- Investigating — 2026-10-08 14:58 UTC
- Identified — 2026-10-08 15:36 UTC (3 updates)
- Resolved — 2026-10-08 19:11 UTC · 4h 13m 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.