Skip to content

Incident detail

Operations requiring system database fail when not connected directly to the system database

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 have identified a problem with the routing of some internal messages which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves updating the system database while connected to the neo4j database. Such commands and queries might involve user management as an example.

    The workaround is to connect to the system database directly and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system". If using the Neo4j drivers, specify system as the database name to connect to.

    We are currently investigating the root cause and will update this incident with progress.

  2. Investigating

    We have identified a problem with the routing of some internal messages which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves updating the system database while connected to the neo4j database. Such commands and queries might involve user management as an example.

    The workaround is to connect to the system database directly and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system". If using the Neo4j drivers, specify system as the database name to connect to.

    We are currently investigating the root cause and will update this incident with progress.

  3. Investigating

    We have identified a problem with the routing of some internal messages which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. Such commands and queries might involve user management as an example.

    The workaround is to connect to the system database directly and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system". If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

    We are currently investigating the root cause and will update this incident with progress.

  4. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

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

  5. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

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

  6. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

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

  7. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

    The root cause has been identified, and we are working on rolling out a fix.

  8. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

    The root cause has been identified, and we are working on rolling out a fix.

  9. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

    The root cause has been identified, and we are working on rolling out a fix.

  10. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

    The root cause has been identified, and we are working on rolling out a fix.

  11. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

    The root cause has been identified, and we are working on rolling out a fix.

  12. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

    The root cause has been identified, and we are working on rolling out a fix.

  13. Identified

    We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

    The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

    The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".

    If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

    The root cause has been identified, and we are working on rolling out a fix.

  14. Resolved

    We have successfully rolled out a fix and this issue is now fixed.

Keep exploring

More from Neo4j Aura

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