Skip to content

Pulumi status · pulumi.com

Is Pulumi Down Today?

Infrastructure as code platform.

Report an issue

No, Pulumi is not down

pulumi.com is currently up. Our monitoring probes can reach pulumi.com and complete a check without errors. Latest response time was 24 ms. The latest automated check was run 2026-08-14 18:23 UTC from primary location.

Current status
Operational

Currently up for 2h 36m

Last check
Checked every 10 minutes

Latest 2026-08-14 18:23 UTC · Primary location

Last 24 hours
100%

0 incidents, 0m down

Official status
Operational
Our check
Operational
Active incident
None
Last outage
None recorded
Response time
24 ms
User reports
Normal

None today

Pulumi live status

19 of 19 operational

  • APIOperational
  • AWS ec2-us-west-2Operational
  • AWS elb-us-west-2Operational
  • AWS rds-us-west-2Operational
  • AWS s3-us-west-2Operational
  • ConsoleOperational
  • DeploymentsOperational
  • DockerOperational
  • DocsOperational
  • ESCOperational
  • GitHubOperational
  • GitLabOperational
  • InsightsOperational
  • MailchimpOperational
  • Pulumi NeoOperational
  • RegistryOperational
  • Stripe APIOperational
  • Stripe JSOperational
  • Third Party ServicesOperational

Current incident

No active incidents reported by the official Pulumi status source.

Response time

Latest 107 ms

Loading response-time chart…

Uptime

Availability from independent checks, with recorded incidents and downtime in each window.

Today

100%

0 incidents, 0m down

Last 7 days

100%

0 incidents, 0m down

Last 30 days

100%

0 incidents, 0m down

Last 365 days

100%

0 incidents, 0m down

Latest Pulumi incidents

Recorded outages with duration and start time.

No outage history stored yet.

How this status checker works

Who's Down Today monitors Pulumi independently of the company that runs it. We send reachability checks from our primary location every 10 minutes and record response time, HTTP errors, and timeouts.

When Pulumi publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.

This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.

Frequently asked questions

Is Pulumi down right now?

No. No, Pulumi is not down. Who's Down Today shows Pulumi as operational based on the latest official signals and independent checks. If you still cannot reach pulumi.com, the issue may be local to your connection, DNS, VPN, browser, or device.

Is Pulumi down for everyone or just me?

Who's Down Today currently shows Pulumi as operational from our monitoring location, which means pulumi.com is responding normally to our checks. If you are still having trouble, try another browser, device, or network, and check DNS or VPN settings.

What should I do if pulumi.com is up but I still cannot access it?

Try opening pulumi.com from another browser, device, or network (for example a mobile hotspot). You can also disable a VPN, flush local DNS, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed Pulumi outage.

How does Who's Down Today check if Pulumi is down?

We combine independent HTTP reachability checks with public status information where it exists. When Pulumi publishes a public status page or incident feed, that official signal is treated as a strong input. A single failed probe is treated as a possible transient or regional failure, not an automatic global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.

What does a Pulumi outage mean?

An outage on this page means recorded incidents or failed checks indicated that Pulumi was not responding normally. That does not always mean every user was affected. Some outages are regional, some affect only certain features, and some appear as errors or slow responses instead of a full failure.

Can this page tell me the root cause of a Pulumi outage?

Not exactly. We can show when an issue started, how long it lasted, the public incident title, and symptoms such as timeouts or slow response times. We do not have access to Pulumi's internal systems, so we cannot identify a private root cause such as a failed deploy or database incident unless the provider publishes it.

How do I report an issue with Pulumi?

Use the report form on this page if Pulumi looks down for you. Reports are anonymous, rate-limited, and used only as supporting evidence alongside official sources and independent checks.