- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Split (Harness 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 0m it lasted.
Anything that failed between 2026-04-28 21:48 UTC and 2026-04-28 18:27 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) 1
- resolved
Requests made by SDKs with Rule Based Segments support could have gotten a null instead of an empty for responses with no Rule Based Segments, leading to an null pointer exception. Impact observed: 18:27 until 19:05 UTC. The impact for SDKs would have been a failure to initialize or process an update. Any change made to feature flags or RBS in an affected environment would re-generate any specific caches remaining.
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-07cf954f95
Is Split (Harness FME) still down?
No, this incident was resolved 2026-04-28 18:27 UTC. For Split (Harness FME)'s live state, see https://down.guide/split.
How long did it last?
0m, from 2026-04-28 21:48 UTC to 2026-04-28 18:27 UTC, by the times Split (Harness FME) posted.
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.