{
  "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-18T20:14:56.101Z"
  },
  "data": {
    "id": "incident_statuspage_neo4j_jjdwq8sbn4zl",
    "slug": "neo4j-some-issues-with-backups-2025-08-19",
    "title": "Some issues with backups",
    "summary": "Some issues with backups",
    "status": "resolved",
    "stale": false,
    "severity": "minor",
    "startedAt": "2025-08-19T09:19:36.139+00:00",
    "updatedAt": "2025-09-12T19:42:06.338+00:00",
    "resolvedAt": "2025-08-19T12:04:18.329+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-some-issues-with-backups-2025-08-19",
      "api": "/api/v1/incidents/neo4j-some-issues-with-backups-2025-08-19",
      "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-18T20:10:16.01+00:00",
      "stale": false,
      "officialUrl": "https://status.neo4j.io",
      "statusPageUrl": "https://status.neo4j.io"
    },
    "updates": [
      {
        "id": "update_statuspage_neo4j_jjdwq8sbn4zl_sgrvflcn3kq9",
        "status": "investigating",
        "body": "We are currently investigating an issue with backups. We will update shortly as we get more details",
        "createdAt": "2025-08-19T09:19:36.562+00:00"
      },
      {
        "id": "update_statuspage_neo4j_jjdwq8sbn4zl_8p460gb77j42",
        "status": "investigating",
        "body": "We are continuing to investigate the issue with backups. New backups after 0:00 last night are failing to complete.\nExisting backups are unaffected and remain available.",
        "createdAt": "2025-08-19T10:05:22.393+00:00"
      },
      {
        "id": "update_statuspage_neo4j_jjdwq8sbn4zl_vxkln5r8ldmh",
        "status": "investigating",
        "body": "We are continuing to investigate this issue.",
        "createdAt": "2025-08-19T10:34:35.986+00:00"
      },
      {
        "id": "update_statuspage_neo4j_jjdwq8sbn4zl_w0skn51hxwxh",
        "status": "investigating",
        "body": "We continue to investigate and have identified the issue more clearly.\n\nBeyond backups, other operations are also affected: pause and clone. \n\nOperations may fail or take a long time to complete.",
        "createdAt": "2025-08-19T10:51:47.829+00:00"
      },
      {
        "id": "update_statuspage_neo4j_jjdwq8sbn4zl_yv870cd255mf",
        "status": "monitoring",
        "body": "The fix has been deployed and we will continue to monitor this incident.",
        "createdAt": "2025-08-19T11:30:18.808+00:00"
      },
      {
        "id": "update_statuspage_neo4j_jjdwq8sbn4zl_vdmpcj0btcgn",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2025-08-19T12:04:18.329+00:00"
      },
      {
        "id": "update_statuspage_neo4j_jjdwq8sbn4zl_3z2zd9vmdnlw",
        "status": "resolved",
        "body": "### What happened\n\nOn August 18, 2025, at 19:18 UTC, the release of a faulty component in Neo4j Aura impacted the ability to perform backups of customer instances. The problem was identified when a critical component was updated without aligning with another dependent component, leading to failed backup attempts. This resulted in Neo4j not being able to take backups of customer instances for a period of approximately 17 hours. Our team quickly identified the root cause and began mitigation efforts early on August 19, 2025. By 11:54 UTC, the issue was fully resolved, and normal backup operations resumed. We apologize for any inconvenience this may have caused and are taking steps to prevent similar issues in the future.\n\nThe issue arose because the deployment of the neo4j-backup system was not properly synchronized with the deployment of the neo4j-operator. This misalignment led to critical changes being introduced that impacted the ability to create new backups effectively. Essentially, the two components were not updated in harmony, which caused disruptions in the backup process.\n\n### How customers were affected\n\nCustomers were unable to  get successful backups of their instances for 17 hours. We promptly addressed the issue by reverting the recent backup changes that caused disruptions and ensured the stability of our service by cleaning up old, failing backups.\n\n### What we are doing now\n\nNeo4j remains committed to providing reliable service and is implementing additional safeguards to prevent similar incidents in the future.\n\nNew mitigations being deployed:\n\n* Enhancing our monitoring systems to detect similar issues faster\n* Implementing additional automated checks to prevent service disruptions\n* Improving our service resilience to handle similar scenarios",
        "createdAt": "2025-09-12T19:41:27.518+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}