CircleCI's Machine Jobs component slowed down for 55 minutes on 3 November 2026, with Machine and Remote Docker job wait times climbing well above normal. CircleCI says increased usage was behind the slowdown, and the fault sits on their side, not yours.
Started
14:14 UTC
Duration
Lasted 55m
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: Machine Jobs
What happened?
CircleCI opened the incident at 14:14 UTC, reporting that some users would see increased wait times for Machine and Remote Docker jobs because of increased usage. At that point they put the wait time at just under 7 minutes. That is the only component CircleCI named: Machine Jobs. By 14:45 CircleCI posted that a fix had been applied and wait times were starting to recover, while they kept monitoring the rollout. The incident closed at 15:08, 55 minutes after it opened, with CircleCI stating that wait times had returned to normal for Machine and Remote Docker. There are three updates on record for this incident, and all three are shown here, so the published timeline is complete as far as CircleCI chose to disclose it. No user reports were filed during the window. CircleCI's own account is the only source for what happened: it names a cause, increased usage, but gives no detail on what drove that usage up or why it pushed wait times past normal. Over the last 90 days CircleCI has logged 26 incidents, with a median duration of 1 hour 35 minutes, so this one resolved faster than CircleCI's typical incident. Across all time CircleCI has recorded 113 incidents, averaging 14.1 a month.
Learning
This incident shows a queue backing up behind the build pipeline rather than the pipeline going down outright: jobs still ran, they just waited longer to start. That is a layer an uptime check on your own endpoints will not see, because your product can stay fully reachable while your CI jobs sit in CircleCI's queue for minutes longer than usual. Over the last 30 days UptimeRobot's own checks against CircleCI recorded 11 incidents, all resolved, with a median duration of 1h 14m, a different count from CircleCI's own 90-day median of 26 incidents at 1 hour 35 minutes, because the two are measuring from different vantage points and different windows. Neither number is wrong. One reflects what CircleCI itself chose to publish, the other reflects what an external vantage point actually observed. If your build pipeline slows down with no change on your end, the cause is as likely to be queue pressure on CircleCI's infrastructure as anything in your own configuration. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.