{
  "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-03T19:31:32.017Z"
  },
  "data": {
    "id": "incident_statuspage_harness_krb186nq1nwq",
    "slug": "harness-mtls-outage-with-delegates-2026-09-14",
    "title": "MTLS Outage with Delegates",
    "summary": "MTLS Outage with Delegates",
    "status": "resolved",
    "stale": false,
    "severity": "critical",
    "startedAt": "2026-09-14T19:00:28+00:00",
    "updatedAt": "2026-09-21T22:58:06.29+00:00",
    "resolvedAt": "2026-09-15T03:28:11.132+00:00",
    "provider": {
      "slug": "harness",
      "name": "Harness"
    },
    "affectedServices": [
      {
        "slug": "harness-cicd",
        "name": "CI/CD"
      }
    ],
    "links": {
      "html": "/incidents/harness-mtls-outage-with-delegates-2026-09-14",
      "api": "/api/v1/incidents/harness-mtls-outage-with-delegates-2026-09-14",
      "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-03T19:30:12.218+00:00",
      "stale": false,
      "officialUrl": "https://status.harness.io",
      "statusPageUrl": "https://status.harness.io"
    },
    "updates": [
      {
        "id": "update_statuspage_harness_krb186nq1nwq_3gpczynzrlpf",
        "status": "investigating",
        "body": "We are currently investigating this issue.",
        "createdAt": "2026-09-14T22:48:28.989+00:00"
      },
      {
        "id": "update_statuspage_harness_krb186nq1nwq_1dbllv62f4xy",
        "status": "identified",
        "body": "The issue has been identified and a fix is being implemented.",
        "createdAt": "2026-09-15T00:42:49.982+00:00"
      },
      {
        "id": "update_statuspage_harness_krb186nq1nwq_3bfjdyz8j2r5",
        "status": "identified",
        "body": "We are continuing to work on a fix for this issue.",
        "createdAt": "2026-09-15T00:45:38.316+00:00"
      },
      {
        "id": "update_statuspage_harness_krb186nq1nwq_51g1xvg48ptr",
        "status": "monitoring",
        "body": "A fix has been implemented and we are monitoring the results.",
        "createdAt": "2026-09-15T01:46:10.815+00:00"
      },
      {
        "id": "update_statuspage_harness_krb186nq1nwq_05ctn6bwtxw9",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2026-09-15T03:28:11.132+00:00"
      },
      {
        "id": "update_statuspage_harness_krb186nq1nwq_wnym550w864d",
        "status": "resolved",
        "body": "# **Summary**\n\nTo improve the security posture, On September 14, 2026, Harness performed a scheduled rotation of the TLS certificate used to secure Delegate connections for accounts using mutual TLS \\(mTLS\\),The replacement  \ncertificate passed Harness's existing pre-deployment validation and smoke testing. However, the rotation also  \nintroduced a change in certificate authority, which required additional certificate-chain and gateway  \nconfiguration this prevented affected Delegates from connecting to Harness.  \nHarness has identified the contributing factors and is implementing the corrective actions described below to prevent a recurrence.  \n\n# **Impact**\n\n  \nDelegates configured to use mutual TLS in Prod environment were unable to connect to Harness for  \nuntil Harness applied a temporary mitigation \\(disabling mTLS\\) that restored  \nconnectivity while the underlying issue was corrected.\n\nThis affected the ability to run pipelines and other operations dependent on the affected Delegates. Full,  \npermanent connectivity — with mTLS restored to its normal, fully secure configuration — was confirmed for  \nboth environments by 7:20 PM PST.  \n\n# **Root Cause**\n\n‌\n\n  \nAs part of routine certificate maintenance, Harness rotated the certificate used by the gateway component that  \nsecures mutual TLS connections for Delegates in prod environments.  The rotation also introduced a  \nchange in certificate authority, which required additional certificate-chain and gateway configuration that was  \nnot fully covered by the existing validation process. As a result, the gateway was unable to load the new  \ncertificate correctly, and Delegates relying on mutual TLS could not establish a secure connection.  \n\n# **Remediation**\n\n  \nOnce the certificate rotation was confirmed as the source of the issue, Harness engineering worked continuously  \nto correct the certificate and validate the fix with Citi before fully restoring the secure configuration.  \nCorrective and Preventive Actions\n\nDuring remediation, Harness also identified and corrected a secondary issue with the replacement certificate's  \nchain, which required an additional deployment before connectivity was fully and permanently restored.  \n\n# **Next Steps**\n\n  \nHarness is taking the following steps to prevent a recurrence of this issue:\n\n1. Extend pre-deployment validation and smoke testing to explicitly cover certificate authority changes and full  \n  certificate-chain verification, closing the specific gap that allowed this configuration through.\n2. Enhance automation  for managing mTLS-related configuration changes,\n3. Improve monitoring and alerting for Delegate connectivity, including account-level visibility, so similar issues  \n  are detected automatically",
        "createdAt": "2026-09-21T18:26:26.305+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}