Skip to main content
Buildkite

Delayed Test Engine ingestion processing

Degraded Lasted 3h 10m · started · Buildkite's page

Level
confirmed
Worst impact
Degraded
Components
Ingestion
Down Index
21of 100

What to do

  • Check whether you use Buildkite Ingestion. 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 3h 10m it lasted.

    Anything that failed between 2026-05-12 12:59 UTC and 2026-05-12 16:09 UTC may need a replay.
  • Subscribe to Buildkite's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=buildkite works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Buildkite 2

  1. monitoring

    We are currently experiencing delayed processing of Test Engine data. We have identified and applied a fix for the issue but are expecting to continue to experience delays while we clear the ingestion backlog

    provider

  2. resolved

    The fix was successful and the backlog has now been cleared.

    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-6cfb17ba46

Is Buildkite still down?

No, this incident was resolved 2026-05-12 16:09 UTC. For Buildkite's live state, see https://down.guide/buildkite.

How long did it last?

3h 10m, from 2026-05-12 12:59 UTC to 2026-05-12 16:09 UTC, by the times Buildkite posted.

What was affected?

Buildkite named Ingestion.

What caused it?

Buildkite hasn't published a root cause. If it does, it shows here.

Where does this come from?

Buildkite's official status page, https://www.buildkitestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.