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)

As listed on Neo4j Aura’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Neo4j Aura status & history page.

Related: Neo4j Aura status & history. SquidGrid is not affiliated with Neo4j Aura.