Pulumi

Affected: API, Console

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-16 10:48 UTC

   We know about a problem with Bitbucket login for Pulumi Cloud. The problem started on 15 October 2026 at approximately 16:51 UTC. You cannot log in to Pulumi Cloud with your Bitbucket account at this time. After you log in at Bitbucket, Pulumi Cloud shows the message "Internal...

2. monitoring 2026-10-16 11:54 UTC

   A fix has been deployed and we're monitoring the results.

3. resolved 2026-10-16 13:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, ESC

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 15:35 UTC

   We have detected issues with Pulumi OIDC (inbound). The team is currently investigating the issue.

2. resolved 2026-10-06 16:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Pulumi Neo

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-11 18:02 UTC

   We are currently experiencing a high rate of upstream errors for Neo inference calls.

2. monitoring 2026-09-11 18:41 UTC

   We have switched model versions and are continuing to monitor

3. monitoring 2026-09-12 00:19 UTC

   Switching models has stabilized Neo inference calls

4. resolved 2026-09-12 00:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: GitHub

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Incident with GitHub.com.

1. investigating 2026-08-17 14:05 UTC

   GitHub has reported an active, critical incident. Related functionality in the Pulumi Console is temporarily unavailable.

2. investigating 2026-08-17 14:30 UTC

   https://www.githubstatus.com/incidents/zkxwbgr0cnmx

3. resolved 2026-08-17 17:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Deployments

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-24 02:56 UTC

   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.

2. identified 2026-07-24 03:08 UTC

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

3. monitoring 2026-07-24 04:20 UTC

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

4. resolved 2026-07-24 04:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-08 19:09 UTC

   We are aware of an issue affecting login access to Pulumi Cloud and are investigating.

2. monitoring 2026-07-08 19:36 UTC

   We have taken mitigation steps and are seeing signs of recovery. We are continuing to monitor the situation.

3. monitoring 2026-07-08 19:37 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-07-08 19:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Deployments, Insights

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-22 18:06 UTC

   We are aware of degraded performance on Pulumi APIs and are actively investigating the issue.

2. investigating 2026-06-22 18:30 UTC

   We are continuing to investigate this issue.

3. identified 2026-06-22 19:14 UTC

   We have identified a likely cause and are working on steps to address the issue.

4. monitoring 2026-06-22 19:44 UTC

   A fix has been rolled out and we are monitoring results

5. monitoring 2026-06-22 19:45 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-06-22 19:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-06-11 22:20 UTC

   We are investigating an issue affecting customers who sign in to Pulumi Cloud with a Bitbucket identity or use Bitbucket-connected accounts. Beginning at approximately 06:00 UTC on June 11, requests to refresh Bitbucket authentication tokens began failing. Affected users may...

2. identified 2026-06-11 22:56 UTC

   Atlassian has acknowledged an incident affecting Bitbucket OAuth login, which is the cause of the Bitbucket sign-in and authentication failures affecting Pulumi Cloud. Their incident is being tracked at: https://bitbucket.status.atlassian.com/incidents/h51sr145gsmx The issue is...

3. monitoring 2026-06-12 00:02 UTC

   Atlassian has deployed a fix for their incident affecting Bitbucket OAuth login, and we have confirmed that Bitbucket authentication requests from Pulumi Cloud are succeeding again. Error rates have returned to normal levels and sign-in with Bitbucket is working.

4. resolved 2026-06-12 00:17 UTC

   The incident has now been resolved and the service is operating normally for all customers.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-12 21:05 UTC

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

2. monitoring 2026-05-12 23:03 UTC

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

3. resolved 2026-05-12 23:14 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-04-20 10:30 UTC

   Some Pulumi Cloud organizations experienced elevated errors when decrypting ESC environments. A subset of environment revisions were affected, and those revisions failed to decrypt 100% of the time during the window. Overall, 3.32% of decrypt-attempt requests across Pulumi Cloud...

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-15 09:43 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...

2. identified 2026-04-15 10:26 UTC

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

3. monitoring 2026-04-15 12:26 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 2026-04-15 14:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console, Deployments, Insights

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-10 17:58 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 2026-04-10 18:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Deployments

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-06 11:29 UTC

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

2. investigating 2026-03-06 11:30 UTC

   We are continuing to investigate this issue.

3. identified 2026-03-06 11:41 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 2026-03-06 11:45 UTC

   Rollback has deployed. We are continuing to monitor

5. resolved 2026-03-06 11:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Pulumi Neo

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-03 23:26 UTC

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

2. resolved 2026-02-03 23:33 UTC

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

Excerpts are shortened. Read the full incident on Pulumi's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-11-18 13:44 UTC

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

2. resolved 2025-11-18 15:45 UTC

   Cloudflare has restored the impacted services.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments, Registry, Docs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 15:05 UTC

   These are affected by the global AWS outage

2. identified 2025-10-20 15:33 UTC

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

3. identified 2025-10-20 15:37 UTC

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

4. identified 2025-10-20 15:43 UTC

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

5. identified 2025-10-20 17:41 UTC

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

6. resolved 2025-10-21 03:26 UTC

   All impacted areas have recovered

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Console

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-08 17:27 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 2025-09-08 18:00 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 2025-09-08 19:21 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...

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-28 16:42 UTC

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

2. monitoring 2025-07-28 16:43 UTC

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

3. resolved 2025-07-28 16:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-06-12 14:42 UTC

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

2. monitoring 2025-06-12 14:42 UTC

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

3. resolved 2025-06-12 14:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-06-11 13:56 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 2025-06-11 15:30 UTC

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

3. resolved 2025-06-11 15:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-01 19:03 UTC

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

2. identified 2025-05-01 19:30 UTC

   A fix has been implemented and is being deployed. We are monitoring rollout, ETA of approx 30 minutes.

3. resolved 2025-05-01 20:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-04-29 18:41 UTC

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

2. monitoring 2025-04-29 19:06 UTC

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

3. resolved 2025-04-29 19:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-28 09:45 UTC

   We are currently tracking an issue where logs for updates aren't being saved and displayed

2. identified 2025-03-28 10:50 UTC

   A fix is being prepared.

3. resolved 2025-03-28 11:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-04 20:43 UTC

   We are currently investigating this issue.

2. identified 2025-03-04 20:51 UTC

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

3. monitoring 2025-03-04 21:27 UTC

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

4. resolved 2025-03-04 21:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-02-27 17:05 UTC

   [duplicate message]

2. investigating 2025-02-27 17:06 UTC

   We are aware of an issue preventing users from viewing stack update logs in the web console.

3. identified 2025-02-27 17:47 UTC

   We have identified a fix and are in the process of deploying it.

4. identified 2025-02-27 18:41 UTC

   We are in the process of rolling out a secondary fix.

5. resolved 2025-02-27 19:13 UTC

   We've applied the fix, the incident has been resolved. We will continue to monitor error reports related to this issue throughout the day.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-04 21:09 UTC

   We are currently investigating this issue.

2. investigating 2025-02-04 21:09 UTC

   We are currently investigating this issue.

3. monitoring 2025-02-04 22:00 UTC

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

4. resolved 2025-02-05 00:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-24 12:43 UTC

   We are currently investigating this issue.

2. identified 2025-01-24 14:41 UTC

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

3. resolved 2025-01-24 15:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-01-09 18:49 UTC

   A deployment went out this morning at 09:49 PST that prevented a subset of users from accessible stack pages. This change has been rolled back and impacted users should be able to access stack pages again.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-12-12 22:03 UTC

   We are seeing increased error rates for deployments that are building docker images that rely on dockerhub. We are investigating.

2. resolved 2024-12-12 23:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2024-12-12 20:58 UTC

   A fix is currently being deployed and we will monitor for continued affects.

2. monitoring 2024-12-12 21:02 UTC

   continuing to monitor

3. resolved 2024-12-12 21:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-28 06:32 UTC

   Expect high latency while using Pulumi APIs and Pulumi Cloud console.

2. investigating 2024-11-28 07:32 UTC

   We are continuing to investigate this issue.

3. monitoring 2024-11-28 07:33 UTC

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

4. resolved 2024-11-28 07:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Deployments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-18 19:40 UTC

   We are aware of a major outage in the Pulumi Cloud API and are rolling out a fix.

2. monitoring 2024-11-18 19:50 UTC

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

3. resolved 2024-11-18 19:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Insights

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-05 20:32 UTC

   We are currently investigating reports of degraded performance with Resource Search. You may see outdated search results during this period for stacks which were recently updated.

2. investigating 2024-11-05 20:33 UTC

   We are continuing to investigate this issue.

3. investigating 2024-11-05 21:07 UTC

   We are continuing to investigate this issue.

4. identified 2024-11-05 22:31 UTC

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

5. monitoring 2024-11-06 00:16 UTC

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

6. resolved 2024-11-06 03:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-04 18:54 UTC

   Error rate is elevated but we've implemented a fix and it should be resolving within the hour

2. resolved 2024-11-04 19:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Console

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-31 18:25 UTC

   We are currently investigating issues accessing https://app.pulumi.com, especially when authenticating or re-authenticating.

2. resolved 2024-10-31 19:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console, Deployments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-17 16:25 UTC

   We are currently investigating this issue.

2. monitoring 2024-10-17 18:23 UTC

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

3. resolved 2024-10-17 18:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console, Deployments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-10-17 00:50 UTC

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

2. monitoring 2024-10-17 01:13 UTC

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

3. resolved 2024-10-17 02:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-09-03 18:30 UTC

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

2. monitoring 2024-09-03 18:34 UTC

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

3. resolved 2024-09-03 18:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Console

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-07-30 20:20 UTC

   We are currently investigating an issue with email notifications from the Pulumi service.

2. resolved 2024-07-30 20:48 UTC

   We identified an upstream problem with our email service provider, which has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Insights

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-07-29 21:09 UTC

   We are currently investigating this issue.

2. identified 2024-07-29 21:38 UTC

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

3. monitoring 2024-07-29 21:42 UTC

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

4. resolved 2024-07-29 21:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2024-07-22 23:57 UTC

   We are currently experiencing a partial outage with Pulumi Copilot due to connectivity issues with Microsoft Azure. The team is actively investigating.

2. resolved 2024-07-23 00:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-06-20 22:33 UTC

   Deployments running on images hosted on DockerHub are failing due to a DockerHub outage. This includes the default pulumi/pulumi image.

2. resolved 2024-06-20 22:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Insights

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-06-07 00:20 UTC

   We are currently investigating this issue.

2. resolved 2024-06-07 03:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2024-06-04 21:30 UTC

   We're experiencing an elevated level of ESC API errors and are currently looking into the issue.

2. resolved 2024-06-04 22:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-04-08 19:10 UTC

   We are seeing elevated failures in Pulumi Deployments related to a failure to pull Docker images. We have identified the issue and are working on a fix.

2. identified 2024-04-08 21:42 UTC

   We are continuing to see intermittent failures in Pulumi Deployments related to a failure to pull Docker images. We are in the process of rolling out a fix that should correct the issue.

3. resolved 2024-04-08 23:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console, Deployments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-20 00:43 UTC

   We are currently working on resolving this issue

2. resolved 2024-03-20 00:47 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Console

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-01-20 19:11 UTC

   We have identified a UI issue in ESC that can lead to data loss and we are releasing a fix.

2. resolved 2024-01-20 20:34 UTC

   We have reverted this feature and this is working as expected now.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Insights

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-05 20:00 UTC

   We are currently investigating an incident where resource search is timing out

2. investigating 2024-01-05 20:02 UTC

   We are continuing to investigate this issue.

3. investigating 2024-01-05 20:03 UTC

   We are continuing to investigate this issue.

4. resolved 2024-01-05 21:37 UTC

   We identified the issue and search should be functioning normally now.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: Deployments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-11-30 22:16 UTC

   We are currently investigating an incident where a subset of deployments are stuck in the running state.

2. identified 2023-11-30 22:46 UTC

   We have identified the root cause of the issue and are working on a remediation.

3. resolved 2023-11-30 23:59 UTC

   All deployments should be functioning as normal.

Excerpts are shortened. Read the full incident on Pulumi's status page.

Affected: API, Console, Deployments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-11-09 03:53 UTC

   We are currently investigating this issue.

2. investigating 2023-11-09 04:41 UTC

   We are continuing to investigate this issue.

3. resolved 2023-11-09 04:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pulumi's status page.