- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Agent API
- Down Index
- 28of 100
What to do
Check whether you use Buildkite Agent API. 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 50m it lasted.
Anything that failed between 2026-05-07 08:48 UTC and 2026-05-07 09:37 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've spotted that something has gone wrong. We're currently investigating the issue with new builds not starting.
provider
- investigating
We've identified issue with job acquiring endpoint. We're rolling back now. We'll provide next update in ~20 minutes.
provider
- identified
We're currently seeing recovery at 50% rate. We'll provide next update soon.
provider
- resolved
We've reverted a change that caused stale environment variables provided to acquire job used in Hosted Agents, agent-stack-k8s and other agent implementations using acquire job.
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-d1996baaa0
Is Buildkite still down?
No, this incident was resolved 2026-05-07 09:37 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
50m, from 2026-05-07 08:48 UTC to 2026-05-07 09:37 UTC, by the times Buildkite posted.
What was affected?
Buildkite named Agent API.
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.