Neo4j Aura incident
AuraDB Free tier: query performance degraded
Neo4j Aura experienced a minor incident on April 23, 2024 affecting AuraDB Free (*.databases.neo4j.io), lasting 2d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 23, 2024, 10:33 AM UTC
We are currently investigating an issue where some queries are not performing well.
- identified Apr 23, 2024, 12:27 PM UTC
We have identified the issue more precisely and continue to work on a fix.
- identified Apr 23, 2024, 02:26 PM UTC
We have identified the root cause and are working on rolling out a fix.
- identified Apr 23, 2024, 04:31 PM UTC
We are preparing and fix and will roll this out at our next opportunity.
- identified Apr 23, 2024, 06:16 PM UTC
We are continuing to get a fix rolled out. We do not currently have an ETA but we will continue to update you on a regular cadence.
- identified Apr 23, 2024, 09:20 PM UTC
We are continuing to work on a fix for this issue.
- identified Apr 23, 2024, 11:25 PM UTC
We are continuing to work on getting a fix rolled out. We will continue to update you as things progress.
- identified Apr 24, 2024, 04:00 AM UTC
We are continuing to get a fix rolled out. We do not currently have an ETA, but we will continue to update you on a regular basis.
- identified Apr 24, 2024, 07:01 AM UTC
We are continuing to work on getting a fix rolled out. We will continue to update you as things progress.
- identified Apr 24, 2024, 10:01 AM UTC
We are continuing to get a fix rolled out. We do not currently have an ETA, but we will continue to update you on a regular basis.
- identified Apr 24, 2024, 12:28 PM UTC
We are continuing to work on getting a fix rolled out. We will continue to update you as things progress.
- identified Apr 24, 2024, 04:04 PM UTC
We are continuing to work on getting a fix rolled out. We will continue to update you as things progress.
- identified Apr 24, 2024, 10:32 PM UTC
We are continuing to work on getting a fix rolled out. We will continue to update you as things progress.
- identified Apr 25, 2024, 01:47 AM UTC
We are continuing to get a fix rolled out. We do not currently have an ETA, but we will continue to update you on a regular basis.
- identified Apr 25, 2024, 04:30 AM UTC
We are continuing to work on getting a fix rolled out. We will continue to update you as things progress.
- identified Apr 25, 2024, 07:30 AM UTC
We are continuing to work on getting a fix rolled out. We will continue to update you as things progress.
- identified Apr 25, 2024, 09:54 AM UTC
We are rolling out the fix and will continue to update you as things progress.
- monitoring Apr 25, 2024, 12:35 PM UTC
A fix has been rolled out and we are monitoring the effects and validating this address the issues.
- resolved Apr 25, 2024, 01:05 PM UTC
This issue has now been resolved and the performance is restored.
- postmortem Jul 17, 2024, 03:32 PM UTC
### **What happened** A new feature to optimize query execution relating to the eager operation was released. Under some conditions certain Cypher statements with MERGE and CREATE operations would become inefficient on low resourced instances consuming more memory. ### **How the service was affected** Some queries would fail to complete or take an abnormal level of resources. This was mostly affecting AuraDB Free users or smaller instances of the Professional tier \(1GB RAM\) due to the limited resources available in both compute and memory. ### **What we are doing now** * We are now specifically testing on small instances * Benchmarking the features on low resources machines before rolling out