Delayed Hosted Agents instance creation
Timeline · 1 update
- resolved Oct 19, 2026, 05:39 PM UTC
We are getting reports from a few customers that Hosted Agent jobs are delayed in starting. We are investigating.
Buildkite had 53 outages in the last 2 years totaling 56h 53m of downtime — averaging 2.2 incidents per month.
There were 53 Buildkite outages since October 15, 2025 totaling 56h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are getting reports from a few customers that Hosted Agent jobs are delayed in starting. We are investigating.
We've received reports of degraded checkout performance with GitHub repositories when using Hosted Agents and are investigating.
We continue to observe degraded checkout performance. Our engineering teams are working on establishing an alternative network transit path to alleviate networking performance issues.
The issue is now resolved. Network maintenance from our provider caused unexpected side effects that impacted outgoing traffic from Hosted Agents.
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.
The mitigation is rolling out and we are seeing recovery. We will continue to monitor and provide an update.
The error rate has returned to normal levels.
We are investigating delays to build and job notifications for a subset of customers.
We've resolved the underlying error, and outbound notifications queues are now in the process of catching up for impacted customers.
Outbound notification queues have now fully caught up for all impacted customers.
Outbound notification latency remains at expected levels. Some customers may have received duplicate notifications before the underlying error was resolved.
Between 11:45 and 15:00 (GMT+10) on 28 September, macOS hosted agent jobs could not start because of a misconfigured agent image update. This has been fixed and new jobs are running normally. Jobs from that window still waiting in the Scheduled state won't start on their own. Please cancel and retry them.
We're aware of a major AWS outage in us-east-1, we are taking action to prevent impact and monitoring the situation.
We did not experience any customer impact during this AWS us-east-1 outage.
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 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.
This incident has been resolved.
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 have deployed mitigations and have observed recovery across Hosted Agents. We will continue monitoring.
Jobs running on Hosted Agents are now being dispatched promptly.
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.
Some job dispatches to hosted agents are timing out, leading to jobs starting late. We're currently investigating and will update again soon.
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.
Jobs running on Hosted Agents are now being dispatched promptly.
We're investigating an issue with job dispatch to our Hosted Agents.
Our engineers are continuing to investigate an issue with delayed job dispatch for Hosted Agents. Job dispatch for self-hosted agents remains unaffected.
We're beginning to see recovery with delayed job dispatch for Hosted Agents. We are currently working through the backlog of delayed jobs.
We are continuing to process through the backlog of delayed jobs and monitoring.
Job dispatch for Hosted Agents is no longer experiencing delays.
We are experiencing delivery issues with email notifications due to an issue with an upstream provider.
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.
We are seeing successful email deliveries and are monitoring processing of our outbound email queue.
Our outbound email queue has finished processing all previously failed deliveries. Email notifications are processing successfully.
Internal processing of uploaded test execution data has been delayed, and is currently catching up. No data has been dropped, and all data should be processed over the next hour.
Catch-up processing continues, most of the backlog is processed, ingestion latency is decreasing.
Processing of uploaded test execution data has caught up and is back to normal.
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 identified issues affecting certain customers when the buildkite-agent attempts to register with Buildkite. When agents are not able to register, builds may start to back up. We've identified a potential root case and are attempting changes to fix it.
We have rolled out a few changes to fix the underlying issues and are seeing signs of recovery. We'll keep monitoring until all systems are fully recovered and communicate once we are confident everything is stable again.
Recovery is underway; we'll keep monitoring until recovery is complete.
Mitigation strategies worked as expected and now agent registration is back to normal. All systems are stable now.
At 06:04 UTC we deployed a defective request routing change to `agent-edge.buildkite.com`, which caused some customers' agents to abruptly disconnect. At 06:09 UTC we noticed the problem, and immediately reverted the change. We began to observe recovery at 06:10 UTC, and are continuing to monitor.
Agent connectivity is recovered, but some agents are not reconnecting automatically after the earlier forced disconnects. We recommend restarting agent service to make agents reconnect.
This incident has been resolved.
We've spotted that something has gone wrong and there's elevated latency. We're currently investigating the issue, and will provide an update soon.
We've identified the cause of the issue and are actively mitigating.
We have identified and fixed the issue. We are monitoring and seeing signs of improvement.
We think the impact from the issue is over.
Between 22:03 - 22:16 UTC customers experienced delayed job dispatch, build processing and notifications. Additionally there were errors receiving webhooks during this period.
We're observing increased latency for all our customers. We're currently investigating and will provide status updates as they become available.
We've isolated the issue to elevated load on our REST API service and are working to mitigate. The agent and stacks API isn’t affected.
We've isolated the issue to elevated load on our REST API service and have mitigated the issue. The agent and stacks API isn’t affected.
The mitigation applied before the last update had the intended effect, and we have seen recovery in REST API latency.
We're observing increased latency and error rates for a subset of our customers on the Agent API. We're currently investigating and will provide status updates as they become available.
Between 00:05 - 00:34 UTC, a subset of customers experienced increased latency and timeout errors on the Agent API. This impacts job assignment. At peak impact, we saw an error rate of 1.3% of requests and job acceptance latency up to 53s.
We have received reports email deliveries have not been working, affecting signup and invite emails as well as build notification emails. This issue has now been resolved.
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.
Processing of the backlog is complete.
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Additional capacity was added to our redis caches. This triggered a failover between UTC 15:10 - 15:14 and there was a spike of errors on the REST and GraphQL APIs. Customers would have seen some errors in the Buildkite UI during this period as well. We have been monitoring the situation since then and things have returned to baseline.