Pulumi の障害履歴

1. 2026年8月17日 14:05 UTCinvestigating

   GitHubは、アクティブで重要なインシデントを報告しました。 Pulumi Consoleの関連機能は一時的に利用できません.

2. 2026年8月17日 14:30 UTCinvestigating

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

3. 2026年8月17日 17:06 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月24日 2:56 UTCidentified

   チームアクセストークンがPulumi Cloud APIに認証できない問題について調査しています。これにより、デプロイやAPIエラーが失敗する可能性があります。 原因を特定し、修正が展開されています。 修正が始まると更新を行います.

2. 2026年7月24日 3:08 UTCidentified

   この問題の修正には引き続き取り組んでいます。

3. 2026年7月24日 4:20 UTCmonitoring

   修正を実装し、結果を監視しています.

4. 2026年7月24日 4:24 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月8日 19:09 UTCinvestigating

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

2. 2026年7月8日 19:36 UTCmonitoring

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

3. 2026年7月8日 19:37 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026年7月8日 19:45 UTCresolved

   This incident has been resolved.

1. 2026年6月22日 18:06 UTCinvestigating

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

2. 2026年6月22日 18:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026年6月22日 19:14 UTCidentified

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

4. 2026年6月22日 19:44 UTCmonitoring

   A fix has been rolled out and we are monitoring results

5. 2026年6月22日 19:45 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2026年6月22日 19:52 UTCresolved

   This incident has been resolved.

1. 2026年6月11日 22:20 UTCinvestigating

   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. 2026年6月11日 22:56 UTCidentified

   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. 2026年6月12日 0:02 UTCmonitoring

   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. 2026年6月12日 0:17 UTCresolved

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

1. 2026年5月12日 22:50 UTCinvestigating

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

2. 2026年5月12日 23:03 UTCmonitoring

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

3. 2026年5月12日 23:14 UTCresolved

   The incident has been resolved.

1. 2026年5月6日 19:05 UTCresolved

   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.

1. 2026年4月15日 9:43 UTCinvestigating

   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. 2026年4月15日 10:26 UTCidentified

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

3. 2026年4月15日 12:26 UTCmonitoring

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

4. 2026年4月15日 14:10 UTCresolved

   This incident has been resolved.

1. 2026年4月10日 17:58 UTCidentified

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

2. 2026年4月10日 18:10 UTCresolved

   This incident has been resolved.

1. 2026年3月6日 11:29 UTCinvestigating

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

2. 2026年3月6日 11:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026年3月6日 11:41 UTCidentified

   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. 2026年3月6日 11:45 UTCmonitoring

   Rollback has deployed. We are continuing to monitor

5. 2026年3月6日 11:52 UTCresolved

   This incident has been resolved.

1. 2026年2月3日 23:26 UTCinvestigating

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

2. 2026年2月3日 23:33 UTCresolved

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

1. 2025年11月18日 13:44 UTCidentified

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

2. 2025年11月18日 15:45 UTCresolved

   Cloudflare has restored the impacted services.

1. 2025年10月20日 15:05 UTCidentified

   These are affected by the global AWS outage

2. 2025年10月20日 15:43 UTCidentified

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

3. 2025年10月20日 17:41 UTCidentified

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

4. 2025年10月21日 3:26 UTCresolved

   All impacted areas have recovered

1. 2025年9月8日 17:27 UTCinvestigating

   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. 2025年9月8日 18:00 UTCidentified

   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. 2025年9月8日 19:21 UTCresolved

   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.

1. 2025年7月28日 16:42 UTCinvestigating

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

2. 2025年7月28日 16:43 UTCmonitoring

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

3. 2025年7月28日 16:50 UTCresolved

   This incident has been resolved.

1. 2025年6月12日 14:42 UTCidentified

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

2. 2025年6月12日 14:42 UTCmonitoring

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

3. 2025年6月12日 14:44 UTCresolved

   This incident has been resolved.

1. 2025年6月11日 13:56 UTCidentified

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

2. 2025年6月11日 15:30 UTCmonitoring

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

3. 2025年6月11日 15:42 UTCresolved

   This incident has been resolved.

1. 2025年5月1日 19:03 UTCidentified

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

2. 2025年5月1日 19:30 UTCidentified

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

3. 2025年5月1日 20:08 UTCresolved

   This incident has been resolved.

1. 2025年4月29日 18:41 UTCidentified

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

2. 2025年4月29日 19:06 UTCmonitoring

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

3. 2025年4月29日 19:09 UTCresolved

   This incident has been resolved.

1. 2025年3月28日 9:45 UTCinvestigating

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

2. 2025年3月28日 10:50 UTCidentified

   A fix is being prepared.

3. 2025年3月28日 11:29 UTCresolved

   This incident has been resolved.