Pulumi Outage History
16 incidents recorded over the last 365 days, 16 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Pulumi Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 30, 2026 | Elevated error rates and intermittent failures across Pulumi CloudThis incident has been resolved. Error rates and latency have been normal since 19:24 UTC, and all systems are operating normally. | 1h 31m | Resolved |
| Oct 16, 2026 | Bitbucket login is not availableThis incident has been resolved. | 2h 42m | Resolved |
| Oct 6, 2026 | Issues with Pulumi OIDC (inbound)This incident has been resolved. | -2 min | Resolved |
| Sep 11, 2026 | Neo OutageThis incident has been resolved. | 6h 17m | Resolved |
| Aug 17, 2026 | GitHub services failingThis incident has been resolved. | 3h 1m | Resolved |
| Jul 24, 2026 | Some Team Access Token operations failingThis incident has been resolved. | 1h 28m | Resolved |
| Jul 8, 2026 | Degraded performance for Pulumi Cloud loginThis incident has been resolved. | 35 min | Resolved |
| Jun 22, 2026 | Degraded performance on Pulumi APIsThis incident has been resolved. | 1h 46m | Resolved |
| Jun 11, 2026 | Bitbucket authentication failures affecting sign-in and Bitbucket-backed accountsThe incident has now been resolved and the service is operating normally for all customers. | 1h 57m | Resolved |
| May 12, 2026 | Elevated API error rates and latencyThe incident has been resolved. | 2h 9m | Resolved |
| May 6, 2026 | Elevated errors when decrypting ESC environmentsSome 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… | -23555 min | Resolved |
| Apr 15, 2026 | Bitbucket Authentication UnavailableThis incident has been resolved. | 4h 27m | Resolved |
| Apr 10, 2026 | Slowed API response timesThis incident has been resolved. | 11 min | Resolved |
| Mar 6, 2026 | Machine tokens unable to open referenced environments when running stack previews.This incident has been resolved. | 22 min | Resolved |
| Feb 3, 2026 | Errors when creating new Pulumi Neo tasksWe've identified and rolled back the change that caused the issue. The incident is now resolved. | 6 min | Resolved |
| Nov 18, 2025 | get.pulumi.com unreachableCloudflare has restored the impacted services. | 2h 1m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Pulumi incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Pulumi Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Pulumi acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Pulumi outage in this window ran 6h 17m, against a mean recovery of 2h 2m. If you depend on Pulumi in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.