Provider
CircleCIIncident detail
Issues with network routing for Mac jobs
Issues with network routing for Mac jobs
Timeline window
to
Sponsored placement
Google AdSense placeholder
This slot is reserved for future AdSense placement. It stays as a non-invasive placeholder until a client ID and slot ID are configured.
Timeline
Incident updates
Updates are normalized from the official source chronology so timeline changes remain easy to scan.
Investigating
What's happening Our engineers are investigating network routing issues for some Mac jobs. What's impacted Mac jobs that make outbound requests, including checking out from GitHub.
Identified
We have implemented a change to address the routing issues and are monitoring the results.
Identified
Mac jobs are still seeing intermittent failures with network routing. We are working with our infrastructure provider to address the networking issues.
Identified
We are seeing improvement in Mac job network routing. We will continue to monitor for signs of recovery.
Monitoring
Our team is moving this incident to Monitoring status based on significant improvement seen in our tests and low error rate. We are seeing improvement in network routing for Mac jobs and are actively engaged with our infrastructure provider. If your Mac jobs experience network-related failures or degraded service please reach out to CircleCI support.
Monitoring
We are continuing to monitor for any further issues.
Monitoring
We are continuing to monitor. We still observe a low percentage of intermittent failures. The failure rate is trending down as we continue to monitor. We advise customers to contact CircleCI Support if they see a change in degraded services and increased failure rate.
Investigating
Due to continued reports of intermittent failures and a lack of sustained improvement while in monitoring status, this incident is elevated back to investigating to escalate with our infrastructure provider.
Monitoring
A fix has been implemented and we are monitoring the results.
Resolved
We are concluding this incident based on a confirmed fix with our infrastructure provider and successful tests. For any customers seeing failed runs, please run again for a successful connection.