Pulumi incident

Elevated errors when decrypting ESC environments

Notice Resolved View vendor source →

Pulumi experienced a notice incident on May 6, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 07:05 PM UTC
Resolved
Apr 20, 2026, 10:30 AM UTC
Duration
Detected by Pingoru
May 06, 2026, 07:05 PM UTC

Update timeline

  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.

Looking to track Pulumi downtime and outages?

Pingoru polls Pulumi's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Pulumi reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Pulumi alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Pulumi for free

5 free monitors · No credit card required