Console is not available

Update timeline

1. identified Mar 06, 2026, 10:18 AM UTC

   We identified an issue with the availability of console.neo4j.io - we are investigating

2. monitoring Mar 06, 2026, 10:24 AM UTC

   We have made a code change and we believe the console is available again.

3. resolved Mar 06, 2026, 10:25 AM UTC

   We have checked and confirm that the issue is now fully addressed.

4. postmortem Mar 30, 2026, 07:25 AM UTC

   ## What Happened On March 6, at 10:04 AM UTC, the Aura Console became inaccessible following a recent deployment. The deployment included changes related to user organizations and switching to an org memberships entity. This change caused the console to become inaccessible for a short period. ## How the service was affected A deployment to the Aura Console introduced an issue that caused an unexpected increase in backend requests related to access validation. This led to elevated CPU usage, which impacted the availability of the console and dependent services. We rolled back to a previous version to restore access. The rollback ensured the full restoration of access to the Aura Console, resolving the core issue within the incident window ## What are we doing now We are currently implementing a comprehensive strategy to bolster system resilience and prevent future recurrence. Our immediate actions include integrating stricter and more robust safeguards into the deployment pipeline. Crucially, we are significantly enhancing our validation processes to proactively detect and flag any potential performance impacts _before_ code is promoted to the production environment