Provider
Neo4j AuraIncident detail
Database instance write performance impacted
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
We are currently investigating this issue.
Investigating
We are aware of an issue that could result in a degradation in write performance for all Aura instance. We have identified the cause and are preparing a fix.
Investigating
We are continuing to investigate this issue.
Monitoring
The issue impact has been refined and currently could impact AuraDB Virtual Dedicated Cloud and Business Critical instances only. We have identified the cause and the faulty component has been reverted for the majority of instances.
We will continue to monitor the situation, while the full fix is prepared.
Monitoring
We continue to work towards the issue resolution.
Monitoring
We continue to work towards the issue resolution.
Monitoring
We are continuing to investigate this issue.
Monitoring
We are continuing to monitor the situation whilst a full fix for the solution is prepared.
Monitoring
We are continuing to monitor the situation. The full fix for the solution is currently undergoing final testing and will start deployment once testing is completed.
Monitoring
The full fix for the solution is starting to be deployed across the estate and are continuing to monitor the situation.
Monitoring
The full fix for the solution is starting to be deployed across the estate and are continuing to monitor the situation.
Monitoring
The full fix for the solution is starting to be deployed across the estate and are continuing to monitor the situation.
Monitoring
We are continuing to monitor for any further issues.
Monitoring
The full fix for the solution is continuing to be deployed across the estate and are continuing to monitor the situation.
Resolved
The full fix for the solution has now been deployed across the estate and this issue is now resolved.
Resolved
### What happened
Between August 22 and August 28, 2025, a performance issue affected some of our database services following a recent update. Our team quickly responded and discovered that the problem was due to a bug in the latest update, which caused certain memory settings to be incorrectly configured. We promptly applied the previous version of those settings to stabilize the affected databases. By August 28, all databases were successfully transferred to a new, stable version, and the incident was fully resolved.
The issue was caused by a misconfiguration in the system's data processing module. Specifically, an incorrect parameter setting in the data pipeline led to a bottleneck, which slowed down the processing speed. This misconfiguration affected the way data was being queued and processed, resulting in delays. Our technical team has identified the root cause and implemented a fix to ensure that the data pipeline operates efficiently, preventing future occurrences of this issue.
### How the service was affected
Some customers reported a performance change on their instance.
### What we are doing now
Neo4j remains committed to providing reliable service and is implementing additional safeguards to prevent similar incidents in the future.
New mitigations being deployed:
- Enhancing our monitoring systems to detect similar issues faster
- Implementing additional automated checks to prevent service disruptions
- Improving our service resilience to handle similar scenarios
- Introducing dynamic configuration management to ensure seamless updates
- Enabling multiple configuration defaults to better manage database priorities
- Improving notification systems for faster response to potential issues
- Enhancing our tools to streamline database management and transfers
Keep exploring
More from Neo4j Aura
Neighboring incidents on Neo4j Aura's timeline and the rest of their record on OutageDeck.