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)
The latest update from Snowflake.
State
Resolved
Started
11 d ago
2026-10-21 18:26 UTC
Lasted
5 h 3 min
until 2026-10-21 23:29 UTC
Worst impact
Major outage
Timeline
10 updatesInvestigating
2 h 38 min 52%
Identified
1 h 18 min 26%
Monitoring
1 h 7 min 22%
Updates
Times in UTCAs posted by Snowflake
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)
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 been unable to access or use multiple Snowflake services and features. Affected users may have been unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also have failed to run or may not start as expected. Impact start time: 17:50 UTC October 21, 2026 Impact end time: 21:25 UTC October 21, 2026 Preliminary root cause: A configuration change applied to the cloud services layer in the specified region interacted with existing settings in a way that caused a significant number of instances to be taken out of service. This led to ca
Current status: Our monitoring indicates that the previously affected services have returned to normal operation. We'll continue to monitor the environment until we're confident all services are functioning properly. 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 been unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also have failed to run or may not start as expected. Impact start time: 18:00 UTC October 21, 2026 Impact end time: 21:25 UTC October 21, 2026 Preliminary root cause: A configuration change applied to the cloud services layer in the specified region interacted with existing settings in a way that caused a significant number of instances to be taken out of service. This led to cascading failures across sign-in, query execution
Current status: Services in the specified region are recovering, and our monitoring indicates that most core services, including sign-in, Snowsight, query execution, and data ingestion, are returning to normal operation. We're continuing to monitor to confirm full recovery across all services. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. Impact start time: 18:00 UTC October 21, 2026 Preliminary root cause: A recent configuration change in the affected region caused service infrastructure to stop processing requests, resulting in a service disruption.
Current status: We're continuing to monitor the affected region, and we're seeing early signs of recovery. Affected services are recovering gradually, and we're working to confirm full restoration. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. ETA: Our current estimate is that service will be restored within 1 hour. Impact start time: 18:00 UTC October 21, 2026
Current status: We've completed a configuration change to address the issue that we suspect caused the impact while we continue to investigate other potential factors. We're also monitoring the region for signs of recovery and are continuing to work on restoring full service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, customers using replication may review their failover procedures and determine whether failover is warranted based on the impact to their organization.
Current status: We've identified a configuration issue within the core systems which process requests in the impacted region that we suspect is contributing to impact, and we're further investigating this issue to confirm our findings and identify a method to restore service. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also fail to run or may not start as expected. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, customers using replication may review their failover procedures and determine whether failover is warranted based on the impact to their organization. Impact start time: 18:00 UTC October 21, 2
Current status: We're continuing to investigate the core systems that process requests in the impacted region to assist us in isolating the root cause of this issue. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, or ingest files using Snowpipe. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, customers using replication may review their failover procedures and determine whether failover is warranted based on the impact to their organization.
Current status: We're investigating the core systems that process requests in the impacted region to assist us in isolating the source of the impact and identifying a path to resolution. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, execute queries, or ingest files using Snowpipe.
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use multiple core Snowflake services and features. Affected users may be unable to sign in, use Snowsight, or ingest files using Snowpipe.
Affected components
6Snowflake in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
73
Median duration
1 h 56 min
This incident
2.6× the median
Other Snowflake incidents
All incidentsSnowflake·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·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)
Snowflake·INC20000294
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
Snowflake·INC20000290
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.
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