Increased latency and error rates
Buildkite reported increased latency and error rates on the Agent API for some customers. Buildkite reports that the incident is resolved. The incident lasted 19 minutes.
State
Resolved
Started
Lasted
19 min
Worst impact
Notice
Timeline
2 updatesInvestigating
19 min 100%
Updates
Times in UTCAs posted by Buildkite
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
We're seeing increased latency and error rates on our Agent API 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
31
Days with an incident
28
Median duration
1 h 10 min
This incident
73% shorter than the median
Other Buildkite incidents
All incidentsBuildkite·Increased latency and error rates
Buildkite reported increased latency and error rates that affected the Job Queue. Buildkite patched the webhook-processing deployment and monitored the recovery. The incident is resolved and it lasted about 90 minutes.
Buildkite·Partially Degraded Service
Buildkite reports degraded service on the GitHub component. Buildkite resolved the incident. The incident lasted 99 minutes.
Buildkite·Elevated API error rates
Buildkite reported high error rates on the REST API and the Agent API. Buildkite later reported that the errors decreased. The incident is resolved and it lasted 33 minutes.
Buildkite·Increased latency and error rates
Buildkite reported increased latency and error rates for a small subset of customers. Buildkite scaled out the resources that process incoming webhooks and monitored the recovery. The incident is resolved and lasted about 2 hours and 8 minutes.
Buildkite·Elevated job dispatch times
We are seeing the job dispatch times are back to normal.
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.live/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.live/feed.xml?providers=buildkite/feed subscribe https://outages.live/feed.xml?providers=buildkiteFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane