Snowflake Status Page

Oct 16, 2026 · resolved Oct 16

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, 2026 Incident end time: 00:40 UTC October 16, 2026 Preliminary 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.

Oct 13, 2026 · resolved Oct 15

Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. We're continuing our deployment of a secondary fix to restore the remaining task graph run history for the affected time period. 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 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 primary mitigation, the next time each task ran, it may still have been marked as failed with an internal error message even though its query ran successfully. This may have happened up to one additional time per task. While the functional impact regarding task failures or tasks silently succeeding is resolved, affected customers may still 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. Incident start time: 10:58 UTC October 13, 2026 Incident end time: 17:35 UTC October 15, 2026 Preliminary root cause: Our investigation identified a metadata mismatch within the metadata database layer. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

Oct 6, 2026 · resolved Oct 6

Current status: We've coordinated with our third-party provider who implemented a 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 seen pages that loaded indefinitely. Customers in other regions who connected from certain locations, including parts of the Middle East, may have seen an “Origin is unreachable” error. This depended on where the user was connecting from, not on which region the account was hosted in. Incident start time: 11:55 UTC October 06, 2026 Incident end time: 14:29 UTC October 06, 2026 Preliminary root cause: A network issue with a third-party edge network provider affected the routing of some Snowsight traffic between certain customer locations and the affected regions, resulting in pages that loaded indefinitely and connection errors. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

Sep 27, 2026 · resolved Sep 27

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 · resolved Sep 26

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)

Is Snowflake down right now?

Yes — Snowflake is reporting a minor incident as of Oct 18, 1:14 AM UTC.

What is Snowflake's current status?

Snowflake: Partially Degraded Service. Alert24 checks Snowflake's status page continuously and can notify you the moment it changes.

How do I get alerted when Snowflake goes down?

Alert24 monitors Snowflake and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.