Is Neo4j Aura down?
Last checked 4m agoNo incidents right now.
Neo4j Aura is operational right now. Last checked 4m ago; the most recent incident resolved 18d ago.
Real-time Neo4j Aura status, recent outages, and incident history — pulled directly from Neo4j Aura's official status page at https://status.neo4j.io every 5 minutes. Pingoru tracks 86 Neo4j Aura services and has captured 1 incident in the last 90 days (99.98% uptime). Get email, Slack, Discord, or webhook alerts the moment Neo4j Aura reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Aura Console (console.neo4j.io)
Timeline · 4 updates
- investigating · May 26, 2026, 06:23 PM UTC
Aura Console is currently not accessible. Our team is investigating the issue. Aura instances are running normally and are not impacted. Console-related administration and configuration procedures may be unavailable. We will provide updates as soon as more information is available.
- monitoring · May 26, 2026, 07:19 PM UTC
The Aura Console issue has now been resolved. The root cause was a failure while fetching public certificates from Auth0. We are reaching out to the Auth0 team to gather more detailed information about the incident.
- resolved · May 26, 2026, 11:06 PM UTC
This incident has been resolved.
- postmortem · Jun 09, 2026, 04:50 PM UTC
**What Happened** During the incident window, users attempting to log in to the Aura Console were unable to do so. Auth0, the authentication provider for Aura Console, experienced an issue that prevented new authentication requests from completing. Existing sessions with valid cached tokens were largely unaffected. Aura database instances were running normally throughout and were not impacted, and access via the Aura API to database instances was also unaffected. **How the service was affected** Authentication requests from the Aura Console to Auth0 began failing, preventing new logins and session refreshes. Affected users received 503 errors when accessing the Aura Console. Once Auth0 recovered, access was restored. **What are we doing now** We've made two changes as a result of this incident: * Client identification: Authentication requests now include a clearer client identifier, reducing the chance of requests being incorrectly blocked in the future. * Observability: We've improved logging and alerting for authentication failures, including better visibility into errors from external services,so we can detect and escalate issues like this faster.
Latest: **What Happened** During the incident window, users attempting to log in to the Aura Console were unable to do so. Auth0, the authentication provider for Aura Console, experienced …
-
- Aura Console Auth error ResolvedStarted May 26, 2026, 06:23 PM UTC · Resolved May 26, 2026, 11:06 PM UTC · 4h 43m