outages.live
Live

Pulumi

Pulumi is operational

Checked 42 s ago Operational

History

90 days agoToday

Incidents in 90 days

5

Days with an incident

6

Median duration

2 h 43 min

Longest incident

6 h 18 min

Components

18
API Operational
90 days ago3 days with an incidentToday
Console Operational
90 days ago2 days with an incidentToday
Deployments Operational
90 days agoNo incidentsToday
ESC Operational
90 days ago1 day with an incidentToday
Insights Operational
90 days agoNo incidentsToday
Pulumi Neo Operational
90 days ago2 days with an incidentToday
Registry Operational
90 days agoNo incidentsToday
Docs Operational
90 days agoNo incidentsToday
Stripe JS Operational
90 days agoNo incidentsToday

Third Party Services

AWS ec2-us-west-2 Operational
90 days agoNo incidentsToday
AWS elb-us-west-2 Operational
90 days agoNo incidentsToday
AWS s3-us-west-2 Operational
90 days agoNo incidentsToday
AWS rds-us-west-2 Operational
90 days agoNo incidentsToday
GitHub Operational
90 days ago1 day with an incidentToday
Stripe API Operational
90 days agoNo incidentsToday
GitLab Operational
90 days agoNo incidentsToday
Docker Operational
90 days agoNo incidentsToday
Mailchimp Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 30, 2026

Duration1 h 32 min19:11 to 20:43Elevated error rates and intermittent failures across Pulumi CloudMajor outage

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

Oct 16, 2026

Duration2 h 43 min10:48 to 13:30Bitbucket login is not availablePartial outage

This incident has been resolved.

Oct 6, 2026

Duration42 min15:35 to 16:17Issues with Pulumi OIDC (inbound)Partial outage

This incident has been resolved.

Sep 11, 2026

Duration6 h 18 min18:02 to 00:19Neo OutageMajor outage

This incident has been resolved.

Aug 17, 2026

Duration3 h 1 min14:05 to 17:06GitHub services failingNotice

This incident has been resolved.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane