# Slowness in Prod1 and Prod2 environment

- Provider: [Split (Harness FME)](https://down.guide/providers/split)
- Confidence: Confirmed
- Impact: Degraded
- lasted 6h 38m
- started 2026-09-08 21:52 UTC
- Continuous Delivery (CD) - FirstGen - EOS, Continuous Delivery (CD) - FirstGen - EOS, Continuous Delivery - Next Generation (CDNG) +26
- id: DWN-a912034e90
- Official page: https://stspg.io/nq6pjsvq1481

## Updates from Split (Harness FME)
### 2026-09-08 21:52 UTC: investigating
We are currently investigating this issue.

### 2026-09-08 22:53 UTC: investigating
We are continuing to investigate this issue.

### 2026-09-08 22:53 UTC: investigating
We are continuing to investigate the issue.

### 2026-09-08 23:31 UTC: investigating
We are continuing to investigate this issue.

### 2026-09-08 23:52 UTC: identified
The issue has been identified and a fix is being implemented.

### 2026-09-09 00:29 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-09-09 00:36 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2026-09-09 00:39 UTC: monitoring
A fix has been implemented and we are monitoring the results.

### 2026-09-09 04:30 UTC: resolved
This incident has been resolved.

### 2026-09-09 23:23 UTC: postmortem
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 a feature flag, it was quickly disabled, and service was restored after a brief monitoring period. 
Customer Impact
\* Customers encountered slowness and failures during pipeline execution and UI operations. Some API calls returned errors or timed out.
\* No data loss or corruption occurred.
Root Cause
The new capability introduced a regression that created contention on a shared backend resource used by multiple Harness components. This saturated the shared platform infrastructure and caused the cascading failures.
Mitigation
\* Disabled the capability across all environments
\* Temporarily increased platform capacity to restore stability
Next Steps
To prevent recurrence, Harness will:
1. Permanently fix the capability by profiling and eliminating the sub-optimal code path and query
2. Improve detection by enhancing alerting for resource-intensive queries on high-frequency platform paths

From the builder: does your app depend on Split (Harness FME)? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=split) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Split (Harness FME).

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-a912034e90), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.