Skip to content

Incident detail

AuraDB/DS : Some instance operations failing

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. Identified

    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.

  2. Identified

    We are continuing to work on a fix for this issue with our cloud partner.

  3. Identified

    We are continuing to work on a fix for this issue.

  4. Identified

    We are continuing to work on a fix for this issue.

  5. Identified

    We are continuing to work on a fix for this issue with our cloud partner.

  6. Identified

    We are continuing to work on a fix for this issue.

  7. Identified

    We are continuing to work on a fix for this issue with our cloud partner.

  8. Identified

    We are continuing to work on a fix for this issue.

  9. Identified

    We are continuing to work on a fix for this issue.

  10. Identified

    We are continuing to work on a fix for this issue.

  11. Identified

    We are continuing to work on a fix for this issue.

  12. Identified

    We are continuing to work on a fix for this issue.

  13. Identified

    We are continuing to work on a fix for this issue with our cloud partner.

  14. Identified

    We are continuing to work on a fix for this issue with our cloud partner.

  15. Identified

    We are continuing to work on a fix for this issue.

  16. Identified

    We are continuing to work on a fix for this issue.

  17. Identified

    We are continuing to work on a fix for this issue.

  18. Identified

    We are continuing to work on a fix for this issue with our cloud partner.

  19. Identified

    We are continuing to work on a fix for this issue with our cloud partner.

  20. Identified

    We are continuing to work on a fix for this issue.

  21. Identified

    We are continuing to work on a fix for this issue with our cloud partner.

  22. Identified

    We are continuing to work on a fix for this issue.

  23. Monitoring

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

  24. Resolved

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

Keep exploring

More from Neo4j Aura

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