Skip to content

Incident detail

AuraDB Free tier: query performance degraded

Resolved incidentMinor1 affected service

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 some queries are not performing well.

  2. Identified

    We have identified the issue more precisely and continue to work on a fix.

  3. Identified

    We have identified the root cause and are working on rolling out a fix.

  4. Identified

    We are preparing and fix and will roll this out at our next opportunity.

  5. Identified

    We are continuing to get a fix rolled out. We do not currently have an ETA but we will continue to update you on a regular cadence.

  6. Identified

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

  7. Identified

    We are continuing to work on getting a fix rolled out. We will continue to update you as things progress.

  8. Identified

    We are continuing to get a fix rolled out.

    We do not currently have an ETA, but we will continue to update you on a regular basis.

  9. Identified

    We are continuing to work on getting a fix rolled out.

    We will continue to update you as things progress.

  10. Identified

    We are continuing to get a fix rolled out.

    We do not currently have an ETA, but we will continue to update you on a regular basis.

  11. Identified

    We are continuing to work on getting a fix rolled out.

    We will continue to update you as things progress.

  12. Identified

    We are continuing to work on getting a fix rolled out.

    We will continue to update you as things progress.

  13. Identified

    We are continuing to work on getting a fix rolled out.

    We will continue to update you as things progress.

  14. Identified

    We are continuing to get a fix rolled out.

    We do not currently have an ETA, but we will continue to update you on a regular basis.

  15. Identified

    We are continuing to work on getting a fix rolled out.

    We will continue to update you as things progress.

  16. Identified

    We are continuing to work on getting a fix rolled out.

    We will continue to update you as things progress.

  17. Identified

    We are rolling out the fix and will continue to update you as things progress.

  18. Monitoring

    A fix has been rolled out and we are monitoring the effects and validating this address the issues.

  19. Resolved

    This issue has now been resolved and the performance is restored.

  20. Resolved

    ### What happened

    A new feature to optimize query execution relating to the eager operation was released. Under some conditions certain Cypher statements with MERGE and CREATE operations would become inefficient on low resourced instances consuming more memory.

    ### How the service was affected

    Some queries would fail to complete or take an abnormal level of resources. This was mostly affecting AuraDB Free users or smaller instances of the Professional tier (1GB RAM) due to the limited resources available in both compute and memory.

    ### What we are doing now

    • We are now specifically testing on small instances 
    • Benchmarking the features on low resources machines before rolling out

Keep exploring

More from Neo4j Aura

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