- Level
- confirmed
- Worst impact
- Degraded
- Components
- REST API, Agent API
- Down Index
- 17of 100
What to do
Check whether you use Buildkite REST API, 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 32m it lasted.
Anything that failed between 2026-10-28 23:17 UTC and 2026-10-28 23:49 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 saw increased latency and error rates in REST and GraphQL for a subset of our customers starting around 22:30 UTC until 22:45. The platform has been stable since. We're investigating the root cause
provider
- resolved
We identified that the majority of the impact was for a single customer and was caused by a database failover. We are investigating the cause and we will work with the impacted customer.
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-5023b6f030
Is Buildkite still down?
No, this incident was resolved 2026-10-28 23:49 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
32m, from 2026-10-28 23:17 UTC to 2026-10-28 23:49 UTC, by the times Buildkite posted.
What was affected?
Buildkite named REST API, 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.