Is Pulumi status down? User reports show no current problems with Pulumi status

Is Pulumi Down Right Now?

Short answer: Pulumi has two layers that fail in different ways: your cloud accounts and the state backend. Most Pulumi down reports are really a stuck update or a locked stack.

This page tracks the Pulumi status through reports from platform and DevOps teams. It covers the Pulumi CLI, self-managed state, and Pulumi Cloud, where a shared outage can block many stacks.

Below are the faults that halt deployments most often, from pending operations to passphrase errors, plus the safe fixes. Never edit state files by hand until you have a backup export.

Is Pulumi Down for Me or Everyone?

So is Pulumi down for me, or is Pulumi Cloud down for everyone? Run pulumi whoami and a plain stack list before any heavy command.

If the CLI cannot reach the backend at all and reports here spike, the service side is at fault. If reads work but one stack refuses updates, that stack holds a lock or a damaged snapshot.

Local backend users skip the cloud question entirely. For them, a Pulumi outage means their file store, their credentials, or their cloud provider API failed.

Why Does Pulumi Say There Are Pending Operations?

An interrupted update leaves resources marked as pending. Pulumi then refuses new updates on that stack, because it cannot be sure what the cloud really holds.

This follows a cancelled run, a crashed laptop, or a lost network mid-deploy. The pending marker is a safety brake, not corruption, and it has a clean way out.

Run pulumi refresh to compare state with the real cloud, or export the stack, clear the pending entries, and import it back. The refresh path is safer for most teams.

Why Does pulumi up Fail With a Snapshot Integrity Error?

Snapshot integrity errors mean the state file broke its own rules. A resource may point at a parent or provider that no longer exists in the file.

Hand-edited state, a bad merge of backend files, or a plugin crash during writes can all cause it. This is why state backups matter before any manual surgery.

Export the stack first. Many cases heal with pulumi stack export, a careful edit, and pulumi stack import. If the file is deeply damaged, restore the last known-good state version from your backend history.

Common Pulumi Problems and Fixes

Pending Operations Block Every Update

Run pulumi refresh and let it settle state against the real cloud. If refresh cannot clear them, export the stack, remove the pending operations entries, and import. Always keep the untouched export as your way back.

Wrong Passphrase for Stack Secrets

Secrets are sealed with your stack passphrase, and Pulumi Cloud stacks use their own setup. Set PULUMI_CONFIG_PASSPHRASE for scripts, and confirm you picked the right stack. A truly lost passphrase means re-encrypting secrets from source values.

Stack Is Locked by Another Update

A running or crashed update holds the lock. Wait for the real run to end first. If the run died, cancel it with pulumi cancel, which releases the lock so new updates can start.

Login Token Expired for Pulumi Cloud

Tokens age out and CI tokens get rotated. Run pulumi login again locally, or issue a fresh access token for automation. If whoami fails for the whole team, check the service reports before rotating everything.

A Resource Fails Halfway Through Create

Cloud APIs reject requests for quotas, name clashes, or missing rights. Read the provider error in the update output; it names the account limit or permission. Fix that in the cloud, then run the update again. Developers shipping realtime apps also check Pusher when live updates stop reaching users after a deploy.