Neo4j Aura incident

Enterprise AuraDB tier backup scheduler operations degraded

Minor Resolved View vendor source →

Neo4j Aura experienced a minor incident on May 24, 2024 affecting AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io) and AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io) and 1 more component, lasting 3d 16h. The incident has been resolved; the full update timeline is below.

Started
May 24, 2024, 03:29 PM UTC
Resolved
May 28, 2024, 08:24 AM UTC
Duration
3d 16h
Detected by Pingoru
May 24, 2024, 03:29 PM UTC

Affected components

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)

Update timeline

  1. identified May 24, 2024, 03:29 PM UTC

    The automated backup scheduler for the AuraDB Enterprise tier is experiencing issues and currently defaults to running backups every 9-10 hours. To get your backups running hourly, please use the Aura API (see https://neo4j.com/docs/aura/platform/api/specification/#/instances/post-snapshots ). We are working on a fix and expect a roll out after 2024-05-27.

  2. identified May 28, 2024, 01:19 AM UTC

    The automated backup scheduler for the AuraDB Enterprise tier is experiencing issues and currently defaults to running backups every 9-10 hours. To get your backups running hourly, please use the Aura API (see https://neo4j.com/docs/aura/platform/api/specification/#/instances/post-snapshots ). We are rolling out the fix and will continue to update you as things progress.

  3. identified May 28, 2024, 07:19 AM UTC

    The automated backup scheduler for the AuraDB Enterprise tier is experiencing issues and currently defaults to running backups every 9-10 hours. To get your backups running hourly, please use the Aura API (see https://neo4j.com/docs/aura/platform/api/specification/#/instances/post-snapshots ). We are rolling out the fix and will continue to update you as things progress.

  4. resolved May 28, 2024, 08:24 AM UTC

    This issue is now resolved and the backup scheduler fix has been rolled out.