- Level
- confirmed
- Worst impact
- Partial outage
- Components
- FME
- Down Index
- 26of 100
What to do
Check whether you use Split (Harness FME) FME. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 16m it lasted.
Anything that failed between 2026-08-24 00:57 UTC and 2026-08-24 01:12 UTC may need a replay.Subscribe to Split (Harness FME)'s feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=split works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Split (Harness FME) 5
- investigating
We are currently investigating this issue.
provider
- investigating
We are currently investigating reports that the Feature Management & Experimentation (FME) user interface is failing to load. Customers attempting to access the FME console may encounter errors or unresponsive pages. Feature flag evaluation and SDK traffic are not believed to be affected. A further update will follow shortly.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
- postmortem
## Summary * Starting at **23:42 UTC** on August 23, 2026, several FME customers reported failures loading the FME UI. * FME UI Artifacts served from the CDN expired due to a retention policy, causing FME UI to fail to load. * Any flag request changes through the API, change delivery, and the data pipeline continued to work with no interruption. ## Root Cause * The FME UI is served from a CDN. The UI artifacts got evicted due to a retention policy, causing the UI to fail to load for all users. ## Impact * The FME UI was unable to load for all users across all production environments. ### What was not impacted? * SDK functionality and runtime flag evaluation * Admin API calls * Customer flag configuration data * No data loss occurred ## Remediation * FME UI got restored in the CDN through a deployment * Recovery confirmed across all production environments before closing the incident. ## Action Items * Improve the asset retention policy so that the currently active version is never subject to eviction.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-c64343e33f
Is Split (Harness FME) still down?
No, this incident was resolved 2026-08-24 01:12 UTC. For Split (Harness FME)'s live state, see https://down.guide/split.
How long did it last?
16m, from 2026-08-24 00:57 UTC to 2026-08-24 01:12 UTC, by the times Split (Harness FME) posted.
What was affected?
Split (Harness FME) named FME.
What caused it?
Split (Harness FME) hasn't published a root cause. If it does, it shows here.
Where does this come from?
Split (Harness FME)'s official status page, https://status.harness.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.