Increased error rates on Agent API
Buildkite reports increased error rates on the Agent API. The Agent API shows degraded performance. Buildkite has seen recovery and continues to monitor the affected service.
State
Monitoring
Started
Ongoing for
2 h 53 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
52 min 30%
Monitoring
2 h 1 min 70%
Updates
Times in UTCAs posted by Buildkite
The affected services have recovered, and we will continue to monitor the issue.
We have seen recovery and are currently monitoring the impacted services.
We are investigating elevated error rates on the Agent API
Affected components
1Buildkite in the last 90 days
Full historyIncidents in 90 days
33
Days with an incident
28
Median duration
1 h 15 min
This incident
2.3× the median
Other Buildkite incidents
All incidentsBuildkite·Partially Degraded Service
Buildkite reports a partially degraded service that affects GitHub and GitHub API Requests. Buildkite reports that the incident is resolved. The incident lasted 96 minutes.
Buildkite·Increased latency and error rates
Buildkite reports increased latency and error rates on the Agent API for some customers. Buildkite says the incident is resolved. It lasted about 19 minutes.
Buildkite·Increased latency and error rates
Buildkite reported increased latency and error rates on the Job Queue. Buildkite patched the webhook-processing deployment to add capacity. Buildkite reports that the incident is resolved. The incident lasted about 90 minutes, from 22:38 on 3 November 2026 to 00:07 on 4 November 2026.
Buildkite·Partially Degraded Service
Buildkite reported partially degraded service for its GitHub component. Buildkite later reported that the issue is resolved. The incident lasted 99 minutes.
Buildkite·Elevated API error rates
Buildkite reported elevated API error rates. The REST API and the Agent API had a partial outage. Buildkite reports that the incident is resolved. The outage lasted about 33 minutes.
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