- Level
- confirmed
- Worst impact
- Degraded
- Components
- Agent API
- Down Index
- 19of 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 1h 35m it lasted.
Anything that failed between 2026-08-25 06:41 UTC and 2026-08-25 08:16 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
At 06:04 UTC we deployed a defective request routing change to `agent-edge.buildkite.com`, which caused some customers' agents to abruptly disconnect. At 06:09 UTC we noticed the problem, and immediately reverted the change. We began to observe recovery at 06:10 UTC, and are continuing to monitor.
provider
- monitoring
Agent connectivity is recovered, but some agents are not reconnecting automatically after the earlier forced disconnects. We recommend restarting agent service to make agents reconnect.
provider
- resolved
This incident has been resolved.
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-cb94ec8114
Is Buildkite still down?
No, this incident was resolved 2026-08-25 08:16 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
1h 35m, from 2026-08-25 06:41 UTC to 2026-08-25 08:16 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.