Snowflake
majorresolved

Azure - West US 2 (Washington): INC0157956

May 29, 2026, 06:47 AM → May 29, 2026, 10:28 PM · 15h 41m

Affected components

Virtual Warehouses

Update timeline

  1. postmortemJun 12, 2026, 09:38 AM

    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)

  2. resolvedMay 29, 2026, 10:28 PM

    <b>Current status:</b> 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. <b>Customer experience:</b> Customers hosted in the specified regions may have been unable to start, resume, or manage virtual warehouses. Virtual warehou

  3. monitoringMay 29, 2026, 12:40 PM

    <b>Current status:</b> 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. <b>Customer experience

  4. monitoringMay 29, 2026, 09:36 AM

    <b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>Incident start

  5. identifiedMay 29, 2026, 08:45 AM

    <b>Current status:</b> 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. <b>Customer experience:</b> 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 unaffe

  6. identifiedMay 29, 2026, 07:45 AM

    <b>Current status:</b> 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. <b>Customer experience:</b> 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. <b>ETA:</b> An

  7. investigatingMay 29, 2026, 06:47 AM

    <b>Current status:</b> We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes. <b>Customer experience:</b> 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. <b>Incident start time:</b> 05:15 UTC May 29, 2026