Looking for an update now? Check the current status, or follow Pulumi for future changes.
94.8%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
93.3%
30
2
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A fix has been deployed and we're monitoring the results.
identified
We know about a problem with Bitbucket login for Pulumi Cloud. The problem started on 15 October 2026 at approximately 16:51 UTC.
You cannot log in to Pulumi Cloud with your Bitbucket account at this time. After you log in at Bitbucket, Pulumi Cloud shows the message "Internal Server Error".
Other login methods or Bitbucket repository integrations and deployments are not affected.
Legacy Incident Archive
8 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
GitHub has reported an active, critical incident. Related functionality in the Pulumi Console is temporarily unavailable.
July 2026
Some Team Access Token operations failing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
We are investigating an issue where some Team Access Tokens are unable to authenticate to the Pulumi Cloud API, which may result in failed deployments or API errors. We have identified the cause and a fix is being deployed. We will provide an update once the fix is live.
Degraded performance for Pulumi Cloud login
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
We have taken mitigation steps and are seeing signs of recovery. We are continuing to monitor the situation.
investigating
We are aware of an issue affecting login access to Pulumi Cloud and are investigating.
June 2026
Degraded performance on Pulumi APIs
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been rolled out and we are monitoring results
identified
We have identified a likely cause and are working on steps to address the issue.
investigating
We are continuing to investigate this issue.
investigating
We are aware of degraded performance on Pulumi APIs and are actively investigating the issue.
Bitbucket authentication failures affecting sign-in and Bitbucket-backed accounts
minorSource not attested
Last archived state: resolved
View archived record details
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.
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 ...
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...
May 2026
Elevated API error rates and latency
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed and error rates and response times have recovered. We are continuing to monitor.
investigating
Investigating elevated API error rates and response times, particularly with ESC endpoints
April 2026
Bitbucket Authentication Unavailable
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been deployed and we are seeing recovery. We are continuing to monitor to confirm the issue is fully resolved.
identified
We have started deploying a fix for this issue. We will provide an update once the deployment is complete.
investigating
Users authenticating with Bitbucket are currently unable to sign in to Pulumi Cloud or use the Pulumi Cloud API. This affects all operations that rely on Bitbucket authentication, including CLI usage and API calls.
Other authentication methods are not affected.
We have identified the cause of the issue and are actively working on a fix. We will provide an update once the fix has been deployed.
Slowed API response times
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are aware of reduced response times across Pulumi Cloud APIs. We have identified the cause and are working on a fix
