CircleCI Status

Resolved: We have identified and applied a workaround for the RAM DIsk issue, which means customers can resume builds using /mnt/ramdisk. We appreciate your patience and understanding whilst we worked on resolving this whilst ensuring the security of our platform for all customers.

Monitoring: At present customers running Docker containers cannot use /mnt/ramdisk. Customers will need to modify their configuration to use the filesystem instead.

This has occurred in order to update the Docker Infrastructure that supports our working_directory: /mnt/ramdisk feature. This is a necessary step in order to address CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881.

This bug affects any Docker jobs utilizing working_directory: /mnt/ramdisk. Jobs will fail on checkout and workspace attachments.

The immediate workaround will be to remove any usage of working_directory: /mnt/ramdisk from your job which will require an update of .circleci/config.yml

Once this maintenance is complete, customers will be unable to utilize working_directory: /mnt/ramdiskuntil further notice.

Resolved: Some customers from 15:26:06 UTC to 18:44:16 UTC would have experienced intermittent issues with running docker jobs. We have since rolled back this change.

Resolved: The macOS resources performance issue has been fully resolved.

All M1 and M4 Pro medium/large resources are operating normally with standard wait times and network performance. We have monitored the infrastructure for stability and confirmed full recovery of all affected services.

We apologize for any inconvenience this may have caused. Thank you for your patience during this incident.

Monitoring: We are observing recovery of the macOS resources performance issue.

Wait times for M1 medium/large and M4 Pro medium/large resources have returned to normal levels Network performance within running jobs appears to be recovering

We are continuing to monitor the situation closely to ensure stability and will provide another update within 30 minutes as we confirm full resolution of the incident.

Identified: We are continuing to investigate degraded network performance affecting macOS resources in our infrastructure.

What's happening: We have identified reduced network bandwidth that is causing performance degradation for specific macOS resource classes.

What's impacted: M1 medium and large resources: Experiencing average wait times of up to 20 minutes before job start M4 Pro medium and large resources: Experiencing average wait times of approximately 5 minutes before job start Running jobs on affected resources: Network-dependent operations within jobs (cache restoration, pulling datasets, downloading dependencies) are also experiencing slowdowns. All other macOS resource classes are operating normally

Next update: We are actively working to resolve this issue and will provide an update within 30 minutes or sooner if the situation changes.

Identified: We are continuing to investigate this and are working with our datacenter provider to mitigate this issue.

Identified: We are experiencing delays starting jobs for M1 and M4 medium and large resource classes. Running jobs on these resource classes will also experience delays due to degraded network performance.

Resolved: We have identified a workaround for the issue preventing users from adding User Keys via the "Authorize with GitHub" option.

While the "Authorize with GitHub" button is currently experiencing issues, users can successfully add SSH keys to their projects using our fully supported and documented manual process : https://circleci.com/docs/guides/integration/add-ssh-key/#steps-to-add-additional-ssh-keys

This workaround provides full functionality for adding SSH keys to your projects, effectively resolving the immediate impact. Our engineering team is actively monitoring this issue and will implement a permanent fix to restore the GitHub authorization flow.

Post resolution Update - 17:30 UTC The GitHub authorization functionality for adding User Keys has been fully restored as of 9:21 UTC. The "Authorize with GitHub" button is now working as expected in project settings.

The manual workaround previously provided is no longer necessary, though it remains a valid alternative method for adding SSH keys.

Thank you for your patience while we resolved this issue.

Investigating: We are currently investigating an issue preventing users from adding User Keys to a project when clicking on "Authorize with Github". Adding any other keys such as deploy keys or existing authorized user keys continues to function normally.