Looking for an update now? Check the current status, or follow Buildkite for future changes.
77.2%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
73.3%
30
8
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We continue to observe degraded checkout performance. Our engineering teams are working on establishing an alternative network transit path to alleviate networking performance issues.
investigating
We've received reports of degraded checkout performance with GitHub repositories when using Hosted Agents and are investigating.
The mitigation is rolling out and we are seeing recovery. We will continue to monitor and provide an update.
identified
Since 2026-09-30 20:52:36 UTC on 30 September, small amount of incoming GitHub webhook deliveries to Buildkite pipelines are being rejected, so the related builds are not created.
For people who use GitHub.com may affect ability to receive status checks. We have identified the cause and are deploying a mitigation. This does not affect GitHub Enterprise Server and other SCM providers.
We observed a slight increase in latency for build creation isolated to a few customers, this has now passed and we are seeing signs of improvement.
investigating
We're seeing increased latency and error rates for a subset of our customers. We're currently investigating and will provide status updates as they become available.
We are seeing improvements across the affected services, and are seeing services return to normal functionality. We are continuing to monitor and are determining the root cause.
investigating
We are continuing to investigate elevated error rates across multiple services, and are working to determine the cause.
investigating
We are continuing to investigate this issue. We are seeing impact on the Agent API which will affect job scheduling, artifact uploads, and an increase in 5xx responses from the Agent API endpoints.
investigating
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
We have deployed mitigations and have observed recovery across Hosted Agents. We will continue monitoring.
investigating
We're seeing increased latency and error rates within our Hosted Agents. We're currently investigating and will provide status updates as they become available.
We're seeing recovery in hosted job scheduling rates. Your jobs should run, but there may be some delays as we work through any backlogs.
investigating
Some job dispatches to hosted agents are timing out, leading to jobs starting late. We're currently investigating and will update again soon.
investigating
We're seeing increased latency and error rates for a subset of our customers. We're currently investigating and will provide status updates as they become available.
We are continuing to process through the backlog of delayed jobs and monitoring.
identified
We're beginning to see recovery with delayed job dispatch for Hosted Agents. We are currently working through the backlog of delayed jobs.
investigating
Our engineers are continuing to investigate an issue with delayed job dispatch for Hosted Agents. Job dispatch for self-hosted agents remains unaffected.
investigating
We're investigating an issue with job dispatch to our Hosted Agents.
We are seeing successful email deliveries and are monitoring processing of our outbound email queue.
identified
Our on-call engineers are working on failing over to an alternative upstream email provider to restore outbound email notifications. No other Buildkite services have been impacted by this disruption.
identified
We are experiencing delivery issues with email notifications due to an issue with an upstream provider.
Legacy Incident Archive
32 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Delayed notifications
majorSource not attested
Last archived state: resolved
View archived record details
identified
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
investigating
We are investigating delays to build and job notifications for a subset of customers.
Increased latency and error rates
Source not attested
Last archived state: resolved
View archived record details
monitoring
We've identified the problem and have completed the remediation steps, we are now monitoring as service resumes.
identified
We're observing increased latency and error rates for a subset of our customers. We're currently remediating and will provide status updates as they become available.
Delayed notifications
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are seeing recovery across affected customers and continue to monitor
identified
We have identified the issue and applied mitigations and are monitoring recovery
We have determined that only a subset of customers are affected by the notification latency.
investigating
We are investigating delays to notifications across all customers
Delayed Test Engine ingestion processing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Ingestion of Test Engine execution data from an internal queue to a data store stalled, has been resumed, and is working through the backlog. Visibility of test executions from the past hour hours will be delayed for approximately a further one hour.
This has been a recurring issue; an architectural change is coming soon to eliminate this failure mode.
Error rates increasing
Source not attested
Last archived state: resolved
View archived record details
investigating
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Delayed Test Engine ingestion processing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are currently experiencing delayed processing of Test Engine data. We have identified and applied a fix for the issue but are expecting to continue to experience delays while we clear the ingestion backlog
Delayed Test Engine ingestion processing
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently experiencing delayed processing of Test Engine data. We have identified and applied a fix for the issue but are expecting to continue to experience delays while we clear the ingestion backlog. At the current processing rate we expect the backlog to be cleared by approximately Sat 09 May 2026 00:00 UTC
Delayed Test Engine ingestion processing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are currently experiencing delayed processing of Test Engine data. We have identified and applied a fix for the issue but are expecting to continue to experience continued processing delays while we clear the ingestion backlog. At the current processing rate we expect the backlog to be cleared by approximately Fri 08 May 2026 13:30 UTC.
AWS us-east-1 single availability zone outage
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
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.)
investigating
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.
investigating
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.
investigating
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.
investigating
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.
investigating
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.
investigating
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.
investigating
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.
Delays in job dispatch, webhook processing, and outbound webhooks
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have now monitoring the incident. We are seeing most customers have recovered, and some showing signs of recovery.
identified
We've identified the issue and are working on applying mitigations. At this time we can confirm inbound and outbound webhooks, and notifications are delayed.
investigating
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
