Is Buildkite down?
Operationalchecked 1 minute ago
We reached Buildkite from all 10 regions we check.
No outage recorded in the 14 days we have measured Buildkite (since Aug 22, 2026).
Buildkite reports: All systems operational (“All Systems Operational”)
Buildkite reports an active incident: Increased latency and error rates (all systems operational, since Sep 4, 2026, 1:40 AM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.
Buildkite's own component breakdown, as they publish it
- AWS ec2-us-east-1Operational
- GitHubOperational
- GitHub Commit Status NotificationsOperational
- Hosted AgentsOperational
- REST APIOperational
- WebOperational
- WebOperational
- WebOperational
- Agent APIOperational
- AWS elasticache-us-east-1Operational
- Email NotificationsOperational
- GitHub API RequestsOperational
- IngestionOperational
- MacOSOperational
- Package Managers - APIOperational
- Remote MCP ServerOperational
- AWS elb-us-east-1Operational
- GitHub WebhooksOperational
- Linux (ARM64)Operational
- Rest APIOperational
- REST APIOperational
- Slack NotificationsOperational
- Atlassian Bitbucket SSHOperational
- AWS rds-us-east-1Operational
- Linux (AMD64)Operational
- Atlassian Bitbucket Website and APIOperational
- Job QueueOperational
- Atlassian Bitbucket Git via HTTPSOperational
- Webhook NotificationsOperational
- SCM IntegrationsOperational
- DocsOperational
These are Buildkite's components, named and scored by Buildkite. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Buildkite's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Buildkite response time, by region
Is it Buildkite, or is it you?
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Buildkite -- it cannot diagnose Buildkite's own systems.
What we measured, function by function
Buildkite answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
- APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 321msstatus code: 401checked: Sep 5, 2026, 2:07 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Buildkite normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestOperationallatency: 142msstatus code: 401checked: Sep 5, 2026, 2:07 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Buildkite normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralOperationallatency: 72msstatus code: 401checked: Sep 5, 2026, 1:57 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Buildkite normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaOperationallatency: 128msstatus code: 401checked: Sep 5, 2026, 1:57 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Buildkite normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaOperationallatency: 565msstatus code: 401checked: Sep 5, 2026, 1:58 AM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Buildkite normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 287msstatus code: 401checked: Sep 5, 2026, 1:58 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Buildkite normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKOperationallatency: 243msstatus code: 401checked: Sep 5, 2026, 1:57 AM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Buildkite normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 1075msstatus code: 401checked: Sep 5, 2026, 2:00 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Buildkite normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaOperationallatency: 415msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Buildkite normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaOperationallatency: 533msstatus code: 401checked: Sep 5, 2026, 2:06 AM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Buildkite normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Buildkite, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Buildkite yet, which is not evidence that nothing is wrong.
Recent outages
measured entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Buildkite since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Buildkite covering any window you pick, with our measurements and Buildkite's own claim at the time, side by side.
Full availability history for Buildkite: 90-day availability by region, month-by-month uptime, and every incident on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversTell me when this goes down
Get told when we measure this
We will tell you when our probes stop reaching Buildkite, and again when they can reach it again. That is our own measurement from ten regions, not Buildkite's status page. No account, no card.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/buildkite)<a href="https://realuptime.io/outages/buildkite"><img src="https://realuptime.io/outages/buildkite/badge.svg?days=30" alt="Buildkite uptime measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What Buildkite's SLA implies, from our measurement
At or above your target
We measured none of downtime for Buildkite over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.
By our measurement there is no shortfall to claim for this period.
This is computed from our own probe measurements, not from Buildkite's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.