Neo4j Aura experienced a minor incident on December 14, 2023 affecting AuraDB Free (*.databases.neo4j.io), lasting 1d 6h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Dec 14, 2023, 12:52 PM UTC
We have observed that some AuraDB Free users are experiencing issues with their instances. We are investigating.
- identified Dec 14, 2023, 02:13 PM UTC
We have identified some memory resource constraints on these instances and are working on a solution.
- identified Dec 14, 2023, 04:38 PM UTC
We continue to work on finding a fix for this issue and are making some progress.
- identified Dec 14, 2023, 06:43 PM UTC
We are continuing to work on this issue. We anticipate having it resolved tomorrow but we will continue to provide regular updates.
- monitoring Dec 14, 2023, 10:31 PM UTC
We are continuing to monitor the situation and will continue updating the status. We expect this to be resolved tomorrow.
- monitoring Dec 15, 2023, 12:34 AM UTC
We are continuing to monitor the situation. We are still expecting a resolution tomorrow.
- monitoring Dec 15, 2023, 03:38 AM UTC
We are continuing to monitor the situation and will continue updating the status. We expect this to be resolved tomorrow.
- monitoring Dec 15, 2023, 06:13 AM UTC
We are continuing to work on this issue. We anticipate having it resolved tomorrow and will continue providing regular updates.
- monitoring Dec 15, 2023, 08:11 AM UTC
We are continuing to monitor the situation. We are still expecting a resolution tomorrow.
- monitoring Dec 15, 2023, 10:14 AM UTC
We are continuing to monitor the situation. We are still expecting a resolution tomorrow.
- monitoring Dec 15, 2023, 12:47 PM UTC
We are continuing to monitor the situation. We are still expecting a resolution soon.
- monitoring Dec 15, 2023, 04:45 PM UTC
We are continuing to monitor the situation. We are still expecting a resolution soon.
- resolved Dec 15, 2023, 07:40 PM UTC
The incident has been resolved and free tier databases are no longer being affected by memory constraints. Please reach out to [email protected] if you are having problems with your instance.