User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
buildkite.com · Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 133 ms · 8 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 217 ms | 0 |
| 03:15 | 0 | 0.0 | 190 ms | 0 |
| 03:30 | 0 | 0.0 | 343 ms | 0 |
| 03:45 | 0 | 0.0 | 192 ms | 0 |
| 04:00 | 0 | 0.0 | 492 ms | 0 |
| 04:15 | 0 | 0.0 | 382 ms | 0 |
| 04:30 | 0 | 0.0 | 314 ms | 0 |
| 04:45 | 0 | 0.0 | 344 ms | 0 |
| 05:00 | 0 | 0.0 | 898 ms | 0 |
| 05:15 | 0 | 0.0 | 108 ms | 0 |
| 05:30 | 0 | 0.0 | 257 ms | 0 |
| 05:45 | 0 | 0.0 | 183 ms | 0 |
| 06:00 | 0 | 0.0 | 458 ms | 0 |
| 06:15 | 0 | 0.0 | 189 ms | 0 |
| 06:30 | 0 | 0.0 | 78 ms | 0 |
| 06:45 | 0 | 0.0 | 222 ms | 0 |
| 07:00 | 0 | 0.0 | 157 ms | 0 |
| 07:15 | 0 | 0.0 | 154 ms | 0 |
| 07:30 | 0 | 0.0 | 132 ms | 0 |
| 07:45 | 0 | 0.0 | 336 ms | 0 |
| 08:00 | 0 | 0.0 | 295 ms | 0 |
| 08:15 | 0 | 0.0 | 273 ms | 0 |
| 08:30 | 0 | 0.0 | 213 ms | 0 |
| 08:45 | 0 | 0.0 | 267 ms | 0 |
| 09:00 | 0 | 0.0 | 275 ms | 0 |
| 09:15 | 0 | 0.0 | 190 ms | 0 |
| 09:30 | 0 | 0.0 | 102 ms | 0 |
| 09:45 | 0 | 0.0 | 169 ms | 0 |
| 10:00 | 0 | 0.0 | 134 ms | 0 |
| 10:15 | 0 | 0.0 | 164 ms | 0 |
| 10:30 | 0 | 0.0 | 217 ms | 0 |
| 10:45 | 0 | 0.0 | 233 ms | 0 |
| 11:00 | 0 | 0.0 | 351 ms | 0 |
| 11:15 | 0 | 0.0 | 239 ms | 0 |
| 11:30 | 0 | 0.0 | 319 ms | 0 |
| 11:45 | 0 | 0.0 | 196 ms | 0 |
| 12:00 | 0 | 0.0 | 295 ms | 0 |
| 12:15 | 0 | 0.0 | 145 ms | 0 |
| 12:30 | 0 | 0.0 | 563 ms | 0 |
| 12:45 | 0 | 0.0 | 178 ms | 0 |
| 13:00 | 0 | 0.0 | 161 ms | 0 |
| 13:15 | 0 | 0.0 | 169 ms | 0 |
| 13:30 | 0 | 0.0 | 289 ms | 0 |
| 13:45 | 0 | 0.0 | 227 ms | 0 |
| 14:00 | 0 | 0.0 | 366 ms | 0 |
| 14:15 | 0 | 0.0 | 209 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Buildkite yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Buildkite goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Buildkite alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Buildkite is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Buildkite's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.