Pulumi had 34 outages in the last 2 years totaling 47h 56m of downtime — averaging 1.4 incidents per month.
There were 34 Pulumi outages since June 4, 2024 totaling 47h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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.
We have started deploying a fix for this issue. We will provide an update once the deployment is complete.
The fix has been deployed and we are seeing recovery. We are continuing to monitor to confirm the issue is fully resolved.
This incident has been resolved.
We are aware of reduced response times across Pulumi Cloud APIs. We have identified the cause and are working on a fix
This incident has been resolved.
We are aware of issues with machine tokens having issues opening environments as part of running previews. We are currently investigating
We are continuing to investigate this issue.
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.
Rollback has deployed. We are continuing to monitor
This incident has been resolved.
We have received reports of errors when creating new Pulumi Neo tasks. We are investigating the issue.
We've identified and rolled back the change that caused the issue. The incident is now resolved.
Cloudflare is having an outage which is impacting certain regions ability to resolve artifacts via get.pulumi.com
Cloudflare has restored the impacted services.
These are affected by the global AWS outage
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
Customers in the eastern part of the United States may experience intermittent errors loading documentation and registry pages
We are continuing to work on a fix for this issue.
All impacted areas have recovered
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.
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.
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.
We are currently investigating a major issue with a release this morning. We are in the process of rolling this back.
We are noticing a significant drop in error rates and are continuing to monitor.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
As part of a programmed maintenance, old stacks might not load logs or outputs. We are actively working on resolving this issue
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and is being deployed. We are monitoring rollout, ETA of approx 30 minutes.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently tracking an issue where logs for updates aren't being saved and displayed
A fix is being prepared.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
[duplicate message]
We are aware of an issue preventing users from viewing stack update logs in the web console.
We have identified a fix and are in the process of deploying it.
We are in the process of rolling out a secondary fix.
We've applied the fix, the incident has been resolved. We will continue to monitor error reports related to this issue throughout the day.
We are currently investigating this issue.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
A deployment went out this morning at 09:49 PST that prevented a subset of users from accessible stack pages. This change has been rolled back and impacted users should be able to access stack pages again.
We are seeing increased error rates for deployments that are building docker images that rely on dockerhub. We are investigating.
This incident has been resolved.
A fix is currently being deployed and we will monitor for continued affects.
continuing to monitor
This incident has been resolved.
Expect high latency while using Pulumi APIs and Pulumi Cloud console.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of a major outage in the Pulumi Cloud API and are rolling out a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of degraded performance with Resource Search. You may see outdated search results during this period for stacks which were recently updated.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.