Skip to main content
Split (Harness FME)

FME SDK are experiencing elevated error rates and delays in response.

Degraded Lasted 1h 47m · started · Split (Harness FME)'s page

Level
confirmed
Worst impact
Degraded
Components
FME, FME, FME
Down Index
24of 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 1h 47m it lasted.

    Anything that failed between 2026-05-08 17:05 UTC and 2026-05-08 18:53 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) 3

  1. investigating

    We are currently investigating this issue.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. 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-89de70ba33

Is Split (Harness FME) still down?

No, this incident was resolved 2026-05-08 18:53 UTC. For Split (Harness FME)'s live state, see https://down.guide/split.

How long did it last?

1h 47m, from 2026-05-08 17:05 UTC to 2026-05-08 18:53 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.