{
  "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-04T04:36:47.967Z"
  },
  "data": {
    "id": "incident_statuspage_neo4j_qgty104t7rl5",
    "slug": "neo4j-issue-impacting-certain-database-operations-for-aura-customers-on-azure-2026-09-17",
    "title": "Issue impacting certain database operations for Aura customers on Azure",
    "summary": "Issue impacting certain database operations for Aura customers on Azure",
    "status": "resolved",
    "stale": false,
    "severity": "major",
    "startedAt": "2026-09-17T16:46:42.638+00:00",
    "updatedAt": "2026-10-16T16:24:18.102+00:00",
    "resolvedAt": "2026-09-17T19:55:19+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-issue-impacting-certain-database-operations-for-aura-customers-on-azure-2026-09-17",
      "api": "/api/v1/incidents/neo4j-issue-impacting-certain-database-operations-for-aura-customers-on-azure-2026-09-17",
      "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 major event for the affected tracked services.",
    "source": {
      "id": "source_neo4j_status",
      "kind": "official_api",
      "name": "Neo4j Aura Status",
      "checkedAt": "2026-11-04T04:30:11.557+00:00",
      "stale": false,
      "officialUrl": "https://status.neo4j.io",
      "statusPageUrl": "https://status.neo4j.io"
    },
    "updates": [
      {
        "id": "update_statuspage_neo4j_qgty104t7rl5_nhwbmb59x38k",
        "status": "investigating",
        "body": "We are currently aware of an issue that is impacting certain database operations, such as create, delete, clone for customers using Aura on Azure.",
        "createdAt": "2026-09-17T16:46:42.788+00:00"
      },
      {
        "id": "update_statuspage_neo4j_qgty104t7rl5_c349zmxjxtyq",
        "status": "identified",
        "body": "We have identified the issue and are working towards a solution. At this time, certain database operations, such as create, delete, and clone for customers using Neo4j Aura on Azure only, continue to be impacted.",
        "createdAt": "2026-09-17T17:11:27.86+00:00"
      },
      {
        "id": "update_statuspage_neo4j_qgty104t7rl5_kpzd5xd8bx22",
        "status": "monitoring",
        "body": "A fix has been deployed to all affected environments. We will monitor the situation to ensure that the fix fully resolves the issue.",
        "createdAt": "2026-09-17T19:06:50.775+00:00"
      },
      {
        "id": "update_statuspage_neo4j_qgty104t7rl5_3jfbld2jldy6",
        "status": "resolved",
        "body": "After deploying the fix, we monitored the impacted instances, operational metrics, and errors. This incident is now resolved. A post-mortem will be available as soon as it’s been completed.",
        "createdAt": "2026-09-17T19:55:19.955+00:00"
      },
      {
        "id": "update_statuspage_neo4j_qgty104t7rl5_88cvp46q6lgn",
        "status": "resolved",
        "body": "# What happened\n\nOn Thursday, 17 September 2026 at 13:52 UTC, a deployment-time conflict between concurrent operations caused a credential used by a core Aura component to authenticate with Azure-hosted infrastructure to be removed.\n\nAs existing authentication tokens expired, the component began returning errors for some Aura instances hosted on Azure, affecting certain database operations. We traced the errors to the missing credential, created a new one, stored it securely, and performed a rolling deployment of the affected component, which completed at 18:39 UTC.\n\nA small number of database creation requests that were in progress during the outage were left in an incomplete state and needed manual remediation. This was completed at 19:48 UTC, and the incident was marked resolved at 19:55 UTC.\n\n# How the service was affected\n\nThe impact was limited to Aura instances hosted on Azure. Other cloud providers were not affected.\n\n* **Database operations:** Customers were unable to perform certain database operations, such as create, delete, and clone, on some Azure instances during the incident window. A small number of creates that were in progress became stuck and were recovered manually.\n* **Management visibility:** Some Azure-hosted instances were temporarily not visible or manageable in Aura Console.\n* **Metrics gaps:** Metrics endpoints for some Azure instances returned intermittent errors, leaving short gaps in metrics data for the affected period. This data will not be backfilled.\n\nAzure instances that were already running remained available and continued to serve workloads normally.\n\n# What we are doing now\n\nWe are taking the following steps to help prevent a recurrence and improve our response:\n\n* **Earlier detection and communication:** We will improve monitoring and alerting, and evaluate automated credential checks, so issues are detected and customers are informed sooner.\n* **Recovery from incomplete database creation:** We will fix a defect that can leave a database creation stuck if an infrastructure call fails partway through, so the system recovers on its own.\n* **Authentication review:** We will review how this component authenticates with cloud providers, to remove single points of failure and reduce the risk of this type of conflict recurring.",
        "createdAt": "2026-10-16T16:23:05.379+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}