outages.live
Live
PulumiIncident · 2026-10-30 19:11 UTC

Elevated error rates and intermittent failures across Pulumi Cloud

ResolvedOfficial update

This incident has been resolved. Error rates and latency have been normal since 19:24 UTC, and all systems are operating normally.

The latest update from Pulumi.

State

Resolved

Started

2 d ago

2026-10-30 19:11 UTC

Lasted

1 h 32 min

until 2026-10-30 20:43 UTC

Worst impact

Major outage

Timeline

3 updates
19:1119:3419:5720:2020:43
Major outageUpdate postedTimes in UTC

Investigating

17 min 19%

Monitoring

1 h 15 min 81%

Updates

Times in UTC

As posted by Pulumi

Resolved2026-10-30 20:43 UTC

This incident has been resolved. Error rates and latency have been normal since 19:24 UTC, and all systems are operating normally.

Monitoring2026-10-30 19:28 UTC

We were seeing elevated error rates and intermittent failures across Pulumi Cloud. A fix has been deployed and we are monitoring the service

Investigating2026-10-30 19:11 UTC

We are seeing elevated error rates and intermittent failures across Pulumi Cloud, including the Pulumi Console. We are actively investigating and working on a fix.

Affected components

2
APIConsole

Pulumi in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

6

Median duration

2 h 43 min

This incident

44% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 18 min
median 2 h 43 min
90 days agoToday

Other Pulumi incidents

All incidents

Pulumi·Bitbucket login is not available

This incident has been resolved.

Resolvedresolved 16 d ago

Pulumi·Issues with Pulumi OIDC (inbound)

This incident has been resolved.

Resolvedresolved 26 d ago

Pulumi·Neo Outage

This incident has been resolved.

Resolvedresolved 51 d ago

Pulumi·GitHub services failing

This incident has been resolved.

Resolvedresolved 76 d ago

Follow Pulumi

Your coding agent knows when Pulumi is down, and tells you when a failure is theirs, not yours. You can also get Pulumi incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "pulumi" and tell me if Pulumi has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=pulumi
Slack
/feed subscribe https://outages.cc/feed.xml?providers=pulumi

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane