Buildkite reported "Buildkite response to the eMudhra certificate compromise" on its status page at 2026-10-20 22:13 UTC.

Buildkite did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-20 22:13 UTC and ended at 2026-10-21 22:38 UTC. It lasted 24 h 25 min.

How do I get alerts for Buildkite?

Subscribe to the Buildkite live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Buildkite. outages.live reads it every few minutes and keeps every update.

BuildkiteIncident · 2026-10-20 22:13 UTC

Buildkite response to the eMudhra certificate compromise

ResolvedOfficial update

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.

The latest update from Buildkite.

State

Resolved

Started

11 d ago

2026-10-20 22:13 UTC

Lasted

24 h 25 min

until 2026-10-21 22:38 UTC

Worst impact

Notice

Timeline

4 updates

22:1304:2010:2616:3222:38

NoticeUpdate postedTimes in UTC

Investigating

1 h 11 min 5%

Monitoring

23 h 13 min 95%

Updates

Times in UTC

As posted by Buildkite

Resolved2026-10-21 22:38 UTC

Monitoring2026-10-21 05:07 UTC

We’ve finished updating the services that power Buildkite so they no longer trust the affected eMudhra certificates. No action is needed from customers for Buildkite hosted services. For components that run in customer infrastructure, we still recommend upgrading to the releases listed in our previous update (Buildkite agent v4.7.0 / v3.138.2, Buildkite CLI v3.64.2, and bktec v3.3.1). We’re continuing to release updates for the other binaries we distribute and will post them here as they ship.

Monitoring2026-10-20 23:25 UTC

We're continuing to monitor the situation, and are making releases to many of our components that run in customer infrastructure. At time of writing, we've released versions that distrust the affected eMudhra certificates for: - Buildkite agent: https://github.com/buildkite/agent: - v4.7.0: https://github.com/buildkite/agent/releases/tag/v4.7.0 - v3.138.2: https://github.com/buildkite/agent/releases/tag/v3.138.2 - Buildkite CLI: https://github.com/buildkite/cli/releases/tag/v3.64.2 - bktec: https://github.com/buildkite/test-engine-client/releases/tag/v3.3.1 We recommend updating to these versions to prevent exposure to the affected certificate providers. We will continue to issue updates for the other binaries we distribute, and are updating any internal services that are affected.

Investigating2026-10-20 22:13 UTC

The private keys for eight certificates issued by eMudhra, an external certificate authority, have been compromised. Software that still trusts these certificates may accept fraudulent HTTPS certificates. We’re updating the services that power Buildkite and preparing new CLI and Agent releases, which we expect to ship shortly. We’re also tracking fixes to the libraries and trust stores we depend on and will apply them as they become available. We’ll update this page with the new versions and any action customers need to take. Mozilla has published background on the compromise.

Buildkite in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 9 min

This incident

21× 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 job dispatch times

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

Resolvedresolved 2 d ago

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.

Resolvedresolved 3 d ago

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.

Resolvedresolved 7 d ago

Buildkite·Delays with Hosted Agents jobs

Processing of Hosted Agents jobs are no longer delayed.

Resolvedresolved 10 d ago

Buildkite·Delayed notifications

Adding additional capacity has resolved the notifications latency.

Resolvedresolved 11 d ago

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

RSS

https://outages.cc/feed.xml?providers=buildkite

Slack

/feed subscribe https://outages.cc/feed.xml?providers=buildkite

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane