- 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 51m it lasted.
Anything that failed between 2026-08-27 10:56 UTC and 2026-08-27 11:47 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
Internal processing of uploaded test execution data has been delayed, and is currently catching up. No data has been dropped, and all data should be processed over the next hour.
provider
- monitoring
Catch-up processing continues, most of the backlog is processed, ingestion latency is decreasing.
provider
- resolved
Processing of uploaded test execution data has caught up and is back to normal.
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-76e9a67728
Is Buildkite still down?
No, this incident was resolved 2026-08-27 11:47 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
51m, from 2026-08-27 10:56 UTC to 2026-08-27 11:47 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.