# Bitbucket authentication failures affecting sign-in and Bitbucket-backed accounts

- Provider: [Pulumi Cloud](https://down.guide/pulumi)
- Level: confirmed
- Impact: Degraded
- lasted 1h 57m
- started 2026-06-11 22:20 UTC
- API, Console
- id: DWN-a5029d7486
- Official page: https://stspg.io/rzb7vqbvn2s9

## Updates from Pulumi Cloud
### 2026-06-11 22:20 UTC: investigating
We are investigating an issue affecting customers who sign in to Pulumi Cloud
with a Bitbucket identity or use Bitbucket-connected accounts.
Beginning at approximately 06:00 UTC on June 11, requests to refresh Bitbucket
authentication tokens began failing. Affected users may experience failed
sign-ins with Bitbucket, as well as intermittent errors in the Pulumi Console
and API after their current Bitbucket session token expires (these tokens
expire every two hours). Integrations that rely on Bitbucket credentials may
also be affected.
Our investigation indicates the failures originate from Bitbucket's OAuth
token service rather than Pulumi infrastructure, and we have engaged Atlassian
support. Customers using GitHub, GitLab, email, or SSO identities
are unaffected.
Workaround: Customers whose Pulumi account has an additional sign-in method
(GitHub, GitLab, email/password, or SSO) can continue to sign in using that
method.
We will post updates as the investigation progresses.

### 2026-06-11 22:56 UTC: identified
Atlassian has acknowledged an incident affecting Bitbucket OAuth login,
which is the cause of the Bitbucket sign-in and authentication failures
affecting Pulumi Cloud. Their incident is being tracked at:
https://bitbucket.status.atlassian.com/incidents/h51sr145gsmx
The issue is external to Pulumi, and no action is required from Pulumi
customers. Until Atlassian resolves their incident, customers signing in
with a Bitbucket identity may continue to experience failed sign-ins and
intermittent Console and API errors after their current session token
expires. Customers using GitHub, GitLab, email, or SSO identities remain
unaffected.
Workaround: Customers whose Pulumi account has an additional sign-in method
(GitHub, GitLab, email/password, or SSO) can continue to sign in using that
method.

### 2026-06-12 00:02 UTC: monitoring
Atlassian has deployed a fix for their incident affecting Bitbucket OAuth login, and we have confirmed that Bitbucket authentication requests from Pulumi Cloud are succeeding again. Error rates have returned to normal levels and sign-in with Bitbucket is working.

### 2026-06-12 00:17 UTC: resolved
The incident has now been resolved and the service is operating normally for all customers.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).