outages.live
Live
BuildkiteIncident ·

Partially Degraded Service

DegradedOfficial update
0

Buildkite reports partially degraded service that affects its GitHub component. The provider is investigating the problem.

State

Components degraded

Started

Ongoing for

1 h 21 min

Worst impact

Degraded

Timeline

1 update
21:0021:2021:4022:0022:21
DegradedUpdate postedTimes in UTC

Components degraded

1 h 21 min 100%

Updates

Times in UTC

As posted by Buildkite

Components degraded

Affected components

1
GitHub

Buildkite in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

29

Days with an incident

27

Median duration

1 h 9 min

This incident

1.2× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

24 h 25 min
median 1 h 9 min
90 days agoToday

Other Buildkite incidents

All incidents

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.

Resolved

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.

Resolved

Buildkite·Elevated job dispatch times

We are seeing the job dispatch times are back to normal.

Resolved

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.

Resolved

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.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=buildkite
Slack
/feed subscribe https://outages.live/feed.xml?providers=buildkite

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane