Neo4j Aura incident

AuraDB/DS : Some instance operations failing

Resolved after 4 days 3 hours, affecting AuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io) and AuraDB Professional on GCP (*.databases.neo4j.io) and 1 more, on October 21, 2024.

monitoring Oct 25, 2024, 09:49 AM UTC

Our cloud provider has put in place some mitigating changes. We are working at validating the effectiveness of the change.

Started: Oct 21, 2024, 12:21 PM UTC
Resolved: Oct 25, 2024, 03:56 PM UTC
Duration: 4d 3h
Detected by Pingoru: Oct 21, 2024, 12:21 PM UTC

Affected components

AuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io)AuraDB Professional on GCP (*.databases.neo4j.io)AuraDS Enterprise on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on GCPAuraDB Free (*.databases.neo4j.io)

Update timeline

identified Oct 21, 2024, 12:21 PM UTC

Some operations (Resume, Restore from backup, Loading, and Clone) on Aura instances are impacted and may not complete successfully. We are working closely with our cloud provider on a solution.
identified Oct 21, 2024, 03:30 PM UTC

We are continuing to work on a fix for this issue with our cloud partner.
identified Oct 21, 2024, 07:21 PM UTC

We are continuing to work on a fix for this issue.
identified Oct 21, 2024, 11:56 PM UTC

We are continuing to work on a fix for this issue.
identified Oct 22, 2024, 03:38 AM UTC

We are continuing to work on a fix for this issue with our cloud partner.
identified Oct 22, 2024, 06:47 AM UTC

We are continuing to work on a fix for this issue.
identified Oct 22, 2024, 10:23 AM UTC

We are continuing to work on a fix for this issue with our cloud partner.
identified Oct 22, 2024, 04:16 PM UTC

We are continuing to work on a fix for this issue.
identified Oct 22, 2024, 09:01 PM UTC

We are continuing to work on a fix for this issue.
identified Oct 23, 2024, 01:00 AM UTC

We are continuing to work on a fix for this issue.
identified Oct 23, 2024, 05:19 AM UTC

We are continuing to work on a fix for this issue.
identified Oct 23, 2024, 10:12 AM UTC

We are continuing to work on a fix for this issue.
identified Oct 23, 2024, 01:27 PM UTC

We are continuing to work on a fix for this issue with our cloud partner.
identified Oct 23, 2024, 04:48 PM UTC

We are continuing to work on a fix for this issue with our cloud partner.
identified Oct 23, 2024, 08:10 PM UTC

We are continuing to work on a fix for this issue.
identified Oct 24, 2024, 12:21 AM UTC

We are continuing to work on a fix for this issue.
identified Oct 24, 2024, 05:20 AM UTC

We are continuing to work on a fix for this issue.
identified Oct 24, 2024, 12:28 PM UTC

We are continuing to work on a fix for this issue with our cloud partner.
identified Oct 24, 2024, 03:22 PM UTC

We are continuing to work on a fix for this issue with our cloud partner.
identified Oct 24, 2024, 10:14 PM UTC

We are continuing to work on a fix for this issue.
identified Oct 25, 2024, 01:18 AM UTC

We are continuing to work on a fix for this issue with our cloud partner.
identified Oct 25, 2024, 04:56 AM UTC

We are continuing to work on a fix for this issue.
monitoring Oct 25, 2024, 09:49 AM UTC

Our cloud provider has put in place some mitigating changes. We are working at validating the effectiveness of the change.
resolved Oct 25, 2024, 03:56 PM UTC

Our cloud provider fix is working well and we have not observed any issues.

Your product runs on more than Neo4j Aura

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.