Major incident

Harness: All modules are running slow in Prod1/2/3/4 due to cloud provider incident

Affected: Platform, Platform, Platform, Platform

Current status of Harness: Operational — live Harness status

Timeline

1. Aug 20, 2026, 15:37 UTC
   investigating
   We are currently investigating this issue.
2. Aug 20, 2026, 16:05 UTC
   investigating
   The slowness could cause either of below symptoms: - Pipelines not starting - Delays in execution - Pipelines being cancelled due to timeouts
3. Aug 20, 2026, 16:22 UTC
   investigating
   Our cloud provider is facing an active incident and we are following up.
4. Aug 20, 2026, 16:32 UTC
   investigating
   We are continuing to investigate this issue.
5. Aug 20, 2026, 16:50 UTC
   identified
   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 information becomes available.
6. Aug 20, 2026, 17:17 UTC
   monitoring
   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 investigating
7. Aug 20, 2026, 19:23 UTC
   resolved
   This incident has been resolved.
8. Aug 26, 2026, 04:57 UTC
   postmortem
   # 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 Delivery, Continuous Integration, pipeline orchestration, and Feature Management & Experimentation were all affected. Google Cloud Platform experienced a multi-product incident in the us-west1 region affecting Bigtable, Compute Engine, Google Kubernetes Engine, and persistent-disk I/O. Harness production infrastructure runs on persistent disks in that region. The degradation raised database operation latency from approximately 2 ms to over 10 ms at the 95th percentile, which in turn caused message-queue processing lag and propagated to every service that depends on timely database access. ‌ # Impact This was a degradation, not an outage. Pipelines continued to execute and complete successfully throughout; they were slow rather than failing. No data was lost, and no customer work was dropped as a result of this incident. # **Root cause** Harness production infrastructure in the affected environments runs on Google Cloud Platform persistent disks in the us-west1 region. When that storage layer degraded, the effect propagated through the platform in a predictable chain: **Persistent-disk I/O degradation in us-west1.** Google Cloud Platform experienced a multi-product incident affecting Bigtable, Compute Engine, Google Kubernetes Engine, and persistent-disk performance. This was an infrastructure failure in the provider’s environment, outside Harness’s control. # **Preventive actions** Although Harness cannot prevent a cloud provider infrastructure failure. The actions below are aimed at detecting one faster and being better positioned to act on it. | **Action** | | --- | | Continue routine pre-testing of targeted cross-region database failovers, as performed during this incident, to keep failover readiness verified rather than assumed | | Assess full-stack multi-region failover readiness for future scenarios in which cross-region latency would be unacceptable |

Updates as published by Harness (original).