Snowflake Incident History

1. resolvedSep 14 · 06:09 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 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.

Reported by Snowflake on their status page.

1. ResolvedSep 14 · 06:09 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 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, 2026Incident end time: 05:18 UTC September 14, 2026Preliminary 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.

Reported by Snowflake on their status page.

1. postmortemSep 18 · 14:28 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/INC20000213

Reported by Snowflake on their status page.

1. ResolvedSep 11 · 13:19 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 sign in to Snowsight, and may have receive an error message such as "Something went wrong." This issue was intermittent and did not affect all users; affected users may also have experienced issues executing queries or managing data.Incident start time: 05:00 UTC September 11, 2026Incident end time: 11:15 UTC September 11, 2026Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.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. resolvedSep 9 · 23:51 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 regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Workaround: There were no available workarounds for this issue. Incident start time: 21:26 UTC September 09, 2026 Incident end time: 21:55 UTC September 09, 2026 Preliminary root cause: A subset of our metadata database infrastructure became unavailable, resulting in failures across multiple Snowflake 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. ResolvedSep 9 · 23:51 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 regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data.Workaround: There were no available workarounds for this issue.Incident start time: 21:26 UTC September 09, 2026Incident end time: 21:55 UTC September 09, 2026Preliminary root cause: A subset of our metadata database infrastructure became unavailable, resulting in failures across multiple Snowflake 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. postmortemSep 14 · 22:14 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/INC20000199

Reported by Snowflake on their status page.

1. ResolvedSep 4 · 10:10 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 use Snowflake services and features using Snowsight.Workaround: There were no available workarounds for this issue.Incident start time: 07:00 UTC September 04, 2026Incident end time: 08:30 UTC September 04, 2026Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.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. postmortemSep 9 · 11:25 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/INC20000190

Reported by Snowflake on their status page.

1. ResolvedSep 1 · 13:50 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 sign in to Snowflake Cowork, and may have seen a message indicating that sign-in was unsuccessful. All other Snowflake features were not impacted.Workaround: There were no available workarounds for this issue.Incident start time: 00:00 UTC September 01, 2026Incident end time: 11:55 UTC September 01, 2026Preliminary root cause: An update to the underlying database objects responsible for managing CoWork sign-on mechanisms experienced a configuration error which resulted in the symptoms observed.A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

Reported by Snowflake on their status page.

1. postmortemSep 9 · 17:27 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/INC20000188

Reported by Snowflake on their status page.

1. identifiedSep 17 · 23:04 UTC

   Current status: We've taken additional steps with our warehouse team to reduce provisioning latencies for virtual warehouses, and we've observed some improvement in provisioning latencies as a result. Resource availability remains variable and correlated to overall demand, with some intermittent delays occurring during high-volume times. We're continuing to work closely with our warehouse team to maintain available capacity and keep provisioning times low. Our third-party cloud platform provider has indicated that the additional compute capacity remains on track, and we're continuing to coordinate with them to restore the needed capacity. We'll provide another update within 7 days. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected. Additionally, starting from 04:00 UTC September 04, 2026, customers hosted in the specified region with workloads on second generation (Gen2) warehouses may experience delays or intermittent failures when resuming or starting virtual warehouses. This may result in longer than expected query run times or delays in completing data pipelines. Warehouses that are already running are largely unaffected. ETA: Based on information from our third-party cloud platform provider, we expect additional compute resources to become available in the specified region by mid-October. We'll provide an updated ETA as we receive more information. Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. For customers experiencing impact to virtual warehouses, and who have already performed a failover, we recommend remaining in the alternate region until we have received additional capacity allocation from the third-party provider. Customers who are continuing to experience impact to virtual warehouses may see additional relief by migrating workloads to first generation (Gen1) warehouses, which remain less impacted by this issue. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform provider is experiencing constrained compute capacity, affecting compute resource provisioning, and causing limited availability of compute resources as well as delays and intermittent failures when resuming or starting virtual warehouses in the specified region.

Reported by Snowflake on their status page.

1. UpdateSep 11 · 00:04 UTC

   Current status: Our third-party cloud platform provider has informed us that they expect to be able to provide additional capacity allocation by mid-October. In the meantime, we are working to preserve compute resources available to us, reduce non-essential resource consumption, and investigate any alternative methods to further reduce impact. Resource availability remains variable and correlated to overall demand, with some intermittent delays occurring during high-volume times. We'll provide another update by 23:00 UTC September 17, 2026.Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected.Additionally, starting from 04:00 UTC September 04, 2026, customers hosted in the specified region with workloads on second generation (Gen2) warehouses may experience delays or intermittent failures when resuming or starting virtual warehouses. This may result in longer than expected query run times or delays in completing data pipelines. Warehouses that are already running are largely unaffected.ETA: Based on information from our third-party cloud platform provider, we anticipate a solution in mid-October.Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved.For customers experiencing impact to virtual warehouses, and who have already performed a failover, we recommend remaining in the alternate region until we have received additional capacity allocation from the third-party provider.Customers who are continuing to experience impact to virtual warehouses may see additional relief by migrating workloads to first generation (Gen1) warehouses, which remain less impacted by this issue.Incident start time: 08:41 UTC August 09, 2026Preliminary root cause: A third-party cloud platform provider is experiencing constrained compute capacity, affecting compute resource provisioning, and causing limited availability of compute resources as well as delays and intermittent failures when resuming or starting virtual warehouses in the specified region.

Reported by Snowflake on their status page.

1. postmortemSep 3 · 21:03 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/INC20000182

Reported by Snowflake on their status page.

1. postmortemSep 3 · 01: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/INC20000175

Reported by Snowflake on their status page.

1. postmortemAug 31 · 22:54 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/INC20000173

Reported by Snowflake on their status page.

1. postmortemSep 3 · 20:06 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/INC20000168

Reported by Snowflake on their status page.

1. postmortemAug 25 · 22:42 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/INC20000163

Reported by Snowflake on their status page.