- Level
- confirmed
- Worst impact
- Degraded
- Components
- Job Queue
- Down Index
- 20of 100
What to do
Check whether you use Buildkite Job Queue. 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 8m it lasted.
Anything that failed between 2026-11-03 18:14 UTC and 2026-11-03 20:22 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 4
- investigating
We're seeing increased latency and error rates for a subset of our customers. We're currently investigating and will provide status updates as they become available.
provider
- investigating
We are continuing to investigate. At this time, the issue is limited to a small subset of customers.
provider
- monitoring
We’ve scaled out the resources that process incoming webhooks and are seeing recovery. We’re now working through the backlog of queued jobs and continuing to monitor
provider
- resolved
We have seen recovery and latency has returned 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-c043f21cee
Is Buildkite still down?
No, this incident was resolved 2026-11-03 20:22 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
2h 8m, from 2026-11-03 18:14 UTC to 2026-11-03 20:22 UTC, by the times Buildkite posted.
What was affected?
Buildkite named Job Queue.
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.