CircleCI Status

Resolved: Pipelines and UI access have fully recovered.

Please contact customer support if you have issues running builds.

This incident has been resolved.

Monitoring: Pipelines are continuing to run as normal.

We will continue monitoring for recovery.

Monitoring: We have identified a source of increased system load which caused failures processing API requests.

We have mitigated the issue and jobs are now running as expected and UI access has recovered.

Some pipelines may have failed or failed to start. Resubmitting should correct these issues.

We are continuing to monitor to ensure recovery.

Investigating: We are investigating an issue that may cause some customers to be redirected to a login page and prevents some pipelines from starting. Thank you for your patience as we continue our mitigation of this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: Error rates viewing orgs are recovering. We will continue to monitor to verify the fix resolves the issues.

Identified: We have identified the cause of errors accessing orgs. We are implementing a fix, and will monitor for recovery as the change rolls out.

Investigating: We are continuing to investigate reports that some customers cannot access their organizations in CircleCI.

Our investigation continues to point to an authorization issue between CircleCI and GitHub. Some affected users have received a 403 from GitHub indicating the resource is SAML protected and the OAuth token may not be authorized.

We previously shared re-authenticating as a potential workaround. We have since received reports that this didn't restore access for all affected customers, so we don't consider it a reliable resolution at this time.

Our engineering team is continuing to investigate this to determine the cause and next steps. We will post another update as soon as we have more information.

We apologize for the continued disruption and appreciate your patience.

Investigating: We are still investigating reports that some customers cannot access their organizations in CircleCI.

Early findings suggest the problem may be related to GitHub authorization, where affected users receive a 403 from GitHub indicating the resource is SAML protected and the OAuth token may not be authorized.

We have not yet confirmed this as the root cause. As a potential workaround, some users may be able to restore access by performing a re-authentication: https://support.circleci.com/hc/en-us/articles/360051228052-How-to-Perform-a-Re-Authentication

We will post another update once we have more certainty.

Investigating: We are continuing to investigate reports that some customers are unable to access their organizations in CircleCI. Those affected may see errors when loading their organizations.

Our engineering team are still working to identify the cause. We will share another update as soon as we have more information.

Investigating: We are investigating reports that some customers are unable to access their organizations in CircleCI. Those affected may see errors when loading their organizations.

Our engineering team is actively investigating.

Resolved: Pipelines and UI access have fully recovered.

Please contact customer support if you have issues running builds.

This incident has been resolved.

Monitoring: Pipelines are continuing to run as normal.

We will continue monitoring for recovery.

Monitoring: We have identified a source of increased system load which caused failures processing API requests.

We have mitigated the issue and jobs are now running as expected and UI access has recovered.

Some pipelines may have failed or failed to start. Resubmitting should correct these issues.

We are continuing to monitor to ensure recovery.

Investigating: We are investigating an issue that may cause some customers to be redirected to a login page and prevents some pipelines from starting. Thank you for your patience as we continue our mitigation of this issue.

Investigating: We are currently investigating this issue.