CircleCI Status

Resolved: Customers using Bitbucket as their VCS provider or as their login provider experienced errors when interacting with Bitbucket repositories and authenticating to CircleCI. This was caused by an incident with Atlassian Bitbucket's OAuth service, which has now been resolved and all affected functionality has returned to normal.

Monitoring: What's happening Atlassian Bitbucket has moved their OAuth service incident to monitoring. You can follow their status at https://bitbucket.status.atlassian.com/incidents/h51sr145gsmx

What's impacted Customers using Bitbucket as their VCS provider may be experiencing disruptions.

What can you expect You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Customers using Bitbucket as their login provider may also be unable to authenticate to CircleCI.

Thank you for your patience while we continue to monitor recovery.

Identified: What's happening Atlassian Bitbucket has acknowledged an incident affecting their OAuth service, which is the cause of the errors our customers are experiencing. The status of their incident is available at: https://bitbucket.status.atlassian.com/incidents/h51sr145gsmx

What's impacted Customers using Bitbucket as their VCS provider may be experiencing disruptions.

What can you expect You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Customers using Bitbucket as their login provider may also be unable to authenticate to CircleCI.

We will provide an update as soon as we have more information. Thank you for your patience while we monitor Bitbucket's incident and recovery.

Identified: What's happening We are investigating an issue we believe is related to an ongoing incident with Atlassian Bitbucket's authentication service. We are actively monitoring Bitbucket's status.

What's impacted Customers using Bitbucket as their VCS provider may be experiencing disruptions.

What can you expect You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Thank you for your patience while our engineers investigate.

We will provide an update as soon as we have more information.

Investigating: We are currently investigating this issue.

Resolved: Between 13:29 UTC and 18:20 UTC on June 9, 2026, some customers experienced 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs running were not impacted during this window. The issue has been resolved and all affected functionality has returned to normal. We thank you for your patience while our team worked on implementing a fix.

Monitoring: A fix has been deployed for the 500 errors customers were experiencing on the pipeline values and workflow API endpoints and in the UI. Engineers are monitoring the change. Jobs running are not impacted

Investigating: Our engineers are continuing to investigate the 500 errors customers are experiencing on the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs currently running are not impacted.

Investigating: Some customers are experiencing 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI.

Engineers are actively investigating.

Resolved: This incident has been resolved.

Monitoring: The fix has been rolled out and we are monitoring for recovery.

Identified: We have identified the cause of the failure and are rolling out a change.

Investigating: We are investigating reports of orb publishing failing.

Resolved: Between 13:29 UTC and 18:20 UTC on June 9, 2026, some customers experienced 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs running were not impacted during this window. The issue has been resolved and all affected functionality has returned to normal. We thank you for your patience while our team worked on implementing a fix.

Monitoring: A fix has been deployed for the 500 errors customers were experiencing on the pipeline values and workflow API endpoints and in the UI. Engineers are monitoring the change. Jobs running are not impacted

Investigating: Our engineers are continuing to investigate the 500 errors customers are experiencing on the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs currently running are not impacted.

Investigating: Some customers are experiencing 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI.

Engineers are actively investigating.

Resolved: This incident has been resolved.

Monitoring: We are seeing signs of recovery from the GitHub API.

Investigating: We are continuing to investigate this issue.

Investigating: Some users may have seen delays or missing commit statuses on GitHub PRs due to an ongoing GitHub API incident.

We are continuing to process builds as normal.

We will provide further updates as we get more information