Pulumi Outage History

Started Oct 16, 2026, 10:48 AM UTC· resolved Oct 16, 2026, 01:30 PM UTC

1. identified Oct 16, 2026, 10:48 AM UTC

   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.

2. monitoring Oct 16, 2026, 11:54 AM UTC

   A fix has been deployed and we're monitoring the results.

3. resolved Oct 16, 2026, 01:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 06, 2026, 03:35 PM UTC· resolved Oct 06, 2026, 04:17 PM UTC

1. investigating Oct 06, 2026, 04:20 PM UTC

   We have detected issues during the OIDC token exchange step from the Pulumi github-auth action. The team is currently investigating the issue.

2. resolved Oct 06, 2026, 04:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 11, 2026, 06:02 PM UTC· resolved Sep 12, 2026, 12:19 AM UTC

1. monitoring Sep 11, 2026, 06:02 PM UTC

   We are currently experiencing a high rate of upstream errors for Neo inference calls.

2. monitoring Sep 11, 2026, 06:41 PM UTC

   We have switched model versions and are continuing to monitor

3. monitoring Sep 12, 2026, 12:19 AM UTC

   Switching models has stabilized Neo inference calls

4. resolved Sep 12, 2026, 12:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 17, 2026, 02:05 PM UTC· resolved Aug 17, 2026, 05:06 PM UTC

1. investigating Aug 17, 2026, 02:05 PM UTC

   GitHub has reported an active, critical incident. Related functionality in the Pulumi Console is temporarily unavailable.

2. investigating Aug 17, 2026, 02:30 PM UTC

   https://www.githubstatus.com/incidents/zkxwbgr0cnmx

3. resolved Aug 17, 2026, 05:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 24, 2026, 02:56 AM UTC· resolved Jul 24, 2026, 04:24 AM UTC

1. identified Jul 24, 2026, 02:56 AM UTC

   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.

2. identified Jul 24, 2026, 03:08 AM UTC

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

3. monitoring Jul 24, 2026, 04:20 AM UTC

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

4. resolved Jul 24, 2026, 04:24 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 08, 2026, 07:09 PM UTC· resolved Jul 08, 2026, 07:45 PM UTC

1. investigating Jul 08, 2026, 07:09 PM UTC

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

2. monitoring Jul 08, 2026, 07:36 PM UTC

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

3. monitoring Jul 08, 2026, 07:37 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jul 08, 2026, 07:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 22, 2026, 06:06 PM UTC· resolved Jun 22, 2026, 07:52 PM UTC

1. investigating Jun 22, 2026, 06:06 PM UTC

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

2. investigating Jun 22, 2026, 06:30 PM UTC

   We are continuing to investigate this issue.

3. identified Jun 22, 2026, 07:14 PM UTC

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

4. monitoring Jun 22, 2026, 07:44 PM UTC

   A fix has been rolled out and we are monitoring results

5. monitoring Jun 22, 2026, 07:45 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Jun 22, 2026, 07:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 11, 2026, 10:20 PM UTC· resolved Jun 12, 2026, 12:17 AM UTC

1. investigating Jun 11, 2026, 10:20 PM UTC

   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.

2. identified Jun 11, 2026, 10:56 PM UTC

   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.

3. monitoring Jun 12, 2026, 12:02 AM UTC

   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.

4. resolved Jun 12, 2026, 12:17 AM UTC

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

Read the full incident report →

Started May 12, 2026, 09:05 PM UTC· resolved May 12, 2026, 11:14 PM UTC

1. investigating May 12, 2026, 10:50 PM UTC

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

2. monitoring May 12, 2026, 11:03 PM UTC

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

3. resolved May 12, 2026, 11:14 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Apr 20, 2026, 10:30 AM UTC· resolved Apr 20, 2026, 10:30 AM UTC

1. resolved May 06, 2026, 07:05 PM UTC

   Some Pulumi Cloud organizations experienced elevated errors when decrypting ESC environments. A subset of environment revisions were affected, and those revisions failed to decrypt 100% of the time during the window. Overall, 3.32% of decrypt-attempt requests across Pulumi Cloud failed due to this issue. At the start of the window, we rolled out a change that prevented secret ciphertext copied from an ESC environment from being decrypted in other environments. Customers who had previously copied ciphertext between environments were affected. Users saw a message: “decryption failed. If this secret's ciphertext was copied from a different environment, copy and paste the plaintext instead.” This change was intended as a security improvement, but the customer impact was higher than expected, so the change was rolled back. The ESC team has conducted an internal postmortem to understand the misjudged customer impact, improve our responsiveness to scenarios like this, and created a plan to launch this security improvement without customer disruption.

Read the full incident report →

Started Apr 15, 2026, 09:43 AM UTC· resolved Apr 15, 2026, 02:10 PM UTC

1. investigating Apr 15, 2026, 09:43 AM UTC

   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.

2. identified Apr 15, 2026, 10:26 AM UTC

   We have started deploying a fix for this issue. We will provide an update once the deployment is complete.

3. monitoring Apr 15, 2026, 12:26 PM UTC

   The fix has been deployed and we are seeing recovery. We are continuing to monitor to confirm the issue is fully resolved.

4. resolved Apr 15, 2026, 02:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 10, 2026, 05:58 PM UTC· resolved Apr 10, 2026, 06:10 PM UTC

1. identified Apr 10, 2026, 05:58 PM UTC

   We are aware of reduced response times across Pulumi Cloud APIs. We have identified the cause and are working on a fix

2. resolved Apr 10, 2026, 06:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 06, 2026, 11:29 AM UTC· resolved Mar 06, 2026, 11:52 AM UTC

1. investigating Mar 06, 2026, 11:29 AM UTC

   We are aware of issues with machine tokens having issues opening environments as part of running previews. We are currently investigating

2. investigating Mar 06, 2026, 11:30 AM UTC

   We are continuing to investigate this issue.

3. identified Mar 06, 2026, 11:41 AM UTC

   We are working on a rollback that should resolve this incident. As this rollback is deploying, you may see error rates decrease for a time until the deploy is complete.

4. monitoring Mar 06, 2026, 11:45 AM UTC

   Rollback has deployed. We are continuing to monitor

5. resolved Mar 06, 2026, 11:52 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 03, 2026, 11:26 PM UTC· resolved Feb 03, 2026, 11:33 PM UTC

1. investigating Feb 03, 2026, 11:26 PM UTC

   We have received reports of errors when creating new Pulumi Neo tasks. We are investigating the issue.

2. resolved Feb 03, 2026, 11:33 PM UTC

   We've identified and rolled back the change that caused the issue. The incident is now resolved.

Read the full incident report →

Started Nov 18, 2025, 01:44 PM UTC· resolved Nov 18, 2025, 03:45 PM UTC

1. identified Nov 18, 2025, 01:44 PM UTC

   Cloudflare is having an outage which is impacting certain regions ability to resolve artifacts via get.pulumi.com

2. resolved Nov 18, 2025, 03:45 PM UTC

   Cloudflare has restored the impacted services.

Read the full incident report →

Started Oct 20, 2025, 03:05 PM UTC· resolved Oct 21, 2025, 03:26 AM UTC

1. identified Oct 20, 2025, 03:05 PM UTC

   These are affected by the global AWS outage

2. identified Oct 20, 2025, 03:33 PM UTC

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

3. identified Oct 20, 2025, 03:37 PM UTC

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

4. identified Oct 20, 2025, 03:43 PM UTC

   Customers in the eastern part of the United States may experience intermittent errors loading documentation and registry pages

5. identified Oct 20, 2025, 05:41 PM UTC

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

6. resolved Oct 21, 2025, 03:26 AM UTC

   All impacted areas have recovered

Read the full incident report →

Started Sep 08, 2025, 05:27 PM UTC· resolved Sep 08, 2025, 07:21 PM UTC

1. investigating Sep 08, 2025, 05:27 PM UTC

   We are currently experiencing issues with displaying some previews in Pulumi Cloud. Our team is actively investigating the problem and working toward a resolution. We will provide updates as soon as more information is available.

2. identified Sep 08, 2025, 06:00 PM UTC

   We’ve identified the root cause of the preview display issues in Pulumi Cloud and are actively rolling out a fix. Thanks for your patience — we’ll share another update once the rollout is complete.

3. resolved Sep 08, 2025, 07:21 PM UTC

   The issue affecting previews in Pulumi Cloud has been resolved. Previews are functioning normally again. Please note that affected previews during the incident window (between 11pm UTC Sept 7, 2025 and 7pm UTC Sept 8, 2025) were not recoverable and will not be available in your history.

Read the full incident report →

Started Jul 28, 2025, 04:42 PM UTC· resolved Jul 28, 2025, 04:50 PM UTC

1. investigating Jul 28, 2025, 04:42 PM UTC

   We are currently investigating a major issue with a release this morning. We are in the process of rolling this back.

2. monitoring Jul 28, 2025, 04:43 PM UTC

   We are noticing a significant drop in error rates and are continuing to monitor.

3. resolved Jul 28, 2025, 04:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 02:42 PM UTC· resolved Jun 12, 2025, 02:44 PM UTC

1. identified Jun 12, 2025, 02:42 PM UTC

   The issue has been identified and a fix is being implemented.

2. monitoring Jun 12, 2025, 02:42 PM UTC

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

3. resolved Jun 12, 2025, 02:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 11, 2025, 01:56 PM UTC· resolved Jun 11, 2025, 03:42 PM UTC

1. identified Jun 11, 2025, 01:56 PM UTC

   As part of a programmed maintenance, old stacks might not load logs or outputs. We are actively working on resolving this issue

2. monitoring Jun 11, 2025, 03:30 PM UTC

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

3. resolved Jun 11, 2025, 03:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 01, 2025, 07:03 PM UTC· resolved May 01, 2025, 08:08 PM UTC

1. identified May 01, 2025, 07:03 PM UTC

   The issue has been identified and a fix is being implemented.

2. identified May 01, 2025, 07:30 PM UTC

   A fix has been implemented and is being deployed. We are monitoring rollout, ETA of approx 30 minutes.

3. resolved May 01, 2025, 08:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 29, 2025, 06:41 PM UTC· resolved Apr 29, 2025, 07:09 PM UTC

1. identified Apr 29, 2025, 06:41 PM UTC

   The issue has been identified and a fix is being implemented.

2. monitoring Apr 29, 2025, 07:06 PM UTC

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

3. resolved Apr 29, 2025, 07:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 28, 2025, 09:45 AM UTC· resolved Mar 28, 2025, 11:29 AM UTC

1. investigating Mar 28, 2025, 09:45 AM UTC

   We are currently tracking an issue where logs for updates aren't being saved and displayed

2. identified Mar 28, 2025, 10:50 AM UTC

   A fix is being prepared.

3. resolved Mar 28, 2025, 11:29 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 04, 2025, 08:43 PM UTC· resolved Mar 04, 2025, 09:35 PM UTC

1. investigating Mar 04, 2025, 08:43 PM UTC

   We are currently investigating this issue.

2. identified Mar 04, 2025, 08:51 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Mar 04, 2025, 09:27 PM UTC

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

4. resolved Mar 04, 2025, 09:35 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 27, 2025, 05:05 PM UTC· resolved Feb 27, 2025, 07:13 PM UTC

1. identified Feb 27, 2025, 05:51 PM UTC

   [duplicate message]

2. investigating Feb 27, 2025, 05:53 PM UTC

   We are aware of an issue preventing users from viewing stack update logs in the web console.

3. identified Feb 27, 2025, 05:54 PM UTC

   We have identified a fix and are in the process of deploying it.

4. identified Feb 27, 2025, 06:41 PM UTC

   We are in the process of rolling out a secondary fix.

5. resolved Feb 27, 2025, 07:13 PM UTC

   We've applied the fix, the incident has been resolved. We will continue to monitor error reports related to this issue throughout the day.

Read the full incident report →