Login issues for some Bitbucket users

Final update

## Summary From 01:33 UTC to 05:18 UTC on July 14, 2026, customers with a Bitbucket-linked identity were unable to log in to CircleCI, and some customers experienced workflows that failed to start or update, due to a change in how Bitbucket's OAuth service reports account permissions. At 05:07 UTC, we deployed a fix that corrected how our systems read the updated permissions field. Some customers needed to log out and re-authenticate their Bitbucket integration after we deployed the fix. Our systems continued processing the backlog of affected jobs until 08:39 UTC. We thank our customers for their patience as we resolved this incident. Please reach out to our support team with any questions or concerns. The status page for this incident can be found [here](https://status.circleci.com/incidents/gsyjwybg477g). ## Background CircleCI supports logging in with a GitHub account, a Bitbucket account, or an email and password. When a customer logs in with a Bitbucket-linked identity, or when CircleCI needs to refresh the customer's access on their behalf, we exchange an authorization token with Bitbucket's OAuth service. This exchange includes a list of the permissions, or "scopes," the cu

1. Postmortem · Jul 14, 22:31 UTC
   ## Summary From 01:33 UTC to 05:18 UTC on July 14, 2026, customers with a Bitbucket-linked identity were unable to log in to CircleCI, and some customers experienced workflows that failed to start or update, due to a change in how Bitbucket's OAuth service reports account permissions. At 05:07 UTC, we deployed a fix that corrected how our systems read the updated permissions field. Some customers needed to log out and re-authenticate their Bitbucket integration after we deployed the fix. Our systems continued processing the backlog of affected jobs until 08:39 UTC. We thank our customers for their patience as we resolved this incident. Please reach out to our support team with any questions or concerns. The status page for this incident can be found [here](https://status.circleci.com/incidents/gsyjwybg477g). ## Background CircleCI supports logging in with a GitHub account, a Bitbucket account, or an email and password. When a customer logs in with a Bitbucket-linked identity, or when CircleCI needs to refresh the customer's access on their behalf, we exchange an authorization token with Bitbucket's OAuth service. This exchange includes a list of the permissions, or "scopes," the customer has granted us, which Bitbucket and CircleCI use to confirm what CircleCI is authorized to do on the customer’s behalf. ## What Happened \(All times UTC\) On April 8, 2026, [Bitbucket announced a change to its OAuth service](https://developer.atlassian.com/cloud/bitbucket/changelog/#CHANGE-31
2. Resolved · Jul 14, 05:15 UTC
   The issue where customers logging in with a Bitbucket-linked identity experienced login errors, and some customers experienced workflows that failed to start or did not update, has been resolved. What you may still experience and need to do - If you use Bitbucket as your login method, please log out and reauthenticate the CircleCI Bitbucket integration on your account. - If any of your workflows are stuck or showing missing status checks, please rerun them to pick up the fix. - If you continue to experience issues after taking these steps, please reach out to CircleCI Support. We thank you for your patience while our team worked on implementing a fix.
3. Monitoring · Jul 14, 04:21 UTC
   What's impacted Some customers logging in with a Bitbucket-linked identity were affected. This may also have included customers logging in with GitHub who have a linked Bitbucket identity on their account. Some customers also experienced workflows that were not starting or updating. What can you expect A fix has been deployed. We are monitoring the situation to confirm full recovery. Next update We will provide an update if anything changes
4. Investigating · Jul 14, 03:51 UTC
   What's impacted Some customers logging in with a Bitbucket-linked identity are affected. This may also include customers logging in with GitHub but have a linked Bitbucket identity on their account. Additionally, some customers are experiencing workflows that are not starting or updating. What can you expect Affected customers may see login errors. Some customers may also notice workflows that fail to start or do not update as expected. Thank you for your patience while our engineers investigate. Next update We will provide another update as soon as we have more information to share
5. Investigating · Jul 14, 03:29 UTC
   Our team continues to investigate login errors affecting some customers using Bitbucket as their identity provider.
6. Investigating · Jul 14, 02:49 UTC
   We are currently investigating login errors affecting some customers using Bitbucket as their identity provider.