Live  /  Buildkite  /  Incident

Buildkite: Buildkite response to the eMudhra certificate compromise

Buildkite · buildkite.comResolved2026-10-21 22:38 UTC
Public — what happened

Summary

Buildkite said that the private keys for eight certificates issued by an outside certificate authority, eMudhra, were compromised, meaning software that still trusts them could accept fraudulent secure website certificates. The notice began on October 20, 2026, and Buildkite said it updated its own hosted services to stop trusting those certificates, with no action needed from customers for those services. For software running in customers' own systems, it released new versions of its agent, command-line tool and bktec and recommended upgrading. The incident is marked resolved as of October 21, 2026.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Buildkite against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Buildkite: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Buildkite report →

More from Buildkite

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Buildkite status & history page.

Related: Buildkite status & history. SquidGrid is not affiliated with Buildkite.