{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Teams, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-11-18T23:13:03.895Z"
  },
  "data": {
    "id": "incident_statuspage_neo4j_ncwz447htvfv",
    "slug": "neo4j-operations-requiring-system-database-fail-when-not-connected-directly-2024-05-31-447htvfv",
    "title": "Operations requiring system database fail when not connected directly to the system database",
    "summary": "Operations requiring system database fail when not connected directly to the system database",
    "status": "resolved",
    "stale": false,
    "severity": "minor",
    "startedAt": "2024-05-31T22:03:20.012+00:00",
    "updatedAt": "2024-06-04T09:56:51.726+00:00",
    "resolvedAt": "2024-06-04T09:56:51.709+00:00",
    "provider": {
      "slug": "neo4j",
      "name": "Neo4j Aura"
    },
    "affectedServices": [
      {
        "slug": "neo4j-auradb",
        "name": "AuraDB"
      },
      {
        "slug": "neo4j-aurads",
        "name": "Graph Data Science"
      }
    ],
    "links": {
      "html": "/incidents/neo4j-operations-requiring-system-database-fail-when-not-connected-directly-2024-05-31-447htvfv",
      "api": "/api/v1/incidents/neo4j-operations-requiring-system-database-fail-when-not-connected-directly-2024-05-31-447htvfv",
      "providerHtml": "/providers/neo4j",
      "alerts": "https://outagedeck.com/account?stack=neo4j&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Neo4j Aura reported a minor event for the affected tracked services.",
    "source": {
      "id": "source_neo4j_status",
      "kind": "official_api",
      "name": "Neo4j Aura Status",
      "checkedAt": "2026-11-18T23:10:12.093+00:00",
      "stale": false,
      "officialUrl": "https://status.neo4j.io",
      "statusPageUrl": "https://status.neo4j.io"
    },
    "updates": [
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_vdnnwdgpkblx",
        "status": "investigating",
        "body": "We have identified a problem with the routing of some internal messages which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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.\n\nWe are currently investigating the root cause and will update this incident with progress.",
        "createdAt": "2024-05-31T22:03:20.265+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_l7kjwx2phtwm",
        "status": "investigating",
        "body": "We have identified a problem with the routing of some internal messages which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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.\n\nWe are currently investigating the root cause and will update this incident with progress.",
        "createdAt": "2024-06-01T04:04:37.032+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_g87qwncjczkn",
        "status": "investigating",
        "body": "We have identified a problem with the routing of some internal messages which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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.\n\nWe are currently investigating the root cause and will update this incident with progress.",
        "createdAt": "2024-06-01T10:17:17.185+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_d01bz3yvb3lb",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nWe have identified the root cause and are working on rolling out a fix.",
        "createdAt": "2024-06-01T17:36:51.746+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_sgrg2vrq7zcn",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nWe have identified the root cause and are working on rolling out a fix.",
        "createdAt": "2024-06-02T01:00:17.984+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_n9hx86n1cb7h",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nWe have identified the root cause and are working on rolling out a fix.",
        "createdAt": "2024-06-02T07:02:15.886+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_7l2rnxcb0sv9",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nThe root cause has been identified, and we are working on rolling out a fix.",
        "createdAt": "2024-06-02T13:28:39.9+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_73yk0mg4sk9t",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nThe root cause has been identified, and we are working on rolling out a fix.",
        "createdAt": "2024-06-02T19:00:17.987+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_qzxnvgyccg0t",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nThe root cause has been identified, and we are working on rolling out a fix.",
        "createdAt": "2024-06-03T01:00:17.826+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_kq4w5qvp6t66",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nThe root cause has been identified, and we are working on rolling out a fix.",
        "createdAt": "2024-06-03T07:02:35.144+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_xpdtpnbphvnb",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nThe root cause has been identified, and we are working on rolling out a fix.",
        "createdAt": "2024-06-03T13:19:42.998+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_yj3ddst7hvxz",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nThe root cause has been identified, and we are working on rolling out a fix.",
        "createdAt": "2024-06-04T01:08:46.452+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_z1r8bxjv7g0x",
        "status": "identified",
        "body": "We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.\n\nThe 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.\n\nThe 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\". \nIf using the Neo4j drivers, specify \"system\" as the database name to connect to in the driver's code.\n\nThe root cause has been identified, and we are working on rolling out a fix.",
        "createdAt": "2024-06-04T07:00:16.346+00:00"
      },
      {
        "id": "update_statuspage_neo4j_ncwz447htvfv_7kfj3cyz4mhg",
        "status": "resolved",
        "body": "We have successfully rolled out a fix and this issue is now fixed.",
        "createdAt": "2024-06-04T09:56:51.709+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}