Is Pulumi down?

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.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are aware of an issue affecting login access to Pulumi Cloud and are investigating.

We have taken mitigation steps and are seeing signs of recovery. We are continuing to monitor the situation.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are aware of degraded performance on Pulumi APIs and are actively investigating the issue.

We are continuing to investigate this issue.

We have identified a likely cause and are working on steps to address the issue.

A fix has been rolled out and we are monitoring results

We are continuing to monitor for any further issues.

This incident has been resolved.

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.

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.

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.

The incident has now been resolved and the service is operating normally for all customers.

Investigating elevated API error rates and response times, particularly with ESC endpoints

A fix has been deployed and error rates and response times have recovered. We are continuing to monitor.

The incident has been resolved.