outages.live
Live

Buildkite

Buildkite is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

26

Days with an incident

26

Median duration

1 h 9 min

Longest incident

24 h 25 min

Components

32

REST API

REST API Operational
90 days ago6 days with an incidentToday
Remote MCP Server Operational
90 days ago3 days with an incidentToday
Web Operational
90 days ago8 days with an incidentToday
Agent API Operational
90 days ago8 days with an incidentToday
Job Queue Operational
90 days ago6 days with an incidentToday
SCM Integrations Operational
90 days agoNo incidentsToday
Docs Operational
90 days agoNo incidentsToday

Third Party Services

AWS ec2-us-east-1 Operational
90 days agoNo incidentsToday
AWS elasticache-us-east-1 Operational
90 days agoNo incidentsToday
AWS elb-us-east-1 Operational
90 days agoNo incidentsToday
AWS rds-us-east-1 Operational
90 days agoNo incidentsToday

SCM Providers

GitHub Operational
90 days agoNo incidentsToday
GitHub API Requests Operational
90 days agoNo incidentsToday
GitHub Webhooks Operational
90 days ago1 day with an incidentToday
Atlassian Bitbucket SSH Operational
90 days agoNo incidentsToday
Atlassian Bitbucket Website and API Operational
90 days agoNo incidentsToday
Atlassian Bitbucket Git via HTTPS Operational
90 days agoNo incidentsToday

Notifications

GitHub Commit Status Notifications Operational
90 days ago4 days with an incidentToday
Email Notifications Operational
90 days ago5 days with an incidentToday
Slack Notifications Operational
90 days ago4 days with an incidentToday
Webhook Notifications Operational
90 days ago4 days with an incidentToday

Test Engine

Web Operational
90 days ago3 days with an incidentToday
Ingestion Operational
90 days ago1 day with an incidentToday
REST API Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration2 h 1 min19:57 to 21:58Elevated job dispatch timesDegraded

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

Oct 28, 2026

Duration32 min23:17 to 23:49Increased latency and error ratesDegraded

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.

Oct 24, 2026

Duration1 min23:40 to 23:40Elevated error ratesNotice

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.

Oct 22, 2026

Duration46 min16:51 to 17:37Delays with Hosted Agents jobsDegraded

Processing of Hosted Agents jobs are no longer delayed.

Oct 20, 2026

Duration24 h 25 min22:13 to 22:38Buildkite response to the eMudhra certificate compromiseNotice

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.

Duration1 h 8 min19:57 to 21:05Delayed notificationsDegraded

Adding additional capacity has resolved the notifications latency.

Oct 19, 2026

Duration1 min15:45 to 15:45Delayed Hosted Agents instance creationDegraded

We received reports from a few customers that Hosted Agent jobs were delayed in starting. We investigated and found this related to a GitHub incident with webhooks that caused throttling in Hosted Agent job creation once webhooks were once again being ingested. Any affected Hosted Agents customers would have seen delays in instance creation between 15:45-17:12UTC.

Oct 6, 2026

Duration5 h 40 min18:19 to 23:59Degraded checkout performance with Hosted AgentsDegraded

The issue is now resolved. Network maintenance from our provider caused unexpected side effects that impacted outgoing traffic from Hosted Agents.

Oct 1, 2026

Duration47 min06:10 to 06:57Small number of incoming GitHub Webhook failingDegraded

The error rate has returned to normal levels.

Sep 30, 2026

Duration1 h 29 min01:03 to 02:32Delayed notificationsDegraded

Outbound notification latency remains at expected levels. Some customers may have received duplicate notifications before the underlying error was resolved.

Sep 22, 2026

Duration42 min20:07 to 20:50Issues with webhook ingestion, GraphQL queriesPartial outage

## Service Impact On September 22, 2026, between 19:09 and 19:32 UTC, customers experienced failures ingesting webhooks and executing GraphQL queries. Some web application requests also failed or timed out. During this period, 2.0% of requests to our webhook ingestion endpoints and 20.3% of requests to our external GraphQL endpoint returned HTTP 500 errors. Webhook ingestion errors ceased by 19:30 UTC, and external GraphQL errors returned to background levels by 19:32 UTC. ## Incident Summary While investigating a separate API performance issue, we made a manual configuration change intended to rollback a routing change for one database proxy. The command instead changed the routing configuration for another database proxy, disrupting access to a database shard used internally by Buildkite. Some customer-facing operations search across all database shards to locate their shard, where routing information isn't available in the request. Those requests round robin through available shards

Sep 21, 2026

Duration45 min23:47 to 00:32AWS us-east-1 outageNotice

We did not experience any customer impact during this AWS us-east-1 outage.

Duration1 h 10 min22:35 to 23:46Increased latency and error ratesDegraded

This incident has been resolved.

Sep 9, 2026

Duration6 h 47 min19:07 to 01:54Buildkite service disruptionPartial outage

## Service Impact _All times UTC unless stated otherwise._ Customers experienced elevated errors and latency across the Buildkite web interface, REST API, Agent API, and job queue during two periods: 18:43:00–19:21:00 and 20:02:00–20:28:00 on September 9, 2026. During these periods, customers encountered failed API requests, delayed job dispatch, and errors in agent operations including authentication, job acceptance, and artifact uploads. Some jobs impacted by the incident did not recover automatically. These jobs had to be manually cancelled and retried to complete successfully. Between 18:43:00–19:21:00: Agent API had an error rate up to 11.2% with no latency impact. REST API had a 9.7% error rate with no latency impact. Web request had a 2.6% error rate with no latency impact. Job queues were delayed by up to 3 minutes. Between 20:02:00–20:28:00: Agent API had an error rate up to 24.7% with no latency impact. REST API had a 4.9% error rate with no latency impact. Web requests had a

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane