INC20000336
Snowflake reported delays or failures when resuming or scaling up Virtual Warehouses and Snowpark Container Services in AWS US West (Oregon), including the Commercial Gov region. Serverless tasks and compute pools also had delays. Snowflake resolved the incident. The impact lasted from 22:50 UTC on November 06, 2026 to 00:31 UTC on November 07, 2026.
State
Resolved
Started
Lasted
3 h 20 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
1 h 3 min 32%
Identified
1 h 6 min 33%
Monitoring
1 h 11 min 35%
Updates
Times in UTCAs posted by Snowflake
Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. 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 experienced delays or intermittent failures when resuming or scaling up virtual warehouses. Serverless tasks may have taken longer than expected to begin. Customers may also have been unable to start new Snowpark Container Services services, including notebooks, and compute pools may have remained stuck when starting or scaling up. Existing warehouses and services that were already running may have been unaffected. Impact start time: 22:50 UTC November 06, 2026 Impact end time: 00:31 UTC November 07, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that affected
Current status: Our third-party cloud platform provider has resolved the underlying issue, and we're monitoring the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or scaling up virtual warehouses. Serverless tasks may have taken longer than expected to begin. Customers may also have been unable to start new Snowpark Container Services services, including notebooks, and compute pools may have remained stuck when starting or scaling up. Existing warehouses and services that were already running may have been unaffected. Impact start time: 22:50 UTC November 06, 2026 Impact end time: 00:31 UTC November 07, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that affected resource provisioning.
Current status: Our third-party cloud platform provider has resolved the underlying issue, and we're monitoring the environment until we're confident all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may have experienced delays or intermittent failures when resuming or scaling up virtual warehouses. Serverless tasks may have taken longer than expected to begin. Customers may also have been unable to start new Snowpark Container Services services, including notebooks, and compute pools may have remained stuck when starting or scaling up. Existing warehouses and services that were already running may have been unaffected. Impact start time: 22:50 UTC November 06, 2026 Impact end time: 01:00 UTC November 07, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that affected resource provisioning.
Current status: We've determined that an issue with a third-party cloud platform provider is affecting our ability to provision compute resources in the specified regions. We're retaining existing virtual warehouse resources in the specified regions to reduce the impact, and we're working with the provider to restore service. We'll provide another update within 2 hours. Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or scaling up virtual warehouses. Existing warehouses that are already running may be unaffected. Additionally, serverless tasks may take longer than expected to begin. Customers may also be unable to start new Snowpark Container Services services, including notebooks, and compute pools may remain in a resizing state when scaling up. 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. Preliminary root caus
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 region may experience delays when resuming or scaling up virtual warehouses. Existing warehouses that are already running may be unaffected. Workaround: There are currently no available workarounds for this issue. Preliminary root cause: A third-party cloud platform provider is experiencing an issue that is affecting resource provisioning, which is delaying virtual warehouse resumes.
Affected components
6Snowflake in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
78
Median duration
1 h 57 min
This incident
1.7× the median
Other Snowflake incidents
All incidentsSnowflake·INC20000337
Snowflake reports delays when customers resume or scale up Virtual Warehouses in Azure West US 2 (Washington). Snowpark Container Services in the same region had intermittent delays when customers created or scaled up compute pools. Snowflake resolved the incident, which lasted about 1 hour 24 minutes.
Snowflake·INC20000321
Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. 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 access or manage their Openflow runtimes deployed in Snowpark Container Services. Runtimes may have shown as active, but opening the Openflow canvas may have failed with errors saying the runtime was unavailable or that the connection was refused. Impact start time: 17:34 UTC October 30, 2026 Impact end time: 22:55 UTC October 30, 2026 Preliminary root cause: A subset of infrastructure responsible for secure communication with Openflow runtimes experienced a certificate issue, which prevented connections to the affected Openflow runtimes A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business day
Snowflake·INC20000319
Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. 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 experienced delays or intermittent failures when resuming or managing virtual warehouses, with the majority of impact occurring between 03:00 and 08:40 UTC October 29, 2026. Existing warehouses that were already running may have been unaffected. Additionally, serverless tasks may have taken longer than expected to begin. Impact start time: 03:00 UTC October 29, 2026 Impact end time: 08:40 UTC October 29, 2026 Preliminary root cause: A third-party cloud platform provider experienced an issue that slowed responses to resource provisioning requests, which delayed virtual warehouse resumes. A root cause
Snowflake·INC20000301
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/INC20000301](https://community.snowflake.com/s/article/INC20000301)
Snowflake·INC20000299
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/INC20000299](https://community.snowflake.com/s/article/INC20000299)
Follow Snowflake
Your coding agent knows when Snowflake is down, and tells you when a failure is theirs, not yours. You can also get Snowflake incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "snowflake" and tell me if Snowflake has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=snowflake/feed subscribe https://outages.cc/feed.xml?providers=snowflakeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane