outages.live
Live

Snowflake

Snowflake is reporting degraded

Checked 3 min ago Degraded

Partially Degraded Service

INC20000150

Snowflake reports degraded service for Virtual Warehouses and Snowpark Container Services in GCP - US Central 1 (Iowa), and for these components in general. Snowflake has identified the problem. Virtual warehouse performance is stable, and Snowpark Container Services shows improvement. New or resumed capacity may stay affected, so starting or resuming Notebooks, compute pools, or OpenFlow runtimes can fail or time out.

Degradedupdated 3 d ago

History

90 days agoToday

Incidents in 90 days

26

Days with an incident

74

Median duration

1 h 54 min

Longest incident

24 h 4 min

Components

688

AWS - US East (N. Virginia)

Databases, Tables, and Views Operational
90 days ago2 days with an incidentToday
Virtual Warehouses Operational
90 days ago2 days with an incidentToday
Data Loading and Unloading Operational
90 days ago2 days with an incidentToday
Applications Operational
90 days ago2 days with an incidentToday
Snowpark Container Services Operational
90 days ago2 days with an incidentToday
Security and Privacy Features Operational
90 days agoNo incidentsToday
AI and ML Operational
90 days ago4 days with an incidentToday
Organization and Account Management Operational
90 days ago1 day with an incidentToday
Listings and Collaboration Operational
90 days agoNo incidentsToday
Alerts and Notifications Operational
90 days ago1 day with an incidentToday
Developer Tools Operational
90 days agoNo incidentsToday
Business Continuity Operational
90 days ago1 day with an incidentToday
Snowflake Postgres Operational
90 days agoNo incidentsToday

Azure - East US 2 (Virginia)

Databases, Tables, and Views Operational
90 days agoNo incidentsToday
Virtual Warehouses Operational
90 days ago2 days with an incidentToday
Data Loading and Unloading Operational
90 days agoNo incidentsToday
Applications Operational
90 days ago1 day with an incidentToday
Snowpark Container Services Operational
90 days ago2 days with an incidentToday
Security and Privacy Features Operational
90 days ago1 day with an incidentToday
AI and ML Operational
90 days ago1 day with an incidentToday
Organization and Account Management Operational
90 days agoNo incidentsToday
Listings and Collaboration Operational
90 days agoNo incidentsToday
Alerts and Notifications Operational
90 days agoNo incidentsToday
Developer Tools Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 30, 2026

Duration3 h 26 min20:38 to 00:04INC20000321Degraded

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

Oct 29, 2026

Duration21 h 28 min04:29 to 01:57INC20000319Degraded

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

Oct 21, 2026

Duration5 h 3 min18:26 to 23:29INC20000301Major outage

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)

Duration51 min07:45 to 08:36INC20000299Degraded

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)

Oct 20, 2026

Duration8 h 52 min06:34 to 15:26INC20000294Major outage

Current status: We've monitored the environment and confirmed that service has been 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 been unable to access or use multiple Snowflake services and features. Affected users may have experienced errors or failures when connecting to Snowsight, managing data, loading data, or using applications. Incident start time: 06:01 UTC October 20, 2026 Incident end time: 14:00 UTC October 20, 2026 Preliminary root cause: A power event at our third-party cloud platform provider made one of the availability zones in the specified region unavailable. Snowflake infrastructure running in that zone, including components that support Snowsight, became unreachable, and requests that depended on it failed until workloads moved to the remaining availability zones. To limit further impact, we s

Oct 19, 2026

Duration44 min00:26 to 01:11INC20000290Degraded

Current status: We've monitored the environment and confirmed that service has been 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 who connect to Snowflake using private connectivity may have experienced intermittent failures when establishing new connections. Affected users may have seen some connection attempts fail while other attempts succeeded. Customers that are already connected were not impacted. Incident start time: 23:07 UTC October 18, 2026 Incident end time: 23:37 UTC October 18, 2026 Preliminary root cause: A third-party cloud platform experienced a network connectivity issue, which caused private connectivity connection failures in the affected region. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

Oct 16, 2026

Duration29 min01:14 to 01:43INC20000287Major outage

[https://community.snowflake.com/s/article/INC20000287](https://community.snowflake.com/s/article/INC20000287)

Oct 14, 2026

Duration24 h 4 min21:47 to 21:51INC20000277Degraded

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/INC20000277](https://community.snowflake.com/s/article/INC20000277)

Oct 6, 2026

Duration1 h 13 min14:44 to 15:57INC20000263Partial outage

[https://community.snowflake.com/s/article/INC20000263](https://community.snowflake.com/s/article/INC20000263)

Sep 27, 2026

Duration1 h 1 min02:15 to 03:16INC20000239Major outage

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/INC20000239](https://community.snowflake.com/s/article/INC20000239)

Sep 25, 2026

Duration1 h 20 min23:00 to 00:20INC20000237Major outage

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/INC20000237](https://community.snowflake.com/s/article/INC20000237)

Sep 14, 2026

Duration1 h 21 min04:48 to 06:09INC20000217Partial outage

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 affected deployments may have experienced performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. Incident start time: 22:22 UTC September 13, 2026 Incident end time: 05:18 UTC September 14, 2026 Preliminary root cause: An update intended to improve authentication handling caused a subset of single sign-on (SSO) sign-in attempts across multiple regions to fail or loop, preventing affected users from logging in to Snowflake. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

Sep 11, 2026

Duration6 h 1 min07:18 to 13:19INC20000213Major outage

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/INC20000213](https://community.snowflake.com/s/article/INC20000213)

Affected components

1
  • Virtual WarehousesGCP - US Central 1 (Iowa)Degraded

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane