Skip to content

Incident detail

Cloning to AuraDS from AuraDB fails

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 where customers doing a clone operation from AuraDB to AuraDS will see a failure. We will keep you updated as we determine the cause of the issue and work toward a resolution.

  2. Investigating

    We are currently investigating an issue where customers doing a clone operation from AuraDB to AuraDS will see a failure.

    We will keep you updated as we determine the cause of the issue and work toward a resolution.

  3. Investigating

    We are currently investigating an issue where customers doing a clone operation from AuraDB to AuraDS will see a failure.

    We will keep you updated as we determine the cause of the issue and work toward a resolution.

  4. Identified

    We have identified the root cause and can confirm that only cloning to AuraDS is impacted.

    A small subset of customers using AuraDS may be affected.

    We are working on a fix.

  5. Identified

    We have further narrowed down the root cause and can confirm that cloning from some existing AuraDB instances to other AuraDB or AuraDS instances is impacted.

    A small subset of customers using AuraDB may be affected. This effects ONLY existing AuraDB instances that are running version 5.20. To determine if you are impacted, use cypher to check your Neo4j version (see example).

    • call dbms.components() yield name, versions, edition unwind versions as version return name, version, edition;
    • Neo4j Kernel 5.20-aura enterprise

    We are working on a fix, which is to roll out 5.20. We will update this incident with an updated status on Monday, June 3rd.

  6. Resolved

    We have now completed the roll out of the 5.20 versions to all tiers of Aura and this now address the issues with cloning.

Keep exploring

More from Neo4j Aura

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