Outage in Pulumi
Bitbucket authentication failures affecting sign-in and Bitbucket-backed accounts
Resolved MinorIncident Report
Summary AI Generated
Pulumi Cloud experienced authentication failures for users signing in with Bitbucket identities, causing failed sign-ins and intermittent errors in the Console and API after session tokens expired every two hours. The issue was caused by an incident with Atlassian's Bitbucket OAuth service, not Pulumi's infrastructure, and affected Bitbucket-connected accounts and integrations while users with GitHub, GitLab, email, or SSO identities remained unaffected. The incident was resolved after approximately 11 hours when Atlassian deployed a fix for their OAuth service.
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.
Trusted by 1,000+ teams
The Status Page Aggregator with Early Outage Detection
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
about 2 hours ago - at 06/12/2026 12:17AM
The incident has now been resolved and the service is operating normally for all customers.
MONITORING
about 2 hours ago - at 06/12/2026 12:02AM
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.
IDENTIFIED
about 3 hours ago - at 06/11/2026 10:56PM
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.
INVESTIGATING
about 3 hours ago - at 06/11/2026 10:20PM
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.
Latest Pulumi outages
Elevated API error rates and latency - about 1 month ago
Bitbucket Authentication Unavailable - about 2 months ago
Slowed API response times - 2 months ago
Errors when creating new Pulumi Neo tasks - 4 months ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
