- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 100
What to do
Check whether your product depends on Buildkite. 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-01 02:41 UTC and 2026-05-01 03:30 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
- identified
We've identified a service change that is causing a service disruption. We are reverting this change.
provider
- monitoring
We've corrected the issue that caused this disruption and normal service has been restored. We are monitoring the situation now.
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-ce705d75e0
Is Buildkite still down?
No, this incident was resolved 2026-05-01 03:30 UTC. For Buildkite's live state, see https://down.guide/buildkite.
How long did it last?
50m, from 2026-05-01 02:41 UTC to 2026-05-01 03:30 UTC, by the times Buildkite posted.
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.