- 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 2h 36m it lasted.
Anything that failed between 2026-04-22 02:32 UTC and 2026-04-22 05:07 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
- monitoring
We noticed a lag in data processing, but our systems are operational and currently working through the backlog. We expect to be fully caught up within the next couple of hours.
provider
- resolved
The backlog has been cleared and all systems are fully operational. Thank you for your patience.
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-f625a39d2b
Is Buildkite still down?
No, this incident was resolved 2026-04-22 05:07 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
2h 36m, from 2026-04-22 02:32 UTC to 2026-04-22 05:07 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.