{
  "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-03T08:35:04.530Z"
  },
  "data": {
    "id": "incident_statuspage_harness_vnjt1dx2wvjc",
    "slug": "harness-api-login-failures-2026-09-15",
    "title": "API Login failures",
    "summary": "API Login failures",
    "status": "resolved",
    "stale": false,
    "severity": "critical",
    "startedAt": "2026-09-15T17:22:37+00:00",
    "updatedAt": "2026-09-29T00:11:27.571+00:00",
    "resolvedAt": "2026-09-15T17:43:21.281+00:00",
    "provider": {
      "slug": "harness",
      "name": "Harness"
    },
    "affectedServices": [
      {
        "slug": "harness-platform",
        "name": "Platform & dashboards"
      }
    ],
    "links": {
      "html": "/incidents/harness-api-login-failures-2026-09-15",
      "api": "/api/v1/incidents/harness-api-login-failures-2026-09-15",
      "providerHtml": "/providers/harness",
      "alerts": "https://outagedeck.com/account?stack=harness&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Harness reported a critical event for the affected tracked services.",
    "source": {
      "id": "source_harness_status",
      "kind": "official_api",
      "name": "Harness Status",
      "checkedAt": "2026-11-03T08:30:12.664+00:00",
      "stale": false,
      "officialUrl": "https://status.harness.io",
      "statusPageUrl": "https://status.harness.io"
    },
    "updates": [
      {
        "id": "update_statuspage_harness_vnjt1dx2wvjc_j6qpv66f497j",
        "status": "investigating",
        "body": "We are currently investigating this issue.",
        "createdAt": "2026-09-15T17:40:37.071+00:00"
      },
      {
        "id": "update_statuspage_harness_vnjt1dx2wvjc_qwmgdcs26nmk",
        "status": "identified",
        "body": "The issue has been identified and a fix is being implemented.",
        "createdAt": "2026-09-15T17:40:46.673+00:00"
      },
      {
        "id": "update_statuspage_harness_vnjt1dx2wvjc_0gp70yf6r500",
        "status": "monitoring",
        "body": "A fix has been implemented and we are monitoring the results.",
        "createdAt": "2026-09-15T17:43:11.589+00:00"
      },
      {
        "id": "update_statuspage_harness_vnjt1dx2wvjc_1brw1kvdch0t",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2026-09-15T17:43:21.281+00:00"
      },
      {
        "id": "update_statuspage_harness_vnjt1dx2wvjc_z2wdchq3xsyj",
        "status": "resolved",
        "body": "# Root Cause Analysis Report\n\n## Brief API Login Failures Due to a Security Policy Misconfiguration\n\n## 1. Executive Summary\n\nOn September 11, 2026, a change to one of our network security policies was deployed with a configuration error. For approximately 6 minutes, this caused login requests to be incorrectly blocked, preventing some users from logging in.\n\n‌\n\nThe issue was detected automatically by our monitoring systems. The problematic change was fully reverted within 5 minutes of detection, restoring normal login functionality.\n\n# 2. Impact\n\n* For approximately 6 minutes \\(12:30–12:36 PM CT on September 11, 2026\\), login requests matching certain URL paths were incorrectly blocked.\n* Any user attempting to log in during this window could have been affected\n* No other functionality was affected. Users already logged in prior to the window were not impacted.\n\n# 3. Root Cause\n\nAs part of a planned security enhancement, our team implemented a new network security policy intended to block a small number of specific, exact URL paths. During implementation, the rule was configured with an erroneous matching condition instead of the intended exact-match condition.\n\n‌\n\nAs a result, the policy blocked any request whose path began with those values, rather than only the exact paths intended ,  which included legitimate login requests that happened to share that prefix. This caused those login attempts to be rejected during the affected window.\n\n# 4. Resolution\n\n* The problematic policy change was identified and fully reverted within 5 minutes of the first alert.\n* Normal login functionality was confirmed restored immediately following the revert.\n\n# 5. Risk of Recurrence & Preventive Actions‌\n\n| **Corrective / Preventive Action** |\n| --- |\n| Enhanced our QA validation step in the process for this class of security policy change, so the deployed configuration is checked against its intended specification before go-live. |\n| Enhanced automated test coverage that specifically validates exact-match versus prefix-match behavior for path-based rules, as an additional safeguard on top of the review process. |",
        "createdAt": "2026-09-29T00:11:07.233+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}