Snowflake Incident History

1. resolvedNov 7 · 04:44 UTC

   Current status: Our third-party cloud platform provider resolved the issue, and we've monitored the environment to confirm 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 experienced delays when resuming or scaling up warehouses, and may have experienced intermittent delays when creating or scaling up Snowpark Container Services compute pools. Impact start time: 01:50 UTC November 07, 2026 Impact end time: 03:14 UTC November 07, 2026 Preliminary root cause: Our third-party cloud platform provider experienced an issue that affected resource provisioning. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

Reported by Snowflake on their status page.

1. resolvedNov 7 · 02:52 UTC

   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 resource provisioning. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

Reported by Snowflake on their status page.

1. resolvedOct 31 · 00:04 UTC

   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 days.

Reported by Snowflake on their status page.

1. resolvedOct 30 · 01:57 UTC

   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 analysis (RCA) will be conducted and a summary will be made available within 10 business days.

Reported by Snowflake on their status page.

1. postmortemOct 28 · 21:13 UTC

   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

Reported by Snowflake on their status page.

1. ResolvedOct 21 · 23:29 UTC

   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, 2026Impact end time: 21:25 UTC October 21, 2026Preliminary 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, data ingestion, and other dependent services.A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

Reported by Snowflake on their status page.

1. postmortemOct 28 · 13:47 UTC

   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

Reported by Snowflake on their status page.

1. ResolvedOct 21 · 08:36 UTC

   Current status: We've monitored the environment and confirmed 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 intermittent failures when using Snowsight. Symptoms may have included slow page loads or brief errors when accessing Snowsight. Retrying the operation may have succeeded in most cases, as the issue was intermittent in nature.Impact start time: 06:18 UTC October 21, 2026Impact end time: 07:06 UTC October 21, 2026Preliminary root cause: A subset of infrastructure responsible for routing incoming traffic in the affected region became unavailable, resulting in intermittent failures when loading Snowsight.A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

Reported by Snowflake on their status page.

1. postmortemNov 3 · 16:23 UTC

   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/INC20000294

Reported by Snowflake on their status page.

1. ResolvedOct 20 · 15:26 UTC

   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, 2026Incident end time: 14:00 UTC October 20, 2026Preliminary 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 stopped placing new workloads in the affected zone and paused routine software updates in the region until the provider restored the zone.A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

Reported by Snowflake on their status page.

1. resolvedOct 19 · 01:11 UTC

   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.

Reported by Snowflake on their status page.

1. ResolvedOct 19 · 01:11 UTC

   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, 2026Incident end time: 23:37 UTC October 18, 2026Preliminary 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.

Reported by Snowflake on their status page.

1. postmortemOct 23 · 16:47 UTC

   https://community.snowflake.com/s/article/INC20000287

Reported by Snowflake on their status page.

1. ResolvedOct 16 · 01:43 UTC

   Current status: We've monitored the environment and confirmed 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 intermittent delays when loading Snowsight or running queries, and some queries may have failed.Workaround: There were no available workarounds for this issue.Incident start time: 23:50 UTC October 15, 2026Incident end time: 00:40 UTC October 16, 2026Preliminary root cause: A routine software update caused a large number of background setup operations to run at the same time, which exhausted the resources of a subset of infrastructure responsible for processing queries in the affected region, resulting in intermittent delays and query failures.A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

Reported by Snowflake on their status page.

1. postmortemOct 23 · 20:17 UTC

   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

Reported by Snowflake on their status page.

1. UpdateOct 15 · 04:57 UTC

   Current status: The infrastructure restarts in the affected region are complete, and our monitoring indicates that the service is continuing to recover. Tasks that were scheduled before the restarts and haven't yet run afterward may be marked as failed the next time they run, even though they actually run successfully. We're preparing a fix to restore the task graph run history and resolve the remaining impact. We'll provide another update within 15 hours.Customer experience: Prior to the mitigation: Customers hosted in the affected region may have experienced intermittent issues with scheduled or manual tasks. Most tasks completed as expected, but some may have been marked as failed even though they ran successfully. A small number of tasks may have remained in a pending state or failed to start. Affected users may have seen an error message, such as "Unexpected exception during task dispatch."After the mitigation: Tasks that haven't run since the infrastructure restarts may be marked as failed with an internal error message the next time they run, even though their queries run successfully. This may happen up to one additional time per task. Customers may also see incomplete task graph run history. Specifically:- When customers open or refresh the Task Graphs tab on the Tasks page in Snowsight (Transformation » Tasks), or the Run History tab for individual tasks, they may not see task runs from before 10:58 UTC October 13, 2026. Some task runs from after that time may not appear.- The INFORMATION_SCHEMA.COMPLETE_TASK_GRAPHS function may not include some recently completed runs.- The INFORMATION_SCHEMA.CURRENT_TASK_GRAPHS function may show extra rows for previously scheduled runs that are no longer running.- The SNOWFLAKE.ACCOUNT_USAGE.COMPLETE_TASK_GRAPHS view will continue to show history from before 10:58 UTC October 13, 2026, but some runs after that time may not appear.ETA: An ETA is not yet available. We'll provide one as soon as possible.Workaround: Before rerunning a task that was reported as failed, we recommend using the QUERY_HISTORY function or the SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY view to confirm whether the queries run by the task actually succeeded or failed. If the queries failed, we recommend rerunning the task to bypass the impact.Incident start time: 10:58 UTC October 13, 2026Preliminary root cause: A subset of infrastructure in the region experienced an issue that left the task metadata inconsistent. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start.

Reported by Snowflake on their status page.

1. postmortemOct 21 · 23:02 UTC

   https://community.snowflake.com/s/article/INC20000263

Reported by Snowflake on their status page.

1. identifiedNov 5 · 23:06 UTC

   Current status: Virtual warehouse performance remains stable. For Snowpark Container Services, additional capacity has not yet become available, later than the end-of-October timeframe previously communicated. We now expect the capacity to become available by the end of next week. We will validate service readiness once it arrives and share a more substantive update. Until then, workloads that require new or resumed capacity may remain affected. We will provide another update within seven days, or sooner if there is a significant change. Customer experience: Customers using Snowpark Container Services may still experience delays, timeouts, or failures when starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. Existing workloads generally continue to run normally; the remaining risk is concentrated in workloads that require new or resumed capacity. ETA: We expect additional capacity to be available by November 13, 2026. Workaround: Customers running Notebooks may continue using a warehouse-based runtime where feasible. There is no general workaround for Snowpark Container Services compute-pool capacity issues; customers experiencing specific failures should contact Snowflake Support. Impact start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses.

Reported by Snowflake on their status page.