Azure - West US 2 (Washington): INC0157956

What to do

• Check whether you use Snowflake Virtual Warehouses in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 15h 42m it lasted.

  Anything that failed between 2026-05-29 06:47 UTC and 2026-05-29 22:28 UTC may need a replay.

• Subscribe to Snowflake's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=snowflake works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snowflake 7

1. investigatingMay 29, 2026, 6:47 AM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Incident start time: 05:15 UTC May 29, 2026

   provider

2. identifiedMay 29, 2026, 7:45 AM UTC

   Current status: We've identified an issue with a third-party cloud platform, and we're coordinating with the provider to develop and implement a fix to restore service. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 05:15 UTC May 29, 2026

   provider

3. identifiedMay 29, 2026, 8:45 AM UTC

   Current status: We're seeing services recover as our third-party provider continues its efforts to restore its environment, and we're actively monitoring recovery as these actions progress. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 05:15 UTC May 29, 2026

   provider

4. monitoringMay 29, 2026, 9:36 AM UTC

   Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Incident start time: 05:15 UTC May 29, 2026 Incident end time: 07:24 UTC May 29, 2026 Preliminary root cause: A third-party cloud platform experienced a power outage in its data center, affecting the underlying infrastructure and causing increased latency and intermittent connectivity for some resources Snowflake depends on.

   provider

5. monitoringMay 29, 2026, 12:40 PM UTC

   Current status: Although the broadest impact has been remediated by our third-party cloud platform, customers may still experience performance latency or degradation as our service provider continues to work on full restoration. As an ETA from them is unavailable, our service provider has advised these customers to enact failover to other regions where possible. We will continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the specified regions may have been unable to start, resume, or manage virtual warehouses. Virtual warehouses may have appeared stuck in the associated state. At this time, there should be no further impact on virtual warehouses. Incident start time: 05:15 UTC May 29, 2026 Incident end time: 07:24 UTC May 29, 2026 Preliminary root cause: A third-party cloud platform experienced a power outage in its data center, affecting the underlying infrastructure and causing increased latency and intermittent connectivity for some resources Snowflake depends on.

   provider

6. resolvedMay 29, 2026, 10:28 PM UTC

   Current status: Our third-party cloud platform has confirmed that the impact to their infrastructure has been mitigated, and we've observed that the impact to Snowflake customers has been resolved. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have been unable to start, resume, or manage virtual warehouses. Virtual warehouses may have appeared to be stuck in the associated state. The majority of the impact occurred during the period of 05:15 UTC to 07:24 UTC on May 29, 2026. Incident start time: 04:24 UTC May 29, 2026 Incident end time: 07:24 UTC May 29, 2026 Preliminary root cause: A third-party cloud platform experienced a power outage in its data center, which affected the underlying infrastructure and caused increased latency and intermittent connectivity for some resources on which Snowflake depends. A root cause analysis (RCA) document will be published within ten business days.

   provider

7. postmortemJun 12, 2026, 9:38 AM UTC

   Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0157956](https://community.snowflake.com/s/article/INC0157956)

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.