Is Buildkite Down?
Reachable from all 8 checked regions
Average response time: 359ms
Last checked · checks run every 6 hours
Official status page: https://www.buildkitestatus.com
Buildkite uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 26 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
26-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Buildkite does
Buildkite runs CI/CD pipelines in which the build agents run on infrastructure you control. Buildkite hosts the pipeline definitions, scheduling and the web dashboard, while the machines that compile and test code stay inside your own network. Engineering teams pick it to keep source and build secrets off a vendor's servers while still getting hosted orchestration.
What an outage looks like
Builds sit queued and never start, because agents poll the Agent API for work and receive nothing. Jobs already running usually finish, since that work happens on your machines, but results fail to upload and the pipeline never advances. The dashboard may be slow or error, and REST API calls from deploy scripts start failing.
What to do about it
Read the component list on Buildkite's status page rather than the headline: Web, Agent API, REST API, Remote MCP Server and Job Queue each fail on their own, and Job Queue is the one that stalls builds. Agents reconnect by themselves once the API returns, so restarting them rarely helps. Avoid re-triggering builds, which deepens the backlog.
Is it down for everyone, or just you?
If this page says Buildkite is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.
Related services
Buildkite outage FAQ
Do my builds keep running during a Buildkite outage?
Why are my builds queued but not starting?
Should I restart my build agents?
Is my code at risk during an outage?
How we measure this
- We request Buildkite's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Buildkite publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Buildkite goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring