Increased latency and error rates
Buildkite reports increased latency and error rates for a small subset of customers. The issue affects webhook processing. Buildkite scaled out the resources that process incoming webhooks and sees recovery. Buildkite now works through the backlog of queued jobs and continues to monitor.
State
Monitoring
Started
Ongoing for
1 h 40 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 31 min 91%
Monitoring
9 min 9%
Updates
Times in UTCAs posted by Buildkite
We’ve scaled out the resources that process incoming webhooks and are seeing recovery. We’re now working through the backlog of queued jobs and continuing to monitor
We are continuing to investigate. At this time, the issue is limited to a small subset of customers.
We are continuing to investigate. At this time, the issue appears to be limited to a small subset of customers.
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.
Buildkite in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
27
Median duration
1 h 9 min
This incident
1.4× the median
Other Buildkite incidents
All incidentsBuildkite·Elevated API error rates
The Buildkite REST API and Agent API have elevated error rates. The REST API component is also affected. Buildkite is investigating this problem.
Buildkite·Elevated job dispatch times
We are seeing the job dispatch times are back to normal.
Buildkite·Increased latency and error rates
We identified that the majority of the impact was for a single customer and was caused by a database failover. We are investigating the cause and we will work with the impacted customer.
Buildkite·Elevated error rates
Between 23:16 and 23:27 we saw elevated error rates across our platform due to a scheduled database upgrade. That upgrade was not intended to cause any impact, but due to an unforeseen dependency on this database customers experienced error rates averages 2.5% during this period.
Buildkite·Delays with Hosted Agents jobs
Processing of Hosted Agents jobs are no longer delayed.
Follow Buildkite
Your coding agent knows when Buildkite is down, and tells you when a failure is theirs, not yours. You can also get Buildkite incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "buildkite" and tell me if Buildkite has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=buildkite/feed subscribe https://outages.cc/feed.xml?providers=buildkiteFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane