Skip to content
OutageDeck

Incident detail

Data science feature on AuraDS , AuraDSE and Aura Professional tiers - Native projection affected.

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Neo4j Aura breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Neo4j Aura alerts work

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Identified

    Impact is that currently it is not possible to load data into GDS via native projection.

    Customers using Aura Graph Analytics are not impacted.

    We have identified a packaging issue with the latest release of Aura.

    Our engineering team is working on a fix.

  2. Identified

    Our teams have a fix and initiated the work to get it ready to roll-out.

    No current ETA available.

    We will keep you updated soon.

  3. Monitoring

    The fix is currently rolling out to production. We will update you upon completion

  4. Resolved

    All instances should have the fix applied and if not it should be in the next 60 minutes

  5. Resolved

    ### What happened

    On January 15, 2026 at 22:12 UTC we began rolling out an update that included an incompatible version of a key component, affecting customers using the GDS plugin. This issue was reported on January 16 at 12:59 UTC, and a fix was deployed within hours, restoring functionality for the majority of affected users by 20:03 UTC.

    The issue occurred because Neo4’s packaging automation process selected the wrong version of the GDS component. GDS 2.25 should have been selected but instead GDS 2.24 was included in the bundle, which caused a compatibility issue. Although a corrected package was created and labeled separately, the release pipeline selected the incorrect package for deployment.

    This issue highlighted a gap in the release validation process, where incompatible component versions were not detected before rollout.

    ### How customers were affected

    Customers using the GDS plugin were unable to use any of the functionality the plugin provides during the incident window.

    The system configuration has been updated to ensure compatibility with the intended component versions, restoring full functionality.

    ### What we are doing now

    The following mitigations have been implemented:

    • Enhanced testing procedures to automatically verify compatibility between Neo4j and all bundled components before release.
    • Improved release processes to ensure that only explicitly validated and correctly labeled packages can be selected for deployment.