- Level
- confirmed
- Worst impact
- Degraded
- Components
- Ingestion
- Down Index
- 18of 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 44m it lasted.
Anything that failed between 2026-03-07 00:21 UTC and 2026-03-07 01:05 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 3
- investigating
We are investigating the elevated latency issue for Test Engine. Processing the backlog of test executions is taking longer than expected, so elevated ingestion latency remains.
provider
- monitoring
We've identified the issue and the system is currently processing the backlog of test executions
provider
- resolved
Processing of test execution ingestion data has successfully caught up.
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-91046d07f2
Is Buildkite still down?
No, this incident was resolved 2026-03-07 01:05 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
44m, from 2026-03-07 00:21 UTC to 2026-03-07 01:05 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.