Harness

Affected: Continuous Delivery - Next Generation (CDNG), Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Security Testing Orchestration (STO), Infrastructure as Code Management (IaCM), Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-19 07:46 UTC

   We are currently investigating this issue.

2. monitoring 2026-10-19 08:02 UTC

   A fix has been implemented and we are monitoring the results.

3. identified 2026-10-19 08:02 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-10-19 08:04 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-10-19 08:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery - Next Generation (CDNG)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 10:10 UTC

   We are currently investigating this issue.

2. identified 2026-10-15 10:10 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-10-15 10:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery - Next Generation (CDNG)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 08:04 UTC

   We are currently investigating this issue.

2. identified 2026-10-15 08:05 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-15 08:09 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-15 08:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Infrastructure as Code Management (IaCM)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 01:06 UTC

   We are currently investigating this issue.

2. identified 2026-10-13 01:07 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-13 01:56 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-13 04:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-12 15:25 UTC

   We are currently experiencing HTTP 429 (rate-limiting) errors when Harness Cloud builds access Maven Central, which may impact build execution. Our team is actively working with Sonatype to resolve the issue as quickly as possible. We will provide further updates as we make...

2. resolved 2026-10-12 16:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Infrastructure as Code Management (IaCM)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 21:46 UTC

   We are currently investigating this issue.

2. investigating 2026-10-06 21:47 UTC

   We are continuing to investigate this issue.

3. identified 2026-10-06 22:03 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-10-06 22:30 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring 2026-10-06 22:30 UTC

   A fix has been implemented and we are monitoring the results. we have confirmation of this fixing the issue.

6. resolved 2026-10-06 22:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Harness's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-06 20:00 UTC

   On October 7, 2026, from 08:00 UTC to 11:00 UTC (1:30 PM to 4:30 PM IST), some pipeline executions on the Prod 7 cluster saw intermittent failures in Policy (OPA) step evaluations.

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery - Next Generation (CDNG)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-10-06 12:54 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2026-10-06 15:35 UTC

   This incident has been resolved.

3. postmortem 2026-10-10 01:57 UTC

   ### Summary Customers on Prod 2 experienced intermittent failures of a few Verify steps at startup. Affected steps failed shortly after launch with a message indicating Continuous Verification\(CV\) could not reach an internal Harness service. The issue stemmed from a recent...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Infrastructure as Code Management (IaCM)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-06 11:58 UTC

   We are currently investigating this issue.

2. investigating 2026-10-06 11:59 UTC

   We are continuing to investigate this issue.

3. identified 2026-10-06 12:24 UTC

   The issue has been identified and a fix is being implemented.

4. resolved 2026-10-06 16:21 UTC

   This incident has been resolved.

5. postmortem 2026-10-09 18:48 UTC

   ## Summary On **Tuesday, 6 October 2026**, IaCM pipelines that use the **OpenTofu plugin** in **Prod1** failed intermittently for a production accountAffected runs injected secrets successfully, then later steps timed out or failed authentication. The same pipeline often...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Platform, Platform, Platform, Platform, Platform

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-05 22:01 UTC

   We are currently investigating this issue.

2. identified 2026-10-05 23:50 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-06 00:26 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-10-06 00:26 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-10-06 00:39 UTC

   Verified the fix and resolved SSO issues.

6. postmortem 2026-10-09 16:17 UTC

   ## Okta Application SP-Initiated SSO Login Failures ‌ # Summary ‌ Between October 5, 2026, 18:18 UTC and October 6, 2026, 00:26 UTC, some Harness customers were unable to sign in to the Harness Hosted MCP server via SAML Single Sign-On \(SSO\). The main Harness Portal user...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Platform, Platform

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-29 20:31 UTC

   We are currently investigating this issue.

2. identified 2026-09-29 20:31 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-09-29 20:50 UTC

   We identified an issue that applies only to SP-initiated login through the published Harness Okta application. After a recent update to that application, those login attempts returned an HTTP 400 error when the configured SSO URL was missing from Additional ACS URLs. General...

4. identified 2026-09-29 20:57 UTC

   We identified an issue that applies only to SP-initiated login through the published Harness Okta application. After a recent update to that application, those login attempts returned an HTTP 400 error when the configured SSO URL was missing from Additional ACS URLs. General...

5. resolved 2026-10-02 00:33 UTC

   This incident has been resolved.

6. postmortem 2026-10-07 18:30 UTC

   # 1. Summary Starting September 29, 2026, customers who sign in to Harness through the published Harness application in the Okta Integration Network \(OIN\) were unable to complete SP-initiated SSO login. Affected users received an HTTP 400 error from Okta instead of being...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-29 18:45 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-29 21:49 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-29 22:01 UTC

   This incident has been resolved.

4. postmortem 2026-10-02 22:40 UTC

   ### Summary Between approximately **11:37 AM and 3:01 PM PDT \(18:37–22:01 UTC\) on September 29, 2026**, customers using Harness CI self-hosted Linux cloud runners in **prod1/prod2 \(us-west1\)** experienced intermittent networking failures during pipeline execution — primarily...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery - Next Generation (CDNG)

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-29 14:41 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-29 15:54 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-09-29 15:57 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-09-29 18:49 UTC

   This incident has been resolved.

5. postmortem 2026-10-02 05:37 UTC

   **Summary** Customers on Prod-2 experienced elevated failure rates in Continuous Verification pipelines. Verification jobs failed to complete or reported errors because CV data-collection workers could not communicate with the platform service that coordinates their work. This...

Excerpts are shortened. Read the full incident on Harness's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-28 11:30 UTC

   On 28th September 2026, we observed an issue with copying files from the Harness Filestore during the export step, where the files were being copied as null/empty files. As a result, all pipelines using Filestore APIs were blocked during the incident window. The issue was caused...

2. postmortem 2026-10-01 17:28 UTC

   ### Summary On September 28, 2026, some customers on Prod-2 experienced failures in CD pipeline steps that read File Store content using pipeline expressions \(e.g., ` `\). Affected expressions returned null instead of the expected file content, causing dependent steps to fail...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Platform, Platform, Platform, Platform, Platform, Platform, Platform, Platform, Platform

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 20:17 UTC

   We are currently investigating connectivity issues affecting customers whose environments are protected by Palo Alto Networks firewalls. These firewalls are blocking connections to Harness APIs, which may result in: - Failed pipeline executions - Inability to deploy applications...

2. monitoring 2026-09-24 08:43 UTC

   Mitigation Available: Harness Traffic Blocked by Network Security Policy We have identified an issue where some customers may be unable to access Harness because Harness traffic is being categorized as “AI-Platform” by Palo Alto network security controls and subsequently blocked...

3. resolved 2026-09-25 17:10 UTC

   After consultation with Palo Alto Networks, we can confirm that on Sept 23rd 2026, app.harness.io was categorized as an AI Platform Service by the Palo Alto Networks Team. Palo Alto Networks sent a notice to customers in August about the reclassification. This change may place...

4. postmortem 2026-10-13 04:50 UTC

   .

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-22 16:40 UTC

   We are currently investigating this issue.

2. identified 2026-09-22 17:14 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-22 18:01 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-22 18:38 UTC

   This incident has been resolved.

5. postmortem 2026-10-02 22:05 UTC

   # Summary On September 22, 2026, three of our outbound network gateways in one region became unhealthy and began rejecting a small percentage of new outbound connection attempts. The issue was resolved the same day problem completely with no further recurrence or follow-on...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Custom Dashboards, Custom Dashboards

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-22 14:00 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-09-22 14:08 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-22 14:20 UTC

   This incident has been resolved.

4. postmortem 2026-10-02 22:10 UTC

   Same as the previous root cause.

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Custom Dashboards

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-21 16:39 UTC

   We are currently investigating this issue.

2. identified 2026-09-21 17:12 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-21 18:27 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-21 18:33 UTC

   This incident has been resolved.

5. postmortem 2026-09-29 22:39 UTC

   ## Summary On Sep 21, 2026, customers in Prod 2 experienced degraded and then largely unavailable deployment dashboards for approximately three hours. The issue was caused by a set of analytics queries behind those dashboards reading far more data than they needed, which...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Infrastructure as Code Management (IaCM)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-18 14:30 UTC

   We are currently investigating this issue.

2. investigating 2026-09-18 16:03 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-18 17:40 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-09-18 19:04 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring 2026-09-19 04:57 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-09-19 04:57 UTC

   This incident has been resolved.

7. postmortem 2026-10-02 22:08 UTC

   This was a customer specific issue.

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Custom Dashboards, Custom Dashboards

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-18 05:03 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-21 08:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-21 09:17 UTC

   This incident has been resolved.

4. postmortem 2026-09-29 22:27 UTC

   # 1. Summary Starting on September 19, 2026, some customers began experiencing failures when downloading or exporting dashboards to CSV through our API, which returned an HTTP 500 \(internal server error\). Standard dashboard viewing, API authentication, and downloads initiated...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: DBDevOps, DBDevOps

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-17 14:00 UTC

   We are currently investigating this issue.

2. investigating 2026-09-17 16:58 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-17 17:13 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-09-17 20:05 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring 2026-09-17 20:11 UTC

   A fix has been implemented and we are monitoring the results.

6. resolved 2026-09-18 21:30 UTC

   This incident has been resolved.

7. postmortem 2026-09-22 19:32 UTC

   ## Summary Between approximately **8:40 AM and 1:00 PM PDT on Wednesday, September 17, 2026**, some customers running **Database DevOps** pipelines in Production experienced intermittent failures when executing schema migration steps \(for example Apply Schema and related...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Infrastructure as Code Management (IaCM), Infrastructure as Code Management (IaCM)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-16 04:13 UTC

   We are currently investigating this issue.

2. identified 2026-09-16 06:59 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-16 06:59 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-09-16 07:00 UTC

   Fix has been implemented in Prod Eu 1 and we are monitoring for any further issues.

5. monitoring 2026-09-16 12:53 UTC

   Fix has been implemented in Prod 1 and we are monitoring for any further issues.

6. resolved 2026-09-16 16:45 UTC

   This incident has been resolved.

7. postmortem 2026-09-21 22:59 UTC

   # Root Cause Analysis Report ## IaCM Module Registry Timeouts ## 1. Summary On Monday, September 15, 2026, some customers using Infrastructure as Code Management \(IaCM\) Module Registry on Prod EU1, and later Prod1, experienced timeouts and failed requests. ‌ Affected customers...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Platform, Platform, Platform, Platform

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-15 17:22 UTC

   We are currently investigating this issue.

2. identified 2026-09-15 17:35 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-15 17:43 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-15 17:43 UTC

   This incident has been resolved.

5. postmortem 2026-09-29 00:11 UTC

   # Root Cause Analysis Report ## Brief API Login Failures Due to a Security Policy Misconfiguration ## 1. Executive Summary On September 11, 2026, a change to one of our network security policies was deployed with a configuration error. For approximately 6 minutes, this caused...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Infrastructure as Code Management (IaCM)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-15 12:05 UTC

   We are currently investigating this issue.

2. identified 2026-09-15 13:19 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-15 13:22 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-09-15 13:32 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-09-15 14:58 UTC

   This incident has been resolved.

6. postmortem 2026-09-22 21:04 UTC

   ## 1. Summary On Monday, September 15, 2026, some customers using Infrastructure as Code Management \(IaCM\) Module Registry on Prod EU1, and later Prod1, experienced timeouts and failed requests. ‌ Affected customers saw Module Registry operations hang or fail in the UI, and...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery - Next Generation (CDNG), Continuous Delivery - Next Generation (CDNG), Continuous Delivery - Next Generation (CDNG)

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-14 19:00 UTC

   We are currently investigating this issue.

2. identified 2026-09-15 00:42 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-09-15 00:45 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2026-09-15 01:46 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-09-15 03:28 UTC

   This incident has been resolved.

6. postmortem 2026-09-21 18:26 UTC

   # **Summary** To 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 certificate passed Harness's existing pre-deployment...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery (CD) - FirstGen - EOS, Continuous Delivery (CD) - FirstGen - EOS, Continuous Delivery - Next Generation (CDNG), Continuous Delivery - Next Generation (CDNG), Cloud Cost Management (CCM), Cloud Cost Management (CCM), Continuous Error Tracking (CET), Continuous Error Tracking (CET), Chaos Engineering, Chaos Engineering, Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Custom Dashboards, Feature Flags (FF), Feature Flags (FF), Security Testing Orchestration (STO), Service Reliability Management (SRM), Internal Developer Portal (IDP), Infrastructure as Code Management (IaCM), Software Supply Chain Assurance (SSCA), Software Engineering Insights (SEI) / AI DLC Insights, Code Repository, Artifact Registry, Platform, AI Test Automation, FME, FME

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-08 21:52 UTC

   We are currently investigating this issue.

2. investigating 2026-09-08 22:53 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-08 22:53 UTC

   We are continuing to investigate the issue.

4. investigating 2026-09-08 23:31 UTC

   We are continuing to investigate this issue.

5. identified 2026-09-08 23:52 UTC

   The issue has been identified and a fix is being implemented.

6. identified 2026-09-09 00:29 UTC

   We are continuing to work on a fix for this issue.

7. monitoring 2026-09-09 00:36 UTC

   A fix has been implemented and we are monitoring the results.

8. monitoring 2026-09-09 00:39 UTC

   A fix has been implemented and we are monitoring the results.

9. resolved 2026-09-09 04:30 UTC

   This incident has been resolved.

10. postmortem 2026-09-09 23:23 UTC

    ### Summary On September 8, 2026, customers in Prod 1 and Prod 2 experienced elevated platform latency and pipeline failures. The issue was caused by a regression in a newly released capability that triggered cascading failures under high load. Because the capability was behind...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Platform

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-05 09:40 UTC

   We are currently investigating this issue.

2. resolved 2026-09-05 09:40 UTC

   This incident has been resolved.

3. postmortem 2026-09-09 18:22 UTC

   ## **Summary** Between 12:34am PST and 12:38am PST on 5th September, the Delegate service manager experienced some elevated exceptions when attempting to write to the database. Consequently, delegate connections were dropped, causing them to disconnect. Delegate automatically...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery - Next Generation (CDNG)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 10:00 UTC

   Pipeline execution is stuck in Prod1. We are investigating the issue.

2. monitoring 2026-09-03 10:28 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-03 11:40 UTC

   This incident has been resolved.

4. postmortem 2026-09-10 07:21 UTC

   # Summary On September 3, 2026, between approximately 2:54 AM and 3:44 AM PDT, customers running pipelines on Prod1 experienced delays in pipeline execution graph rendering and execution status updates. Pipeline execution itself was not affected — pipelines continued to run and...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Platform

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-28 07:04 UTC

   We are currently investigating this issue.

2. identified 2026-08-28 07:16 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-28 07:29 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-28 07:35 UTC

   This incident has been resolved.

5. postmortem 2026-09-02 22:15 UTC

   ## Summary Between August 27 and August 28, 2026, customers experienced an issue where some pipelines, deployments, and related resources appeared as not found in the Harness UI and API, even though the underlying data remained intact. ‌ The issue occurred during a planned...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Infrastructure as Code Management (IaCM), Infrastructure as Code Management (IaCM), Infrastructure as Code Management (IaCM), Infrastructure as Code Management (IaCM)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-26 08:38 UTC

   We are currently investigating an issue reported in IACM pipelines in Prod-1 , Prod-2 ,Prod-4 and EU1 harness clusters.

2. investigating 2026-08-26 08:43 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-08-26 09:05 UTC

   We have reverted the change that caused this issue in all clusters.

4. resolved 2026-08-26 09:10 UTC

   This incident has been resolved.

5. postmortem 2026-09-21 18:07 UTC

   # Root Cause Analysis Report # 1. Summary On Wednesday, August 26, 2026, some customers running Infrastructure as Code Management \(IaCM\) pipelines in Harness production saw those pipelines start, sit in a Running state with no init or plan steps, then abort or expire after...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: FME

Failure mode: CDN or edge layer failed or served bad content. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-24 00:57 UTC

   We are currently investigating this issue.

2. investigating 2026-08-24 01:01 UTC

   We are currently investigating reports that the Feature Management & Experimentation (FME) user interface is failing to load. Customers attempting to access the FME console may encounter errors or unresponsive pages. Feature flag evaluation and SDK traffic are not believed to be...

3. monitoring 2026-08-24 01:08 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-24 01:12 UTC

   This incident has been resolved.

5. postmortem 2026-08-27 23:36 UTC

   ## Summary * Starting at **23:42 UTC** on August 23, 2026, several FME customers reported failures loading the FME UI. * FME UI Artifacts served from the CDN expired due to a retention policy, causing FME UI to fail to load. * Any flag request changes through the API, change...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Platform, Platform, Platform, Platform

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region..

1. investigating 2026-08-20 15:37 UTC

   We are currently investigating this issue.

2. investigating 2026-08-20 16:05 UTC

   The slowness could cause either of below symptoms: - Pipelines not starting - Delays in execution - Pipelines being cancelled due to timeouts

3. investigating 2026-08-20 16:22 UTC

   Our cloud provider is facing an active incident and we are following up.

4. investigating 2026-08-20 16:32 UTC

   We are continuing to investigate this issue.

5. identified 2026-08-20 16:50 UTC

   Our cloud provider has confirmed an ongoing incident impacting multiple regions. Harness pipelines have not experienced failures as a result, though some users may continue to experience slowness. We are monitoring the situation closely and will provide updates as more...

6. monitoring 2026-08-20 17:17 UTC

   We are observing improved latencies across the board following the fix implemented by our cloud provider. We are continuing to monitor the situation closely and will provide further updates as warranted. We noted some stuck executions for CI for couple of customers, which we are...

7. resolved 2026-08-20 19:23 UTC

   This incident has been resolved.

8. postmortem 2026-08-26 04:57 UTC

   # Summary On 20 August 2026, beginning at approximately 15:00 UTC, the Harness platform experienced widespread performance degradation across all production environments. Pipeline executions that normally complete in around two minutes took seven to ten minutes. Continuous...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: FME

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-20 14:32 UTC

   We are currently investigating this issue.

2. identified 2026-08-20 14:47 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-20 14:56 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-20 15:02 UTC

   This incident has been resolved.

5. postmortem 2026-08-23 21:45 UTC

   ### Summary On August 20, 2026, between 10:24 and 14:55 UTC, a subset of FME writes failed. Writes made from the FME UI and writes made with Harness access tokens \(PATs and SATs\) were not affected. Runtime flag evaluation continued to work normally. The issue was mitigated by...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: US - app.traceable.ai / api.traceable.ai

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-19 13:22 UTC

   We are currently investigating this issue.

2. investigating 2026-08-19 14:03 UTC

   We are continuing to investigate this issue.

3. investigating 2026-08-19 14:55 UTC

   We are continuing to investigate this issue.

4. identified 2026-08-19 15:13 UTC

   The issue has been identified and a fix is being implemented.

5. monitoring 2026-08-19 15:22 UTC

   A fix has been implemented and we are monitoring the results.

6. monitoring 2026-08-19 15:33 UTC

   We are continuing to monitor for any further issues.

7. resolved 2026-08-19 16:07 UTC

   This incident has been resolved.

8. postmortem 2026-08-26 17:20 UTC

   **Summary** On 19 August 2026 between 12:35 and 17:29 UTC, the Harness Application Security service experienced a significant disruption affecting both the customer-facing console and the data ingestion pipeline in the SaaS Production and US1 regions. ‌ **Root Cause** The...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Software Engineering Insights (SEI) / AI DLC Insights, Software Engineering Insights (SEI) /AI DLC Insights, Software Engineering Insights (SEI) / AI DLC Insights, Software Engineering Insights (SEI) / AI DLC Insights, Software Engineering Insights (SEI) /AI DLC Insights

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-06 14:30 UTC

   We are currently investigating a Harness component that is experiencing issues. We are working to identify the cause and restore normal operations as soon as possible.

2. investigating 2026-08-06 14:32 UTC

   We are continuing to investigate this issue.

3. identified 2026-08-06 15:46 UTC

   The issue has been identified and a fix is being implemented.

4. resolved 2026-08-06 16:01 UTC

   This incident has been resolved.

5. postmortem 2026-08-10 18:24 UTC

   ## Summary Customers on Prod1, Prod2, and Prod3 \(US\) clusters experienced failures when loading SEI 2.0 dashboards on August 6, 2026, from 7:22 AM PDT to 9:03 AM PDT. Customers calling the SEI 2.0 API also experienced similar failures. No customer data was lost, and ingestion...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery - Next Generation (CDNG)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-08-06 13:50 UTC

   We are monitoring the stuck pipelines in prod2. The new executions are passing as we are continuously monitoring the services.

2. monitoring 2026-08-06 16:58 UTC

   We are monitoring the stuck pipelines in prod2. For the customers who are still seeing stuck pipelines, we request you to abort and re-trigger.

3. resolved 2026-08-06 18:21 UTC

   This incident has been resolved.

4. postmortem 2026-08-17 18:40 UTC

   ## **Summary** On August 6, 2026 \(morning PDT\), some customers running pipelines in the Prod2 production environment observed pipeline executions that stopped making progress — stages that did not advance and produced no further output or status updates. The issue was reported...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Infrastructure as Code Management (IaCM), Infrastructure as Code Management (IaCM), Infrastructure as Code Management (IaCM), Infrastructure as Code Management (IaCM)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-04 12:07 UTC

   We are currently investigating this issue.

2. investigating 2026-08-04 12:08 UTC

   We are continuing to investigate this issue.

3. investigating 2026-08-04 12:17 UTC

   We are continuing to investigate this issue.

4. investigating 2026-08-04 13:00 UTC

   We have identified the issue and started to implement the fix , prod2 is restored.

5. investigating 2026-08-04 13:09 UTC

   We are continuously rolling out fixes to all Clusters, Prod EU1 has been resolved.

6. investigating 2026-08-04 13:16 UTC

   We are continuously rolling out fixes to all Clusters, Prod3 has been resolved.

7. resolved 2026-08-04 15:28 UTC

   This incident has been resolved.

8. postmortem 2026-08-06 17:02 UTC

   # Executive Summary On August 4, 2026, between approximately 3:36 PM and 9:00 PM IST, customers using Infrastructure as Code Management \(IaCM\) on Prod0 and Prod1 were unable to access the Variable Sets settings page. The page rendered blank with no error message, and customers...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-31 20:22 UTC

   We are currently investigating this issue.

2. identified 2026-08-01 02:41 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-01 05:45 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-01 09:11 UTC

   This incident has been resolved.

5. postmortem 2026-08-21 04:19 UTC

   # **Summary** Between 25 July and 4 August 2026, pipeline execution dashboards and overview pages in the Harness Prod 2 and Prod 3 clusters displayed data that was between behind real time. Pipelines themselves continued to build, deploy, and execute normally throughout; the...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Artifact Registry

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-31 13:48 UTC

   We are currently investigating this issue.

2. identified 2026-08-01 02:34 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-01 02:44 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-01 23:49 UTC

   This incident has been resolved.

5. postmortem 2026-08-13 00:50 UTC

   # **Summary** On July 31, 2026, artifact uploads performed through pipeline in the EU1 cluster began failing with an authentication error. Uploads initiated manually \(outside of a pipeline\) were not affected, and the ability to retrieve existing artifacts \(downloads\) was...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-30 05:59 UTC

   Summary - We are intermittently facing network connectivity issues with our Build VM's unable to connect to external resources. We are currently investigating the issue.

2. monitoring 2026-07-30 08:07 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-07-30 08:07 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-07-31 03:22 UTC

   This incident has been resolved.

5. postmortem 2026-08-07 19:32 UTC

   ## Summary CI runners in the us-west1 and us-central1 regions intermittently experienced connection timeouts of approximately 134 seconds when reaching external services such as GitHub and Bitbucket over outbound network gateways. ## Impact * CI runners in the affected regions...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery (CD) - FirstGen - EOS, Continuous Delivery (CD) - FirstGen - EOS, Continuous Delivery - Next Generation (CDNG), Continuous Delivery - Next Generation (CDNG), Cloud Cost Management (CCM), Cloud Cost Management (CCM), Continuous Error Tracking (CET), Continuous Error Tracking (CET), Chaos Engineering, Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Custom Dashboards, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Feature Flags (FF), Custom Dashboards, Feature Flags (FF), Security Testing Orchestration (STO), Security Testing Orchestration (STO), Service Reliability Management (SRM), Service Reliability Management (SRM), Chaos Engineering, Internal Developer Portal (IDP), Internal Developer Portal (IDP), Infrastructure as Code Management (IaCM), Infrastructure as Code Management (IaCM), Software Supply Chain Assurance (SSCA), Software Supply Chain Assurance (SSCA), Software Engineering Insights (SEI) /AI DLC Insights, Software Engineering Insights (SEI) / AI DLC Insights, Code Repository, Code Repository, Artifact Registry, Artifact Registry, Platform, Platform, AI Test Automation, FME, Release Management

Failure mode: A configuration change caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-27 06:42 UTC

   We are currently investigating this issue.

2. identified 2026-07-27 06:45 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-27 06:49 UTC

   A fix has been implemented and we are monitoring the results.

4. investigating 2026-07-27 07:52 UTC

   We are currently investigating this issue.

5. investigating 2026-07-27 08:13 UTC

   We are continuing to investigate this issue.

6. identified 2026-07-27 09:04 UTC

   The issue has been identified and a fix is being implemented.

7. identified 2026-07-27 09:05 UTC

   We are continuing to work on a fix for this issue.

8. monitoring 2026-07-27 09:07 UTC

   A fix has been implemented and we are monitoring the results.

9. monitoring 2026-07-27 09:07 UTC

   We are continuing to monitor for any further issues.

10. monitoring 2026-07-27 09:09 UTC

    We are continuing to monitor for any further issues.

11. resolved 2026-07-27 13:33 UTC

    This incident has been resolved.

12. postmortem 2026-08-07 18:15 UTC

    # Summary During a recent production deployment, a defect in our internal deployment tooling caused two critical services to run with incorrect, non-production configuration values in our production environment This led to a related set of four distinct symptoms: incorrect...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Software Engineering Insights (SEI) /AI DLC Insights, Software Engineering Insights (SEI) / AI DLC Insights, Software Engineering Insights (SEI) / AI DLC Insights

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-22 14:55 UTC

   We are investigating an issue impacting AIDI dashboards. Users may experience increased load times or intermittent failures when accessing dashboards. Our team is actively working to identify the root cause and restore normal performance. We will provide updates as more...

2. identified 2026-07-22 14:58 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-22 15:25 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-22 23:16 UTC

   This incident has been resolved.

5. postmortem 2026-08-10 18:17 UTC

   ## Summary Customers on Prod1, Prod2, and Prod3 clusters experienced intermittent widget load failures and increased load times when accessing AIDI 2.0 dashboards on July 22, 2026. Not all widgets were affected simultaneously the issue manifested as sporadic failures rather than...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-17 17:16 UTC

   We are currently investigating this issue.

2. identified 2026-07-17 17:34 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-17 18:12 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-17 21:56 UTC

   This incident has been resolved.

5. postmortem 2026-08-04 02:48 UTC

   # Summary On 17 July 2026, following a routine code deployment, customers on older delegate versions \(858xx and below\) began experiencing delayed CI builds on Harness Cloud-hosted builds using our global build-queueing capability. Affected builds experienced an unexpected...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Integration Enterprise(CIE) - Self Hosted Runners

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-17 10:30 UTC

   We are currently investigating this issue.

2. identified 2026-07-17 13:12 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-17 13:19 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-07-17 13:19 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-07-17 14:16 UTC

   This incident has been resolved.

6. postmortem 2026-07-22 17:25 UTC

   # Summary Between 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...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Code Repository

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-16 06:40 UTC

   We are currently investigating this issue.

2. resolved 2026-07-16 07:01 UTC

   This incident has been resolved.

3. postmortem 2026-07-22 16:52 UTC

   # Summary Between 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...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Feature Flags (FF), Feature Flags (FF)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-14 11:25 UTC

   Certain users are unable to see feature flags in prod1 and prod2

2. monitoring 2026-07-14 11:56 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-14 11:57 UTC

   This incident has been resolved.

4. postmortem 2026-07-23 22:32 UTC

   ## Summary On July 14, 2026, certain Harness Feature Flag \(FF\) Classic customers on the Prod1 and Prod2 production environments were unable to view Feature Flags in the Harness platform. Affected requests returned an authorization error \(HTTP 403\), so Feature Flags were not...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery (CD) - FirstGen - EOS, Continuous Integration Enterprise(CIE) - Linux Cloud Builds

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-09 20:21 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-09 21:10 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-07-09 21:46 UTC

   This incident has been resolved.

4. postmortem 2026-07-21 05:21 UTC

   # Summary On July 9, 2026, some customers in the Harness Prod3 cluster experienced pipeline failures over a ~2.5-hour window, despite making no changes in their pipelines. Shell Script steps failed when fetching scripts from the Harness File Store, and Kubernetes deployment...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery - Next Generation (CDNG)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-08 07:49 UTC

   We are currently investigating an issue in Prod3 cluster where Harness platform components are loading slower than expected.

2. monitoring 2026-07-08 08:22 UTC

   A fix has been implemented and we are monitoring the results.

3. investigating 2026-07-08 14:40 UTC

   We are currently investigating this issue.

4. monitoring 2026-07-08 16:51 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-07-08 18:56 UTC

   This incident has been resolved.

6. postmortem 2026-07-14 00:14 UTC

   ## Summary Between July 7 and July 8, 2026, customer accounts hosted in our Prod 3 environment experienced intermittent slowness and failures when loading pipelines and resolving templates. The underlying cause was a sharp, sustained increase in internal feature-flag lookup...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: Continuous Delivery - Next Generation (CDNG)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-07 10:22 UTC

   We are currently investigating an issue in Prod3 cluster where pipeline components are loading slower than expected.

2. monitoring 2026-07-07 11:50 UTC

   A fix has been implemented in one of our microservice responsible for dealing with pipeline templates which has resolved the issue. We are continuing to monitor the issue.

3. resolved 2026-07-07 12:36 UTC

   This incident has been resolved.

4. postmortem 2026-07-14 00:04 UTC

   ## Summary Between July 7 and July 8, 2026, customer accounts hosted in our Prod 3 environment experienced intermittent slowness and failures when loading pipelines and resolving templates. The underlying cause was a sharp, sustained increase in internal feature-flag lookup...

Excerpts are shortened. Read the full incident on Harness's status page.

Affected: FME, FME, FME

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-07-02 15:48 UTC

   A fix has been implemented and we are monitoring the results.

2. monitoring 2026-07-02 20:10 UTC

   We are seeing the backlogged items worked through and continuing to monitor results.

3. monitoring 2026-07-02 23:31 UTC

   We are continuing to monitor results while the backlog is worked through.

4. resolved 2026-07-03 16:11 UTC

   This incident has been resolved.

5. postmortem 2026-07-09 19:24 UTC

   **Incident Summary** Harness FME \(Feature Management & Experimentation\) faced substantial delays in scheduled impressions data exports on Jul 2, 2026. This issue stemmed from performance degradation within Tinybird's infrastructure, affecting query execution crucial to our...

Excerpts are shortened. Read the full incident on Harness's status page.