{
  "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, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-07-24T10:17:17.509Z"
  },
  "data": {
    "id": "incident_statuspage_harness_2m37x9nv7prs",
    "slug": "harness-code-services-are-degraded-git-clone-is-failing-2026-07-15",
    "title": "Code services are degraded, git clone is failing",
    "summary": "Code services are degraded, git clone is failing",
    "status": "resolved",
    "severity": "minor",
    "startedAt": "2026-07-16T06:40:19+00:00",
    "updatedAt": "2026-07-22T17:13:19.239+00:00",
    "resolvedAt": "2026-07-16T07:01:23.936+00:00",
    "provider": {
      "slug": "harness",
      "name": "Harness"
    },
    "affectedServices": [],
    "links": {
      "html": "/incidents/harness-code-services-are-degraded-git-clone-is-failing-2026-07-15",
      "api": "/api/v1/incidents/harness-code-services-are-degraded-git-clone-is-failing-2026-07-15",
      "providerHtml": "/providers/harness"
    },
    "impactSummary": "Harness reported a minor event for the affected tracked services.",
    "source": {
      "id": "source_harness_status",
      "kind": "official_status_page",
      "name": "Harness Status",
      "checkedAt": "2026-07-23T12:00:00Z",
      "officialUrl": "https://status.harness.io",
      "statusPageUrl": "https://status.harness.io"
    },
    "updates": [
      {
        "id": "update_statuspage_harness_2m37x9nv7prs_ctqr3t976kfl",
        "status": "investigating",
        "body": "We are currently investigating this issue.",
        "createdAt": "2026-07-16T06:59:19.671+00:00"
      },
      {
        "id": "update_statuspage_harness_2m37x9nv7prs_1kkjdfdjgk5t",
        "status": "resolved",
        "body": "This incident has been resolved.",
        "createdAt": "2026-07-16T07:01:23.936+00:00"
      },
      {
        "id": "update_statuspage_harness_2m37x9nv7prs_c0pgrw3sst24",
        "status": "resolved",
        "body": "# Summary\n\nBetween June 19 and July 17, 2026, the built-in Git Clone step — and any pipeline step using the drone-git clone plugin — failed on ARM64 Kubernetes build infrastructure with the error exec /usr/local/bin/clone: exec format error. AMD64 \\(Intel/AMD\\) builds, Windows builds, and the VM containerless binary path were not affected.\n\nThe root cause was a defect in our internal image publishing process that caused ARM64-tagged drone-git images to actually contain AMD64 binaries. We identified and mitigated the issue the same day it was reported by reverting the drone-git image to the last known-good version. No customer action or configuration change was required.\n\n# Root Cause\n\nOn June 19, 2026, a security remediation restructured how the drone-git image is built. AMD64 builds were updated correctly, but the ARM64 build pipeline didn't build ARM64 files directly — it adapted the AMD64 build file via text substitution and compiled it on ARM64 infrastructure. The June 19 change altered the AMD64 file so that substitution silently no-op'd instead of failing, so the pipeline published an image tagged ARM64 whose Git Clone and Git LFS binaries were still compiled for AMD64. \n\n# Impact\n\n* Affected: The built-in Git Clone step, and any pipeline step using the drone-git clone plugin, running on ARM64 Kubernetes build infrastructure, across all accounts, between July 6 and July 17, 2026.\n* Symptom: Builds failed at the Git Clone step with exec /usr/local/bin/clone: exec format error.\n* Not affected: AMD64 \\(Intel/AMD\\) Kubernetes and VM builds, Windows builds, the VM containerless execution path, and our hardened image variant.\n\n# Mitigation\n\nWe reverted the drone-git image version used across all affected services to the last known-good release. This fully resolved the ARM64 execution failures; no customer configuration changes were required.\n\n# Next Steps\n\nTo prevent such issues from happening again.\n\n* Rebuild the ARM64 image publishing pipeline to build our dedicated ARM64 build files directly, rather than adapting the AMD64 build files.\n* Enhance automated post-publish validation to every image release: verify binary architecture matches the image tag, and run a functional smoke test before an image is considered releasable.\n* Expand automated test coverage to include ARM64 Kubernetes build scenarios.\n* Remove the affected intermediate image versions from circulation once the corrected release is validated.",
        "createdAt": "2026-07-22T16:52:20.157+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}