Snowflake outage, 12 November 2026

INC20000350

Started
Resolved
13 Nov 2026, 00:13 UTC (after 42 min)
Impact
Minor
Affected
Data Loading and Unloading

Is this still happening?

No. Snowflake marked this incident resolved on 13 Nov 2026, 00:13 UTC, 42 min after it began.

Right now: Snowflake reports all systems operational. (as of 13 Nov, 20:53 UTC) Live Snowflake status

At a glance

Our summary from the Snowflake incidents we have recorded since 10 Jul 2026 - how we count.

What caused it: Snowflake's root cause analysis

Current status: Task execution latency has returned to pre-incident levels. We've increased the compute resources available to the affected systems as part of the mitigation, and 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 experienced delays when executing scheduled or manual tasks. Affected users may have seen tasks run slower than expected or fail. Impact start time: 21:45 UTC November 12, 2026 Impact end time: 23:02 UTC November 12, 2026 Preliminary root cause: A subset of infrastructure responsible for task execution exhausted its resources, causing delays in task execution in the affected region.

Read the full postmortem from Snowflake

Last update from Snowflake

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 experienced delays when executing scheduled or manual tasks. Affected users may have seen tasks run slower than expected or fail. Impact start time: 21:45 UTC November 12, 2026 Impact end time: 23:02 UTC November 12, 2026 Preliminary root cause: A subset of infrastructure responsible for task execution exhausted its resources, causing delays in task execution...

13 Nov 2026, 00:13 UTC

Read the full incident on the official Snowflake status page

Similar Snowflake incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 5 h 3 min

    INC20000301Postmortem

  2. , resolved after 8 h 52 min

    INC20000294Postmortem

  3. , resolved after 24 h 4 min

    INC20000277Postmortem

  4. , resolved after 1 h

    INC20000239Postmortem

  5. , resolved after 1 h 20 min

    INC20000237Postmortem

Other recent Snowflake incidents

  1. INC20000347Postmortem

  2. INC20000337Postmortem

  3. INC20000336Postmortem

  4. INC20000321Postmortem

  5. INC20000319Postmortem

  6. INC20000299Postmortem

  7. INC20000290Postmortem

  8. INC20000287Postmortem

All recorded Snowflake incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from Snowflake's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.