Pulumi Outage History

Pulumi is up right now

Pulumi had 12 outages in the last 2 years totaling 25h 29m of downtime — averaging 0.5 incidents per month.

There were 12 Pulumi outages since June 11, 2025 totaling 25h 29m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pulumi.com

Minor May 12, 2026

Elevated API error rates and latency

Detected by Pingoru
May 12, 2026, 09:05 PM UTC
Resolved
May 12, 2026, 11:14 PM UTC
Duration
2h 9m
Affected: API
Timeline · 3 updates
  1. investigating May 12, 2026, 10:50 PM UTC

    Investigating elevated API error rates and response times, particularly with ESC endpoints

  2. monitoring May 12, 2026, 11:03 PM UTC

    A fix has been deployed and error rates and response times have recovered. We are continuing to monitor.

  3. resolved May 12, 2026, 11:14 PM UTC

    The incident has been resolved.

Read the full incident report →

Major April 15, 2026

Bitbucket Authentication Unavailable

Detected by Pingoru
Apr 15, 2026, 09:43 AM UTC
Resolved
Apr 15, 2026, 02:10 PM UTC
Duration
4h 27m
Affected: APIConsole
Timeline · 4 updates
  1. investigating Apr 15, 2026, 09:43 AM UTC

    Users authenticating with Bitbucket are currently unable to sign in to Pulumi Cloud or use the Pulumi Cloud API. This affects all operations that rely on Bitbucket authentication, including CLI usage and API calls. Other authentication methods are not affected. We have identified the cause of the issue and are actively working on a fix. We will provide an update once the fix has been deployed.

  2. identified Apr 15, 2026, 10:26 AM UTC

    We have started deploying a fix for this issue. We will provide an update once the deployment is complete.

  3. monitoring Apr 15, 2026, 12:26 PM UTC

    The fix has been deployed and we are seeing recovery. We are continuing to monitor to confirm the issue is fully resolved.

  4. resolved Apr 15, 2026, 02:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 10, 2026

Slowed API response times

Detected by Pingoru
Apr 10, 2026, 05:58 PM UTC
Resolved
Apr 10, 2026, 06:10 PM UTC
Duration
11m
Affected: APIConsoleDeploymentsSearch
Timeline · 2 updates
  1. identified Apr 10, 2026, 05:58 PM UTC

    We are aware of reduced response times across Pulumi Cloud APIs. We have identified the cause and are working on a fix

  2. resolved Apr 10, 2026, 06:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 6, 2026

Machine tokens unable to open referenced environments when running stack previews.

Detected by Pingoru
Mar 06, 2026, 11:29 AM UTC
Resolved
Mar 06, 2026, 11:52 AM UTC
Duration
22m
Affected: APIDeployments
Timeline · 5 updates
  1. investigating Mar 06, 2026, 11:29 AM UTC

    We are aware of issues with machine tokens having issues opening environments as part of running previews. We are currently investigating

  2. investigating Mar 06, 2026, 11:30 AM UTC

    We are continuing to investigate this issue.

  3. identified Mar 06, 2026, 11:41 AM UTC

    We are working on a rollback that should resolve this incident. As this rollback is deploying, you may see error rates decrease for a time until the deploy is complete.

  4. monitoring Mar 06, 2026, 11:45 AM UTC

    Rollback has deployed. We are continuing to monitor

  5. resolved Mar 06, 2026, 11:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 3, 2026

Errors when creating new Pulumi Neo tasks

Detected by Pingoru
Feb 03, 2026, 11:26 PM UTC
Resolved
Feb 03, 2026, 11:33 PM UTC
Duration
6m
Affected: Pulumi Neo
Timeline · 2 updates
  1. investigating Feb 03, 2026, 11:26 PM UTC

    We have received reports of errors when creating new Pulumi Neo tasks. We are investigating the issue.

  2. resolved Feb 03, 2026, 11:33 PM UTC

    We've identified and rolled back the change that caused the issue. The incident is now resolved.

Read the full incident report →

Notice November 18, 2025

get.pulumi.com unreachable

Detected by Pingoru
Nov 18, 2025, 01:44 PM UTC
Resolved
Nov 18, 2025, 03:45 PM UTC
Duration
2h 1m
Timeline · 2 updates
  1. identified Nov 18, 2025, 01:44 PM UTC

    Cloudflare is having an outage which is impacting certain regions ability to resolve artifacts via get.pulumi.com

  2. resolved Nov 18, 2025, 03:45 PM UTC

    Cloudflare has restored the impacted services.

Read the full incident report →

Major October 20, 2025

AWS outage

Detected by Pingoru
Oct 20, 2025, 03:05 PM UTC
Resolved
Oct 21, 2025, 03:26 AM UTC
Duration
12h 20m
Affected: DeploymentsRegistryDocs
Timeline · 6 updates
  1. identified Oct 20, 2025, 03:05 PM UTC

    These are affected by the global AWS outage

  2. identified Oct 20, 2025, 03:33 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Oct 20, 2025, 03:37 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Oct 20, 2025, 03:43 PM UTC

    Customers in the eastern part of the United States may experience intermittent errors loading documentation and registry pages

  5. identified Oct 20, 2025, 05:41 PM UTC

    We are continuing to work on a fix for this issue.

  6. resolved Oct 21, 2025, 03:26 AM UTC

    All impacted areas have recovered

Read the full incident report →

Minor September 8, 2025

Issue displaying some previews in Pulumi Cloud

Detected by Pingoru
Sep 08, 2025, 05:27 PM UTC
Resolved
Sep 08, 2025, 07:21 PM UTC
Duration
1h 54m
Affected: Console
Timeline · 3 updates
  1. investigating Sep 08, 2025, 05:27 PM UTC

    We are currently experiencing issues with displaying some previews in Pulumi Cloud. Our team is actively investigating the problem and working toward a resolution. We will provide updates as soon as more information is available.

  2. identified Sep 08, 2025, 06:00 PM UTC

    We’ve identified the root cause of the preview display issues in Pulumi Cloud and are actively rolling out a fix. Thanks for your patience — we’ll share another update once the rollout is complete.

  3. resolved Sep 08, 2025, 07:21 PM UTC

    The issue affecting previews in Pulumi Cloud has been resolved. Previews are functioning normally again. Please note that affected previews during the incident window (between 11pm UTC Sept 7, 2025 and 7pm UTC Sept 8, 2025) were not recoverable and will not be available in your history.

Read the full incident report →

Critical July 28, 2025

Major outage

Detected by Pingoru
Jul 28, 2025, 04:42 PM UTC
Resolved
Jul 28, 2025, 04:50 PM UTC
Duration
8m
Affected: API
Timeline · 3 updates
  1. investigating Jul 28, 2025, 04:42 PM UTC

    We are currently investigating a major issue with a release this morning. We are in the process of rolling this back.

  2. monitoring Jul 28, 2025, 04:43 PM UTC

    We are noticing a significant drop in error rates and are continuing to monitor.

  3. resolved Jul 28, 2025, 04:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 12, 2025

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

Detected by Pingoru
Jun 12, 2025, 02:42 PM UTC
Resolved
Jun 12, 2025, 02:44 PM UTC
Duration
2m
Affected: API
Timeline · 3 updates
  1. identified Jun 12, 2025, 02:42 PM UTC

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

  2. monitoring Jun 12, 2025, 02:42 PM UTC

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

  3. resolved Jun 12, 2025, 02:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2025

Old stacks not loading logs and outputs

Detected by Pingoru
Jun 11, 2025, 01:56 PM UTC
Resolved
Jun 11, 2025, 03:42 PM UTC
Duration
1h 45m
Affected: API
Timeline · 3 updates
  1. identified Jun 11, 2025, 01:56 PM UTC

    As part of a programmed maintenance, old stacks might not load logs or outputs. We are actively working on resolving this issue

  2. monitoring Jun 11, 2025, 03:30 PM UTC

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

  3. resolved Jun 11, 2025, 03:42 PM UTC

    This incident has been resolved.

Read the full incident report →