CircleCI Incident History

Some customers are experiencing checkout step failures.

We've identified an issue affecting users attempting to log in with username and password credentials. Our engineering team has determined this is related to an ongoing incident with Auth0, our authentication provider. Users can track the Auth0 incident status at https://status.auth0.com/incidents/zgyzzt12c40v. We're actively monitoring the situation and will provide updates as the issue is resolved. We apologize for any inconvenience this may cause.

Between 09:54UTC and 10:01UTC all jobs experienced a slight delay in starting. All jobs will have run, so it is not necessary rerun any of them. We apologize for the delay.

We are investigating intermittent issues triggering pipelines or sending status updates.

We are investigating intermittent issues with loading the CircleCI UI.

We are investigating intermittent issues with loading the CircleCI UI.

We are continuing to investigate this issue.

We are investigating a delays in starting workflows.

Error message displayed is configs deemed to be invalid. A fix is identified and being implemented.

The issue has been identified and a fix is being implemented.

Our engineers are investigating an issue where some customers may see delays with status updates. The impact is limited to Github App basic status and does not affect oAuth basic or Github checks.We appreciate your patience and understanding as we actively work to resolve this delay. We will keep you updated on our progress.

Between 7:15 UTC and 7:50 UTC, some customers may have been impacted by increased job start latency. Our engineering team promptly identified and resolved this issue and job start times have now returned to normal levels. We thank you for your patience and understanding.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

For additional details, please refer to this announcement: https://discuss.circleci.com/t/docker-executor-infrastructure-upgrade/52282

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are updating the infrastructure supporting the arm resource class and the ip_ranges feature on the Docker Executors through April 1st. Customers may experience build failures during this time. View the announcement post for more information: link.

The issue impacting the wait time on M2 pro medium resource class has now been resolved. We thank you for your patience while we worked through to resolve the delays caused.

A fix has been implemented for the issue impacting our M2 pro medium resource class. The wait times are within normal range and we will continue to monitor the situation as the fix gets rolled out. We thank you for your patience while our engineers worked to resolve this delay.

Our engineers have identified the issue and implemented a fix where builds using m2pro.medium resource class were delayed for up to 6 minutes. We are starting to see recovery in the wait time. We thank you for your patience as we continue to work on this issue.

Our engineers are investigating an issue where customers using M2 Pro medium resource class may experience a higher wait time (delays of up to 6 minutes). We appreciate your patience and understanding as we actively work to resolve this delay. We will keep you updated on our progress.

This incident is now resolved.

The pipelines page is recovering and we are observing normal behaviour. We are continuing to monitor.

We have identified the cause and are continuing to work on a fix.

We have identified an issue causing a timeout when loading the Pipelines page on projects. We are currently working on a potential fix. Pipelines are running as normal.

There was increased wait times for M2 Pro Large.

The issue causing delays in outbound webhooks setup for job completed event has now been resolved. We thank you for your patience and understanding while our engineers worked to fix this issue.

The issue causing delays in outbound webhooks has now been mitigated, the latencies in outbound webhooks are back to normal. We will continue to monitor the situation. Thank you for your understanding while we worked to investigate the issue.

Our engineers are currently investigating an issue causing delays in outbound webhooks, the impact is limited to customers that have outbound webhooks setup for job completed. We will provide updates as soon as more information is available. Thank you for your understanding.