Provider
Neo4j AuraIncident detail
CMI & Instance Operations Unavailable
Timeline window
to
Get alerted the next time Neo4j Aura breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
Engineers are investigating an issue whereby instance actions are not working. You may be unable to import data, pause, resume, create, delete or run manual backups for your instances. Regular Neo4j scheduled backups are continuing to run as normal.
You may be unable to see your instances in the Aura Console.
CMI is also experiencing an outage, you may be unable to ingest metrics from your Aura instances.
Monitoring
A fix has been identified and implemented. Instances should be showing on the console and instance operations should now be available.
You should now also be able to ingest metrics using CMI.
We are continuing to monitor the status of these services.
Resolved
This incident has been resolved.
Resolved
### What happened
On August 22, 2025, from 10:10 to 11:27 UTC, users experienced an issue with the Aura Console where instance operations were unavailable. This was due to a timing issue with refreshing security keys that affected the visibility and operations of instances in the Aura Console and also caused an outage in the Customer Metrics Integration (CMI) and Aura API. The issue was identified within 5 minutes and efforts to resolve it began promptly. The problem was traced back to a recent update and issues with authentication were resolved by refreshing the system cache, with the service fully restored by 11:27 UTC.
The issue arose because of a timing mismatch between the creation of new security keys and their recognition by our system. When new keys were generated, they were quickly used by the Console API. However, another part of our system, the database manager, was still using an older set of keys to verify requests. This mismatch caused requests to fail because the database manager could not recognize the new keys. No unauthorized operations were allowed and this did not affect the security of the service in any way. After approximately an hour, the system automatically updated its keys, and everything started working correctly again.
### How customers were affected
Aura Console features were impacted, including the visibility of instances and therefore ability to connect to instances through the console. Driver connections to instances were not impacted.
The issue also impacted the use of parts of the service including Customer Metrics Integration (CMI) and the Aura API.
### What we are doing now
Neo4j remains committed to providing reliable service and is implementing additional safeguards to prevent similar incidents in the future.
We are taking steps to prevent similar issues in the future by improving our processes and monitoring systems.
Changes we are making:
- Enhancing our caching mechanisms to ensure seamless updates and prevent similar issues in the future.
- Designing a robust process for updating service accounts and keys to guarantee uninterrupted service reliability.
Keep exploring
More from Neo4j Aura
Neighboring incidents on Neo4j Aura's timeline and the rest of their record on OutageDeck.