CircleCI's Docker Jobs component ran delayed for 1h 7m on 28 October 2026, after gen2 jobs using dedicated IP ranges got stuck starting. CircleCI says the cause was limited compute availability at its cloud provider, not anything in your pipeline configuration.
Started
18:15 UTC
Duration
Lasted 1h 7m
Source
IsDown
Next time
CircleCI is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Docker Jobs
What happened?
CircleCI logged one incident on 28 October 2026, affecting the Docker Jobs component. It started at 18:15 UTC with a filing that said docker gen2 jobs using dedicated IP ranges were delayed by about 10 minutes, and that no other resource classes were affected. At 18:51 CircleCI identified the cause as limited compute availability from its cloud provider, and said it was working to free up capacity. By 19:06 it reported signs of recovery, with wait times returning to normal. The incident was marked resolved at 19:19, giving a total duration of 1h 7m. That is four updates across just over an hour, which is a reasonably tight loop for a capacity problem that depends on a third party freeing up resources. No user reports were filed during the window, so there is no external account to weigh against CircleCI's own timeline. Over the past 90 days CircleCI has logged 26 incidents with a median duration of 1 hour 42 minutes, so this one resolved faster than typical. CircleCI has not published a post-mortem for this incident, and nothing beyond the four status updates above is on record explaining why its cloud provider ran short of compute for gen2 dedicated IP jobs specifically.
Learning
This incident sat entirely inside CircleCI's build infrastructure, specifically the layer that provisions compute for gen2 jobs on dedicated IP ranges, and nothing about it would show up from inside your own application or repository. If you only watch your own endpoints, a delay like this looks like nothing at all until your builds start queuing and your team starts asking why deploys are slow. CircleCI's own explanation, limited compute availability from its cloud provider, is the kind of fault that sits one layer below what any status page you control can see. Over a 30 day window, UptimeRobot's own probes recorded 11 incidents against CircleCI with a median duration of 1h 31m, all resolved, which gives you an independent timeline that does not depend on CircleCI choosing to publish one. That is the general shape of this kind of failure: your pipeline is healthy, your code is fine, and the slowdown still comes from the provider's side. Your own monitoring covers your half of that boundary. UptimeRobot watches the provider's half too, so next time this happens you know which side broke without guessing.