Update
We continue to fix a small subset of Free instances that are still impacted.
Update
We addressed the issue in all AuraDB Professional instances. Aura Free can still be affected. We will continue to monitor and fix the remaining databases.
Update
We continue to fix a small subset of instances that are still impacted under the AuraDB Professional and Free tiers.
Update
We continue to fix a subset of instances that are still impacted for AuraDB Professional and Free
Update
We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free
Update
We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free.
Update
We continue to resolve the subset of instances which are still impacted for AuraDB Professional and Free.
Update
AuraDB Virtual Dedicated Cloud and AuraDB Business Critical should all now be fixed. We continue to resolve the subset of instances which are still impacted for AuraDB Professional and Free.
Monitoring
We continue to resolve the subset of instances which are still impacted.
Update
We continue to resolve the subset of instances which are still impacted.
Update
We are continuing to resolve the subset of instances still impacted.
Update
We are continuing to resolve the subset of instances still impacted.
Update
We are continuing to resolve the subset of instances still impacted.
Update
With the configuration fix deployed, we are continuing to resolve the subset of instances still impacted.
Update
We have deployed a configuration fix and are now working to resolve the subset of instances impacted.
Update
We have identified the subset of instances impacted and continue to deploy the fix at this time.
Update
We are deploying the first part of the fix and continue actively working on rolling out the full solution. We expect an ETA in the order of 1hour from now.
Identified
We have identified the cause of the current issue and are actively working on the fix currently.
Update
We are working with engineering teams and continuing to make progress with the investigations at the current time.
Update
We are working with engineering teams and making progress with the investigations at the current time.
Investigating
We are currently investigating an issue at this time.
This incident affects: AuraDB Virtual Dedicated Cloud (*.databases.neo4j.io) (AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io), AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io), AuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io)), AuraDB Professional (*.databases.neo4j.io) (AuraDB Professional on AWS (*.databases.neo4j.io), AuraDB Professional on Azure (*.databases.neo4j.io), AuraDB Professional on GCP (*.databases.neo4j.io)), AuraDS (*.databases.neo4j.io) (AuraDS on AWS (*.databases.neo4j.io), AuraDS on Azure (*.databases.neo4j.io), AuraDS on GCP (*.databases.neo4j.io)), AuraDS Enterprise (*.databases.neo4j.io) (AuraDS Enterprise on AWS (*.databases.neo4j.io), AuraDS Enterprise on Azure (*.databases.neo4j.io), AuraDS Enterprise on GCP (*.databases.neo4j.io)), AuraDB Business Critical (*.databases.neo4j.io) (AuraDB Business Critical (*.databases.neo4j.io) on AWS, AuraDB Business Critical (*.databases.neo4j.io) on Azure, AuraDB Business Critical (*.databases.neo4j.io) on GCP), and Aura API (api.neo4j.io), AuraDB Free (*.databases.neo4j.io).