- Level
- confirmed
- Worst impact
- Degraded
- Components
- REST API, Web, Remote MCP Server
- Down Index
- 17of 100
What to do
Check whether you use Buildkite REST API, Web, Remote MCP Server. 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 20m it lasted.
Anything that failed between 2026-05-13 15:14 UTC and 2026-05-13 15:34 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
- investigating
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
provider
- resolved
Additional capacity was added to our redis caches. This triggered a failover between UTC 15:10 - 15:14 and there was a spike of errors on the REST and GraphQL APIs. Customers would have seen some errors in the Buildkite UI during this period as well. We have been monitoring the situation since then and things have returned to baseline.
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-7b1796cf92
Is Buildkite still down?
No, this incident was resolved 2026-05-13 15:34 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
20m, from 2026-05-13 15:14 UTC to 2026-05-13 15:34 UTC, by the times Buildkite posted.
What was affected?
Buildkite named REST API, Web, Remote MCP Server.
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.