outages.live
Live
BuildkiteIncident · 2026-09-21 23:47 UTC

AWS us-east-1 outage

ResolvedOfficial update

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

The latest update from Buildkite.

State

Resolved

Started

40 d ago

2026-09-21 23:47 UTC

Lasted

45 min

until 2026-09-22 00:32 UTC

Worst impact

Notice

Timeline

2 updates
23:4723:5800:1000:2100:32
NoticeUpdate postedTimes in UTC

Monitoring

45 min 100%

Updates

Times in UTC

As posted by Buildkite

Resolved2026-09-22 00:32 UTC

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

Monitoring2026-09-21 23:47 UTC

We're aware of a major AWS outage in us-east-1, we are taking action to prevent impact and monitoring the situation.

Buildkite in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

26

Days with an incident

26

Median duration

1 h 9 min

This incident

34% shorter than 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·Buildkite response to the eMudhra certificate compromise

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.

Resolvedresolved 10 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