Resolved -
Services are confirmed to be operational and no further interruptions are expected.
Jul 10, 19:23 UTC
Monitoring -
The third-party service that Aura depends on has restored normal operations and the Neo4j Aura systems have recovered.
Our team is actively monitoring the issue to confirm Aura Console is performing as expected.
Jul 10, 17:51 UTC
Update -
We are continuing to investigate this issue.
Jul 10, 17:23 UTC
Investigating -
We are currently investigating an issue affecting the Aura Console where some customers may be unable to see their instances. This issue is caused by a failure in a third-party service that Aura depends on. Affected instances continue to run normally, and database connectivity is not impacted.
Our team is actively investigating the issue.
Jul 10, 17:18 UTC
Resolved -
The fix has been fully deployed to all impacted instances. This incident is now resolved.
Jun 30, 17:45 UTC
Monitoring -
A fix is rolling out and progressing well. We will update with progress.
Jun 30, 16:05 UTC
Update -
We are starting now to deploy a fix to address this issue and will provide an update soon on progress.
Jun 30, 15:41 UTC
Identified -
Running CREATE VECTOR INDEX fails with error 51N31 error: system configuration or operation exception - not supported. Creating a vector index with provided settings is not supported in V2026_02. Required version for operation is V2026_06. Please upgrade DBMS..
This only affects new index, existing VECTOR INDEX are unaffected. Any vector index created prior to 2026-06-30 at 09:00 continue to operate normally.
Jun 30, 14:45 UTC