Buildkite incident

AWS us-east-1 single availability zone outage

Buildkite is currently experiencing a minor incident, which began 1d ago. The vendor's full update timeline is below.

Started
May 08, 2026, 01:12 AM UTC
Resolved
Ongoing
Duration
● 1d 1h
Detected by Pingoru
May 08, 2026, 01:12 AM UTC

Update timeline

  1. investigating May 08, 2026, 01:12 AM UTC

    We're aware that AWS is reporting availability zone failures in us-east-1. We are monitoring the situation but so far there is no customer impact.

  2. investigating May 08, 2026, 01:50 AM UTC

    A small subset of our customers are experiencing delayed notifications. We are actively provisioning additional capacity for these customers. Availability zone automatic failovers are occurring in response to the outage, and this is causing some brief error blips for some customers.

  3. investigating May 08, 2026, 02:35 AM UTC

    We are continuing to actively monitor the impacts of this availability zone outage for Buildkite customers. Some transient errors are visible due to availability zone failover events.

  4. investigating May 08, 2026, 04:08 AM UTC

    We have provisioned additional capacity in unaffected availability zones so that they are able to support the additional load. Automatic failovers continue to occur where necessary. Some latency and transient errors will be visible to customers.

  5. investigating May 08, 2026, 05:10 AM UTC

    We are actively moving resources out of us-east-1c. Similar brief latency and error blips will be visible to customers while these manual failovers occur.

  6. investigating May 08, 2026, 05:45 AM UTC

    We are continuing to move infrastructure resources out of the affected AWS Availability Zone. Brief latency and error blips will unfortunately continue while these manual failovers occur.

  7. investigating May 08, 2026, 07:04 AM UTC

    We are continuing to move infrastructure resources out of the affected AWS Availability Zone. Brief latency and error blips may continue while these manual failovers occur.

  8. investigating May 08, 2026, 07:22 AM UTC

    We are continuing to move infrastructure resources out of the affected AWS Availability Zone. Brief latency and error blips may continue while these manual failovers occur. (Apologies if you receive duplicated notifications for this update.)

  9. monitoring May 08, 2026, 08:07 AM UTC

    Despite the ongoing AWS incident, our own services are now stable. We are continuing to monitor our services closely, and are ready for further action should the need arise. We are also watching AWS services closely as they recover.