Provider
Neo4j AuraIncident detail
Pause / Resume / Destroy operations failing
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.
Identified
We have identified an issue resulting in Pause, Resume and Delete operations to fail in both Console and Aura API across all tiers of Aura. We are actively working to resolve the issue and will report progress.
Monitoring
We have released a fix to this issue and are monitoring to ensure all operations are back to normal.
Resolved
After monitoring the fix for some time, we can confirm that the issue is resolved and normal operations have resumed.
Resolved
### What happened
On November 18, 2025, some customers experienced issues with the delete, pause, and resume operations in the Console. These actions failed due to a temporary system issue introduced during a sequence of updates. While the updates were intended to improve functionality, they unintentionally reintroduced a previously resolved defect.
The issue was identified quickly, and our teams acted immediately to restore normal operation.
The root cause was a misconfiguration in the data processing module. An outdated schema caused the data parsing logic to misinterpret certain input parameters, leading to incorrect behavior and data display within the Console. We have since corrected the schema and added stricter validation to ensure compatibility moving forward.
### How customers were affected
During the incident, some users experienced service disruptions when accessing the Console. Impacts included:
- Intermittent connectivity issues
- Inability to log in
- Temporary unavailability of specific Console features
No customer data was lost.
To prevent a recurrence, we have improved our release process to ensure updates are deployed in the correct order, eliminating overlapping or out-of-sequence changes.
### What we are doing now
Neo4j takes service reliability seriously and is strengthening safeguards to prevent similar incidents.
New mitigations being deployed include:
- Enhanced monitoring to detect related issues earlier
- Additional automated checks to block faulty configurations before deployment
- Improvements to overall service resilience to better tolerate similar failures
We apologize for the disruption and appreciate our customers’ patience as we continue to harden our systems.
Keep exploring
More from Neo4j Aura
Neighboring incidents on Neo4j Aura's timeline and the rest of their record on OutageDeck.