Errors and latency for pipelines
Buildkite Pipelines had errors and delays. The REST API, Web, and Agent API were affected. Buildkite reports that the incident is resolved. It lasted 63 minutes.
State
Resolved
Started
Lasted
1 h 3 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
35 min 55%
Monitoring
28 min 45%
Updates
Times in UTCAs posted by Buildkite
Buildkite Pipelines is operating normally, and this incident is now resolved. We’re continuing to investigate the underlying database issue.
Some customers may have experienced increased errors and delays with Buildkite Pipelines, including artifact operations and agent requests, beginning at approximately 21:46 UTC on November 12. The disruption appears to have subsided around 21:56 UTC. We are not currently observing ongoing customer impact. We are monitoring service health and continuing to investigate the cause, and will update as further information is available.
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Affected components
4Buildkite in the last 90 days
Full historyIncidents in 90 days
33
Days with an incident
28
Median duration
1 h 8 min
This incident
About the median
Other Buildkite incidents
All incidentsBuildkite·Increased error rates on Agent API
The Agent API had increased error rates and latencies. Buildkite reports that the incident is resolved. It lasted about 63 minutes, from 19:12 to 20:15 UTC.
Buildkite·Partially Degraded Service
Buildkite reported a partially degraded service that affected GitHub API Requests. Buildkite has resolved the incident. The outage lasted 33 minutes.
Buildkite·Increased error rates on Agent API
Buildkite reported increased error rates on the Agent API. Buildkite later reported recovery and monitored the service. Buildkite resolved the incident after about 3 hours and 29 minutes.
Buildkite·Partially Degraded Service
Buildkite reported a partially degraded service on GitHub and GitHub API Requests. Buildkite reports that the issue is resolved. The outage lasted 96 minutes.
Buildkite·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.
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