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.
The latest update from Buildkite.
State
Resolved
Started
3 d ago
2026-10-28 23:17 UTC
Lasted
32 min
until 2026-10-28 23:49 UTC
Worst impact
Degraded
Timeline
2 updatesMonitoring
32 min 100%
Updates
Times in UTCAs posted by Buildkite
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.
We saw increased latency and error rates in REST and GraphQL for a subset of our customers starting around 22:30 UTC until 22:45. The platform has been stable since. We're investigating the root cause
Affected components
3Buildkite in the last 90 days
Full historyIncidents in 90 days
26
Days with an incident
26
Median duration
1 h 9 min
This incident
54% shorter than the median
Other Buildkite incidents
All incidentsBuildkite·Elevated job dispatch times
We are seeing the job dispatch times are back to normal.
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.
Buildkite·Buildkite response to the eMudhra certificate compromise
All services that power Buildkite have been updated to distrust the affected certificates, and updated releases are available for the components we distribute that run in customer infrastructure: Buildkite agent: v4.7.0 and v3.138.2 Buildkite CLI: v3.64.2 bktec: v3.3.1 elastic-ci-stack-for-aws: v7.8.0 agent-stack-k8s: v0.52.0 We recommend updating to these versions to prevent exposure to the affected certificate providers.
Buildkite·Delayed notifications
Adding additional capacity has resolved the notifications latency.
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