Harness outage, 13 November 2026
Pipeline slowness on prod3
- Started
- Resolved
- 13 Nov 2026, 18:42 UTC (after 46 min)
- Impact
- Minor
- Affected
- Continuous Delivery - Next Generation (CDNG)
Is this still happening?
No. Harness marked this incident resolved on 13 Nov 2026, 18:42 UTC, 46 min after it began.
Right now: Harness reports all systems operational. (as of 13 Nov, 20:53 UTC) Live Harness status
At a glance
- Harness rated this a minor incident.
- It was resolved after 46 min. That is shorter than a typical Harness incident: the median of the 28 other resolved ones we recorded is 3 h 23 min.
- Harness had 9 other incidents in the 30 days before it.
- 5 earlier incidents look like the same kind of problem (same affected part or wording); the most recent was on 12 Nov 2026.
Our summary from the Harness incidents we have recorded since 5 Sept 2026 - how we count.
Last update from Harness
This incident has been resolved.
Similar Harness incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 17 min
-
, resolved after 12 min
Degraded performance in UI execution graph in prod3Postmortem
-
, resolved after 2 h 40 min
Prod2 Pipelines with verify step failing intermittentlyPostmortem
-
, resolved after 6 h 38 min
-
, resolved after 5 h 25 min
Delegate version 26.11.90407/26.10.90316 missing client tools
Other recent Harness incidents
-
Intermittent CI Pipeline using VM Runner slowness and errorsPostmortem
-
We are currently seeing delegate selection issue for VM infra executionsPostmortem
-
Degraded performance on prod4Postmortem
-
Intermittent failures in Policy step evaluations on Prod 7Postmortem
-
Prod1: Intermittent issue with IACM stages in some pipelinesPostmortem
-
Harness CI Cloud build issues when accessing Maven CentralPostmortem
Something wrong on this page?
Thanks - your report is on its way to us. We read every one.