Live  /  Snowflake  /  Incident

Snowflake: INC20000301

Snowflake · snowflake.comCritical outageResolved2026-10-21 23:29 UTC
Public — what happened

Summary

Snowflake said customers in one of its regions had trouble using many core services, including signing in, using Snowsight, running queries, and loading files with Snowpipe, and later added that scheduled tasks might not run. The company logged the problem at 18:26 UTC on October 21, 2026, giving an impact start of 18:00 UTC, and said it was investigating the systems that process requests in that region. It said it found a configuration issue, made a configuration change, and then saw services gradually recover. Snowflake's preliminary explanation was that a configuration change interacted with existing settings and took many instances out of service, and it said impact ended at 21:25 UTC and marked the incident resolved at 23:29 UTC.

Affected

Databases, Tables, and Views, Virtual Warehouses, Data Loading and Unloading, Applications, Snowpark Container Services, AI and ML

As listed on Snowflake’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Snowflake against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Snowflake: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Snowflake report →

More from Snowflake

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Snowflake status & history page.

Related: Snowflake status & history. SquidGrid is not affiliated with Snowflake.