{
  "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-18T01:11:05.919Z"
  },
  "data": {
    "id": "incident_statuspage_neo4j_vlgflb6y1qv7",
    "slug": "neo4j-auradb-instances-on-aws-affected-by-unavailability-2024-04-29",
    "title": "AuraDB instances on AWS affected by unavailability",
    "summary": "AuraDB instances on AWS affected by unavailability",
    "status": "resolved",
    "stale": false,
    "severity": "major",
    "startedAt": "2024-04-29T08:57:33+00:00",
    "updatedAt": "2024-05-01T10:03:02.54+00:00",
    "resolvedAt": "2024-04-29T12:33:04+00:00",
    "provider": {
      "slug": "neo4j",
      "name": "Neo4j Aura"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/neo4j-auradb-instances-on-aws-affected-by-unavailability-2024-04-29",
      "api": "/api/v1/incidents/neo4j-auradb-instances-on-aws-affected-by-unavailability-2024-04-29",
      "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-18T01:10:12.279+00:00",
      "stale": false,
      "officialUrl": "https://status.neo4j.io",
      "statusPageUrl": "https://status.neo4j.io"
    },
    "updates": [
      {
        "id": "update_statuspage_neo4j_vlgflb6y1qv7_hrqxvj2bg337",
        "status": "monitoring",
        "body": "Some AuraDB instances running on AWS have lost temporarily availability before recovering automatically.",
        "createdAt": "2024-04-30T15:57:33.436+00:00"
      },
      {
        "id": "update_statuspage_neo4j_vlgflb6y1qv7_d2m1sw34hkq4",
        "status": "resolved",
        "body": "This incident is now resolved",
        "createdAt": "2024-04-30T15:58:04.58+00:00"
      },
      {
        "id": "update_statuspage_neo4j_vlgflb6y1qv7_xy1j7vkzztk8",
        "status": "resolved",
        "body": "## **What happened**\n\nOn 2024-04-29 at 08:57:35 UTC, Neo4j implemented a code update that had unintended consequences for our infrastructure management.\n\nThe aforementioned code introduced a bug in our cluster management tool, which became apparent when an update to our Kubernetes clusters resulted in the termination of VMs hosting certain databases. While the system self-healed, this led to instances becoming temporarily unavailable for some AWS customers.\n\nSince our code rollout occurs progressively across environments, the impact was staggered across AWS service tiers.\n\n## **How the service was affected**\n\nSome of our AWS customers \\(running instances up to 32GB of RAM\\) experienced a <10 minute service interruption between 2024-04-29 08:57:35 UTC and 2024-04-29 12:33:40 UTC when the last batch of impacted databases completed the self-healing process.\n\nThe impact occurred during multiple time intervals. Each interval affected a different group of instances, resulting in shorter recovery times for individual instances.\n\nThis occurred in the following time intervals as the roll out was staggered:\n\n* 08:57:35 - 09:09:50 UTC\n* 09:11:55 - 09:25:05 UTC\n* 09:37:05 - 09:48:55 UTC\n* 10:08:35 - 10:20:50 UTC\n* 11:13:00 - 11:27:10 UTC\n* 12:10:20 - 12:23:40 UTC\n* 12:19:30 - 12:33:40 UTC\n\n## **What we are doing now**\n\nAfter conducting a comprehensive analysis of the situation, we are taking decisive actions to prevent such incidents from occurring in the future. Our efforts fall into two key areas:\n\n##### **Immediate Actions:**\n\n* Enhancing monitoring and alert systems for the underlying Aura infrastructure, with a focus on detecting and responding to individual \\(or small groups of\\) database unavailability promptly.\n* Strengthening testing protocols and code review processes to identify and address bugs in the components managing Cloud Infrastructure at an earlier stage.\n\nThese measures are aimed at ensuring the reliability and stability of our services moving forward.",
        "createdAt": "2024-04-30T15:59:09.809+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}