Pulumi change history

Pulumi reported a major Bitbucket login outage affecting API and Console, with failures beginning approximately 2026-10-15 16:51 UTC. The recorded incident ran from 2026-10-16 10:48 UTC to 2026-10-16 13:30 UTC (2 h 42 min); a fix was deployed, and other login methods, Bitbucket repository integrations and deployments were unaffected.

Pulumi reported a major incident affecting inbound OIDC, with API and ESC listed as affected components. It started at 2026-10-06 15:35 UTC and was resolved at 2026-10-06 16:17 UTC, lasting 42 min; no cause or specific fix was stated.

Pulumi Neo experienced a critical outage with a high rate of upstream errors for inference calls, starting 2026-09-11 18:02 UTC and lasting 6 h 17 min. Pulumi switched model versions, which stabilized inference calls, and resolved the incident at 2026-09-12 00:19 UTC.

Pulumi reported a major outage preventing Bitbucket-authenticated users from signing in to Pulumi Cloud or using its API, including CLI operations; other authentication methods were unaffected. It started at 2026-04-15 09:43 UTC and was resolved at 2026-04-15 14:10 UTC, lasting 4 h 27 min. A fix was deployed at 04-15 12:26 UTC, with recovery observed.

Creating new Pulumi Neo tasks produced errors during a major-impact incident starting 2026-02-03 23:26 UTC and resolved at 2026-02-03 23:33 UTC, lasting 6 min. Pulumi identified and rolled back the change that caused the issue.

Pulumi reported a major AWS outage affecting Deployments, Docs, and Registry, with intermittent documentation and registry loading errors for customers in the eastern United States. It started at 2025-10-20 15:05 UTC and resolved at 2025-10-21 03:26 UTC, lasting 12 h 20 min; Pulumi attributed the disruption to the global AWS outage and confirmed all impacted areas recovered.

Pulumi reported a critical API outage starting 2025-07-28 16:42 UTC, lasting 8 min and resolved at 2025-07-28 16:50 UTC. Pulumi reported a major issue with that morning’s release and began rolling it back; error rates dropped significantly by 07-28 16:43 UTC.

Pulumi reported a major API incident causing a high error rate running program updates, starting at 2025-04-29 18:41 UTC and resolved at 2025-04-29 19:09 UTC (27 min). A fix was implemented by 19:06 UTC; no cause was stated.

Pulumi reported a major API incident in which update logs weren't being saved or displayed, starting at 2025-03-28 09:45 UTC. A fix was being prepared at 03-28 10:50 UTC; the incident was resolved at 2025-03-28 11:29 UTC after 1 h 44 min.

Pulumi Deployments experienced increased error rates for deployments building docker images that rely on dockerhub, with impact rated major. The incident started at 2024-12-12 22:03 UTC and was resolved at 2024-12-12 23:57 UTC, lasting 1 h 53 min; no cause or fix was stated.

Pulumi deployments were failing in a major-impact incident starting 2024-12-12 20:58 UTC, lasting 21 min and resolved at 2024-12-12 21:20 UTC. Pulumi reported deploying a fix and monitoring; no cause was stated.

Pulumi reported a critical outage affecting the Pulumi Cloud API and Deployments, starting at 2024-11-18 19:40 UTC and resolved at 2024-11-18 19:59 UTC; the computed duration was 18 min. A fix was implemented by 19:50 UTC, followed by monitoring.

Pulumi Copilot experienced a partial outage with major impact due to connectivity issues with Microsoft Azure. It started at 2024-07-22 23:57 UTC and was resolved at 2024-07-23 00:30 UTC, lasting 33 min.

Pulumi reported a major Deployments outage starting 2024-06-20 22:33 UTC: deployments using DockerHub-hosted images, including the default pulumi/pulumi image, failed due to a DockerHub outage. The incident was resolved at 2024-06-20 22:42 UTC, with a reported duration of 8 min.

Pulumi reported a major outage affecting API, Console, and Deployments starting 2024-03-20 00:43 UTC. It was resolved at 2024-03-20 00:47 UTC, with a computed duration of 3 min; no cause or specific fix was stated.

Pulumi reported a major incident in which resource search timed out, affecting API, Console, Insights, and Search. It started at 2024-01-05 20:00 UTC and was resolved at 2024-01-05 21:37 UTC, lasting 1 h 36 min. Pulumi said it identified the issue and search should be functioning normally; no specific cause or fix was provided.