Live / Harness / Incident
Harness: Degraded performance on prod4
Harness · split.ioMinor incidentResolved2026-10-19 08:21 UTC
Public — what happened
Summary
Harness reported a minor incident described as degraded performance on its prod4 environment, beginning at 07:46 UTC on 2026-10-19. The company said it began investigating right away and by 08:02 UTC had identified the issue and put a fix in place. Harness then monitored the results, and the incident was marked resolved at 08:21 UTC. The company did not say who was affected or what caused the problem.
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
Timeline
- Started — 2026-10-19 07:46 UTC
- Investigating — 2026-10-19 07:46 UTC
- Monitoring — 2026-10-19 08:02 UTC
- Identified — 2026-10-19 08:02 UTC
- Monitoring — 2026-10-19 08:04 UTC
- Resolved — 2026-10-19 08:21 UTC · 35 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Harness against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Harness: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Harness report →
More from Harness
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.