- Level
- confirmed
- Worst impact
- Degraded
- Components
- FME, FME, FME
- Down Index
- 28of 100
What to do
Check whether you use Split (Harness FME) FME, 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 1d it lasted.
Anything that failed between 2026-07-02 15:48 UTC and 2026-07-03 16:11 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) 4
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are seeing the backlogged items worked through and continuing to monitor results.
provider
- monitoring
We are continuing to monitor results while the backlog is worked through.
provider
- resolved
This incident has been resolved.
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-c8156853d3
Is Split (Harness FME) still down?
No, this incident was resolved 2026-07-03 16:11 UTC. For Split (Harness FME)'s live state, see https://down.guide/split.
How long did it last?
1d, from 2026-07-02 15:48 UTC to 2026-07-03 16:11 UTC, by the times Split (Harness FME) posted.
What was affected?
Split (Harness FME) named FME, FME, 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.