Live

INC20000351

0

Snowflake Virtual Warehouses in AWS Europe (Ireland) had intermittent delays in virtual warehouse resume operations, which caused queued or delayed queries. Snowflake implemented a fix and monitored the environment. Snowflake reports that this incident is resolved. The impact lasted about 7 hours.

State

Resolved

Started

Lasted

9 h 3 min

Worst impact

Degraded

Timeline

7 updates
13:0515:2117:3719:5322:09
DegradedUpdate postedTimes in UTC

Identified

2 h 10 min 24%

Monitoring

6 h 54 min 76%

Updates

Times in UTC

As posted by Snowflake

Resolved

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 region may have experienced intermittent delays on virtual warehouse resume operations, which could have caused queued or delayed queries for workloads running on affected warehouses. Impact start time: 08:07 UTC November 16, 2026 Impact end time: 15:00 UTC November 16, 2026 Preliminary root cause: Our investigation identified that a recent configuration change intended to improve resource allocation on associated virtual warehouse infrastructure resulted in customer impact. Specifically, this change inadvertently increased the volume of the requests being handled by the affected infrastructure, until the point of resource exhaustion. Further, we identified that this issu

Monitoring

Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: As our teams have executed their recovery actions, customers hosted in the specified region should no longer be experiencing intermittently delayed virtual warehouse resume operations, causing queued or delayed queries for workloads running on affected warehouses. Impact start time: 08:07 UTC November 16, 2026 Impact end time: 15:00 UTC November 16, 2026 Preliminary root cause: An update intended to improve the allocation of infrastructure resources to virtual warehouse resulted in unexpected behavior and has been rolled back.

Monitoring

Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: As our teams have executed their recovery actions. Customers hosted in the specified region should no longer be experiencing intermittently delayed virtual warehouse resume operations, causing queued or delayed queries for workloads running on affected warehouses. Impact start time: 08:07 UTC November 16, 2026 Impact end time: 15:00 UTC November 16, 2026 Preliminary root cause: An update intended to improve the allocation of infrastructure resources to virtual warehouse resulted in unexpected behavior and has been rolled back.

Identified

Current status: We're continuing to implement our recovery actions to restore service. We'll provide another update within 1 hour. Customer experience: As our teams execute their recovery actions, customers hosted in the specified region may continue to experience intermittently delayed virtual warehouse resume operations, causing queued or delayed queries for workloads running on affected warehouses. We expect these delays to reduce as our actions progress and take effect. 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. Impact start time: 08:07 UTC November 16, 2026

Monitoring

Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: As our teams have executed their recovery actions. Customers hosted in the specified region should no longer be experiencing intermittently delayed virtual warehouse resume operations, causing queued or delayed queries for workloads running on affected warehouses. Impact start time: 08:07 UTC November 16, 2026 Impact end time: 15:00 UTC November 16, 2026 Preliminary root cause: An update intended to improve the allocation of infrastructure resources to virtual warehouse resulted in unexpected behavior and has been rolled back.

Identified

Current status: We're continuing to implement our recovery actions to restore service. We'll provide another update within 1 hour. Customer experience: As our teams execute their recovery actions, customers hosted in the specified region may continue to experience intermittently delayed virtual warehouse resume operations, causing queued or delayed queries for workloads running on affected warehouses. We expect these delays to reduce as our actions progress and take effect. 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. Impact start time: 08:07 UTC November 16, 2026

Identified

Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: As our teams begin executing recovery actions, customers hosted in the specified regions may continue to experience intermittently delayed virtual warehouse resume operations, causing queued or delayed queries for workloads running on affected warehouses. 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. Impact start time: 08:07 UTC November 16, 2026

Affected components

2
Virtual WarehousesAWS - Europe (Ireland) - Virtual Warehouses

Snowflake in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

27

Days with an incident

83

Median duration

1 h 58 min

This incident

4.6× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

77 days
median 1 h 58 min
90 days agoToday

Other Snowflake incidents

All incidents

Snowflake·INC20000350

Snowflake Data Loading and Unloading tasks in AWS US West (Oregon) had delays. Snowflake reports that this incident is resolved. It lasted 42 minutes.

Resolved

Snowflake·INC20000347

Snowflake reported degraded performance for Databases, Tables, and Views in Azure Australia East (New South Wales). Customers in that region had delays when resuming virtual warehouses, and queries took longer than usual. Snowflake resolved the incident; the impact lasted 72 minutes.

Resolved

Snowflake·INC20000337

Snowflake reports degraded service for Virtual Warehouses and Snowpark Container Services in Azure West US 2 (Washington). Customers had delays when resuming or scaling up warehouses, and intermittent delays when creating or scaling up Snowpark Container Services compute pools. The incident is resolved and it lasted 84 minutes.

Resolved

Snowflake·INC20000336

Snowflake reports degraded Virtual Warehouses and Snowpark Container Services in AWS US West (Oregon) and AWS US West Commercial Gov (Oregon). Snowflake resolved the incident. The impact lasted from 22:50 UTC on November 06, 2026 to 00:31 UTC on November 07, 2026.

Resolved

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

Resolved

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=snowflake
Slack
/feed subscribe https://outages.live/feed.xml?providers=snowflake

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane