Looking for an update now? Check the current status, or follow Buildkite for future changes.
77.2%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
73.3%
30
8
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Catch-up processing continues, most of the backlog is processed, ingestion latency is decreasing.
monitoring
Internal processing of uploaded test execution data has been delayed, and is currently catching up. No data has been dropped, and all data should be processed over the next hour.
Issues identified with buildkite-agent registration
Recovery is underway; we'll keep monitoring until recovery is complete.
investigating
We have rolled out a few changes to fix the underlying issues and are seeing signs of recovery.
We'll keep monitoring until all systems are fully recovered and communicate once we are confident everything is stable again.
investigating
We identified issues affecting certain customers when the buildkite-agent attempts to register with Buildkite. When agents are not able to register, builds may start to back up.
We've identified a potential root case and are attempting changes to fix it.
investigating
We're seeing increased latency and error rates for a subset of our customers. We're currently investigating and will provide status updates as they become available.
Systems have recovered and we are seeing new builds created. For a period of about 20min new builds could not be created due to a failure of our internal DNS services. No build requests were lost during this time and we are continuing to process the backlog
investigating
We have identified a fix and applied mitigations, and we are seeing signs of recovery.
investigating
We are currently investigating a sitewide outage.
investigating
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Legacy Incident Archive
32 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
March 2026
504 errors viewing builds
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The deploy to revert this change is complete and builds are loading normally. We will continue to monitor for any other issues.
identified
We've identified a change which we think is the cause of this issue, and we're in the process of reverting it.
investigating
We're seeing an increase in 504 errors when viewing pipeline builds. We're investigating this now.
Increased Delays with Hosted Agents
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The networking issue has been resolved, dispatch of Hosted Agents has returned to normal levels and no further issues with Git cloning. We are monitoring the situation.
identified
The issue has been identified to be related to Networking and affecting Git Mirror cloning.
