Jobs using IP ranges failing with infrastructure errors
Docker executor jobs with the IP ranges feature enabled failed at a higher rate with infrastructure errors. CircleCI reports that the incident is resolved and lasted about 2 hours and 26 minutes. A workaround was to rerun the failed job.
State
Resolved
Started
Lasted
2 h 26 min
Worst impact
Degraded
Timeline
6 updatesIdentified
1 h 8 min 47%
Monitoring
1 h 18 min 53%
Updates
Times in UTCAs posted by CircleCI
We have seen recovery for IP range jobs for gen2 docker jobs. We appreciate your patience while we worked through the incident.
We are continuing to monitor the rollout for recovery.
A fix has been fully deployed, we are now monitoring for recovery.
The fix for IP range docker jobs are rolling out across the fleet. We will monitor for recovery in infra fails.
We are continuing to rollout a fix for IP range docker jobs. Customers may continue to retry jobs that use IP ranges that experience infra fails. We will provide an update within 20 minutes on the fix.
Customers running Docker executor jobs with the IP ranges feature enabled are experiencing a higher rate of infrastructure failures. A fix is being rolled out. Customers who see an infrastructure failure on one of these jobs can rerun the failed job. We will provide another update as we have more information to share.
Affected components
1CircleCI in the last 90 days
Full historyIncidents in 90 days
40
Days with an incident
29
Median duration
1 h 14 min
This incident
2.0× the median
Other CircleCI incidents
All incidentsCircleCI·Delays and intermittent failures running Smarter Testing
Smarter Testing had delays and intermittent failures that affected Docker, Machine, macOS, and Windows jobs. CircleCI reports that the incident is resolved and that the outage lasted 2 hours and 48 minutes.
CircleCI·Minor Service Outage
CircleCI reports degraded service on api.anthropic.com. CircleCI reports that the incident is resolved and that it lasted 3 minutes.
CircleCI·Minor Service Outage
The Anthropic api.anthropic.com component had degraded performance. CircleCI reports that the incident is resolved and lasted 24 minutes.
CircleCI·Partially Degraded Service
CircleCI reports a partially degraded service that affects GitHub Pull Requests. CircleCI resolved this incident. It lasted 4 hours and 6 minutes.
CircleCI·Partially Degraded Service
CircleCI reported degraded service for GitHub Pull Requests. CircleCI resolved the issue. The outage lasted 3 minutes.
Follow CircleCI
Your coding agent knows when CircleCI is down, and tells you when a failure is theirs, not yours. You can also get CircleCI incidents in a feed reader or in Slack.
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.live/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 "circleci" and tell me if CircleCI 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.
https://outages.live/feed.xml?providers=circleci/feed subscribe https://outages.live/feed.xml?providers=circleciFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane