- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API, Console
- Down Index
- 32of 100
What to do
Check whether you use Pulumi Cloud API, Console. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 43m it lasted.
Anything that failed between 2026-10-16 10:48 UTC and 2026-10-16 13:30 UTC may need a replay.Subscribe to Pulumi Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=pulumi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Pulumi Cloud 3
- identified
We know about a problem with Bitbucket login for Pulumi Cloud. The problem started on 15 October 2026 at approximately 16:51 UTC. You cannot log in to Pulumi Cloud with your Bitbucket account at this time. After you log in at Bitbucket, Pulumi Cloud shows the message "Internal Server Error". Other login methods or Bitbucket repository integrations and deployments are not affected.
provider
- monitoring
A fix has been deployed and we're monitoring the results.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-5495776271
Is Pulumi Cloud still down?
No, this incident was resolved 2026-10-16 13:30 UTC. For Pulumi Cloud's live state, see https://down.guide/pulumi.
How long did it last?
2h 43m, from 2026-10-16 10:48 UTC to 2026-10-16 13:30 UTC, by the times Pulumi Cloud posted.
What was affected?
Pulumi Cloud named API, Console.
What caused it?
Pulumi Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Pulumi Cloud's official status page, https://status.pulumi.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.