Minor Service Outage
CircleCI reports degraded GitHub Git Operations, GitHub Pull Requests, and GitHub API Requests. CircleCI reports that the incident is resolved. The incident lasted 99 minutes.
State
Resolved
Started
Lasted
1 h 39 min
Worst impact
Degraded
Timeline
2 updatesComponents degraded
1 h 39 min 100%
Updates
Times in UTCAs posted by CircleCI
Affected components
3CircleCI in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
24
Median duration
1 h 31 min
This incident
About the median
Other CircleCI incidents
All incidentsCircleCI·Partially Degraded Service
CircleCI reported degraded service for GitHub Git Operations. The incident started at 21:03 UTC and lasted 102 minutes. CircleCI reports that this outage is resolved.
CircleCI·Increased wait time for Machine and Remote Docker jobs
CircleCI reports increased wait times for Machine and Remote Docker jobs. The provider applied a fix and monitored the result. The incident is resolved and lasted about 54 minutes.
CircleCI·Delays for gen2 dedicated IP range jobs
## **Summary** From 14:20 to 19:08 UTC on October 28, customers running Gen 2 Docker jobs using IP Ranges saw increased wait times for their jobs to start. From 14:20 until 17:02, the delays were intermittent, and from 17:02 to 18:50, the delays were continuous. No other job types were affected. The incident was caused by limited availability of the cloud instances we had configured for the IP Ranges cluster. In response, our engineering team added additional fallback instance types to the IP Ranges cluster and transferred capacity from one of our other Gen 2 clusters to the IP Ranges cluster. By 18:50, wait times had improved, and by 19:08 they had fully recovered. After we resolved the incident, we increased the number of baseline cloud instances we maintain for IP Ranges jobs. We have also configured an IP Ranges cluster in an additional cloud region. The original status page can be found here: [Delays for gen2 dedicated IP range jobs](https://status.circleci.com/incidents/8q9j33r2r
CircleCI·Increased Docker gen2 wait times
## Summary From 15:44 to 20:55 UTC on October 21, customers running Gen 2 Docker jobs saw increased wait times for their jobs to start. Delays were longest on the 2xlarge resource class, where jobs waited up to 20 minutes. The incident was caused by limited availability of the cloud instances we had configured to meet demand, particularly for 2xlarge jobs. In response, our engineering team configured additional instance types, configured additional Gen 2 Docker clusters. By 20:55 UTC, wait times had returned to normal and the incident was resolved. After the incident was resolved, we expanded our Gen 2 Docker fleet into additional cloud regions, and we continue actively standing up additional cloud regions to prevent similar incidents in the future. The original status page can be found here: [October 21 - Increased Docker gen2 wait times](https://status.circleci.com/incidents/5jb50gh55gtj). ## Background When CircleCI executes a Docker job, we schedule it on one of several clusters of
CircleCI·Increased wait times for macOS jobs on m4pro.large
Wait times for macOS jobs on the m4pro.large resource class have returned to normal. We thank you for your patience while the backlogs cleared.
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