Outage report · Partial outage

Harness outage on Jul 27, 2026

The Prod3 & Prod1 environment is experiencing intermittent outages. We are currently investigating the issue.

SeverityPartial outage

StartedJul 27, 2026, 06:42UTC

ResolvedJul 27, 2026, 13:33UTC

Duration6h 51m

What happened

Harness reported a partial outage starting Jul 27, 2026, 06:42 UTC, affecting 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) and 35 more. It was marked resolved at Jul 27, 2026, 13:33 UTC.

The incident lasted 6h 51m from first report to resolution.
It was the 2nd longest of 3 significant outages Harness reported in the 12 months up to it.
Harness had reported no other partial or major outages in the 90 days before it.
11 other vendors we track reported a significant incident within 12 hours of it.

Latest update from Harness

# 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 configuration behavior, intermittent login/access failures, a filestore access issue affecting one customer environment, and delayed pipeline status updates in the UI. ‌ We have identified and are implementing a permanent fix for the underlying configuration defect, and have already put in place resource and capacity changes that resolve the UI delay symptom. ‌ At no point during this incident were pipeline executions themselves lost, corrupted, or left in a stuck state. Where execution behavior was affected, it was limited to delays in status visibility, not in the underlying processing. # Incident Details ## Incorrect Production Configuration Values Applied Our engineering team confirmed a defect in the S

Read Harness's official incident report ↗