Skip to main content
CircleCI

Issue authenticating only Bitbucket users

Degraded Lasted 2h 47m · started · CircleCI's page

Level
confirmed
Worst impact
Degraded
Components
Pipelines & Workflows
Down Index
21of 100

What to do

  • Check whether you use CircleCI Pipelines & Workflows. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2h 47m it lasted.

    Anything that failed between 2026-06-11 21:31 UTC and 2026-06-12 00:18 UTC may need a replay.
  • Subscribe to CircleCI's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=circleci works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from CircleCI 5

  1. investigating

    We are currently investigating this issue.

    provider

  2. 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.

    provider

  3. 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.

    provider

  4. 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.

    provider

  5. 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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-187973c835

Is CircleCI still down?

No, this incident was resolved 2026-06-12 00:18 UTC. For CircleCI's live state, see https://down.guide/circleci.

How long did it last?

2h 47m, from 2026-06-11 21:31 UTC to 2026-06-12 00:18 UTC, by the times CircleCI posted.

What was affected?

CircleCI named Pipelines & Workflows.

What caused it?

CircleCI hasn't published a root cause. If it does, it shows here.

Where does this come from?

CircleCI's official status page, https://status.circleci.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.