Skip to main content
Pulumi Cloud

We identified many endpoints returning 301 causing infinite redirection for certain stacks.

Degraded Lasted 2m · started · Pulumi Cloud's page

Level
confirmed
Worst impact
Degraded
Components
API
Down Index
12of 100

What to do

  • Check whether you use Pulumi Cloud API. 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 2m it lasted.

    Anything that failed between 2025-06-12 14:42 UTC and 2025-06-12 14:44 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

  1. identified

    The issue has been identified and a fix is being implemented.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. 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-f18641dde2

Is Pulumi Cloud still down?

No, this incident was resolved 2025-06-12 14:44 UTC. For Pulumi Cloud's live state, see https://down.guide/pulumi.

How long did it last?

2m, from 2025-06-12 14:42 UTC to 2025-06-12 14:44 UTC, by the times Pulumi Cloud posted.

What was affected?

Pulumi Cloud named API.

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.