- Level
- confirmed
- Worst impact
- Degraded
- Components
- Ingestion
- Down Index
- 23of 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 8h 36m it lasted.
Anything that failed between 2026-03-04 03:59 UTC and 2026-03-04 12:35 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
- monitoring
We've identified and fixed the root cause and now monitoring the issue. Test execution may be delayed for up to 30 minutes.
provider
- monitoring
Processing the backlog of test executions is taking longer than expected, so elevated ingestion latency remains. We continue to monitor progress. We have also identified database schema improvements we can make that will increase throughput to avoid this scenario in future.
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-e57dae2900
Is Buildkite still down?
No, this incident was resolved 2026-03-04 12:35 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
8h 36m, from 2026-03-04 03:59 UTC to 2026-03-04 12:35 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.