Skip to content

Incident detail

Some issues with backups

Resolved incidentMinor2 affected services

Timeline window

to

Get alerted the next time Neo4j Aura breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are currently investigating an issue with backups. We will update shortly as we get more details

  2. Investigating

    We are continuing to investigate the issue with backups. New backups after 0:00 last night are failing to complete.

    Existing backups are unaffected and remain available.

  3. Investigating

    We are continuing to investigate this issue.

  4. Investigating

    We continue to investigate and have identified the issue more clearly.

    Beyond backups, other operations are also affected: pause and clone.

    Operations may fail or take a long time to complete.

  5. Monitoring

    The fix has been deployed and we will continue to monitor this incident.

  6. Resolved

    This incident has been resolved.

  7. Resolved

    ### What happened

    On August 18, 2025, at 19:18 UTC, the release of a faulty component in Neo4j Aura impacted the ability to perform backups of customer instances. The problem was identified when a critical component was updated without aligning with another dependent component, leading to failed backup attempts. This resulted in Neo4j not being able to take backups of customer instances for a period of approximately 17 hours. Our team quickly identified the root cause and began mitigation efforts early on August 19, 2025. By 11:54 UTC, the issue was fully resolved, and normal backup operations resumed. We apologize for any inconvenience this may have caused and are taking steps to prevent similar issues in the future.

    The issue arose because the deployment of the neo4j-backup system was not properly synchronized with the deployment of the neo4j-operator. This misalignment led to critical changes being introduced that impacted the ability to create new backups effectively. Essentially, the two components were not updated in harmony, which caused disruptions in the backup process.

    ### How customers were affected

    Customers were unable to  get successful backups of their instances for 17 hours. We promptly addressed the issue by reverting the recent backup changes that caused disruptions and ensured the stability of our service by cleaning up old, failing backups.

    ### What we are doing now

    Neo4j remains committed to providing reliable service and is implementing additional safeguards to prevent similar incidents in the future.

    New mitigations being deployed:

    • Enhancing our monitoring systems to detect similar issues faster
    • Implementing additional automated checks to prevent service disruptions
    • Improving our service resilience to handle similar scenarios

Keep exploring

More from Neo4j Aura

Neighboring incidents on Neo4j Aura's timeline and the rest of their record on OutageDeck.