Pulumi logo

Is Pulumi Down?

SaaSLive status, outages, and incident history

No. Pulumi is up right now.

Every monitored Pulumi system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Pulumi breaks

Pulumi is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Pulumi status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Pulumi Component Status

The main Pulumi systems on this page. All 18 are operational right now.

18operational
API
Operational
Console
Operational
Deployments
Operational

15 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Docs, ESC, Insights, Pulumi Neo, Registry, Stripe JS, Third Party Services » AWS ec2-us-west-2, Third Party Services » AWS elb-us-west-2, Third Party Services » AWS rds-us-west-2, Third Party Services » AWS s3-us-west-2, Third Party Services » Docker, Third Party Services » GitHub, and 3 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Pulumi Outages & Incidents

Incident history from the official Pulumi status page, including resolution updates.

Neo OutageResolved Sep 11, 2026 · 6h 17mResolved

This incident has been resolved. --- [2026-09-11T17:19:21.761-07:00] (monitoring) Switching models has stabilized Neo inference calls --- [2026-09-11T11:41:21.492-07:00] (monitoring) We have switched model versions and are continuing to monitor --- [2026-09-11T11:02:01.670-07:00] (monitoring) We are currently experiencing a high rate of upstream errors for Neo inference calls.

GitHub services failingResolved Aug 17, 2026 · 3h 1mResolved

This incident has been resolved. --- [2026-08-17T07:30:21.108-07:00] (investigating) https://www.githubstatus.com/incidents/zkxwbgr0cnmx --- [2026-08-17T07:05:19.644-07:00] (investigating) GitHub has reported an active, critical incident. Related functionality in the Pulumi Console is temporarily unavailable.

Some Team Access Token operations failingResolved Jul 24, 2026 · 1h 28mResolved

This incident has been resolved. --- [2026-07-23T21:20:44.996-07:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-07-23T20:08:46.854-07:00] (identified) We are continuing to work on a fix for this issue. --- [2026-07-23T19:56:50.338-07:00] (identified) We are investigating an issue where some Team Access Tokens are unable to authenticate to the Pulumi Cloud API, which may result in failed deployments or API errors. We have identified the cause and a fix is being deployed. We will provide an update once the fix is live.

Pulumi Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Pulumi incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 4 days with incidentsSep 25

Live Pulumi Outage Reports

Problems reported by engineers using Pulumi. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Pulumi problems reported yet.

Something wrong with Pulumi on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Pulumi

Pulumi exposes 19 monitored components on its status page at status.pulumi.com — API, AWS ec2-us-west-2 and Console among them. Follow Pulumi downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Pulumi uptime at 100.00%. Response times, incident history, and SLA tracking for Pulumi are available on the PulsAPI dashboard.

Pulumi Status FAQ

Is Pulumi down right now?

The verdict at the top of this page comes from the latest poll of the official Pulumi status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Pulumi is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Pulumi recovers.

How do I check Pulumi uptime history?

PulsAPI tracks Pulumi uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Pulumi changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Pulumi outages?

PulsAPI reads the official Pulumi status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Pulumi components?

Yes. PulsAPI monitors 18 individual Pulumi components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Pulumi goes down?

Yes. Create a free account and subscribe to Pulumi: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Pulumi to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Pulumi problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Pulumi?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Pulumi plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Pulumi with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services