Live  /  Snowflake  /  Incident

Snowflake: INC20000294

Snowflake · snowflake.comCritical outageResolved2026-10-20 15:26 UTC
Public — what happened

Summary

Snowflake said customers in one region may have been unable to use several of its services, including Snowflake Postgres, and could have seen errors when connecting, loading data or using applications. The company said the problem began around 06:01 UTC on October 20, 2026, and that it had traced it to an issue with a third-party cloud provider affecting one availability zone. Snowflake said workloads moved away from the affected infrastructure and its monitoring showed healthy service from 06:40 UTC, while it kept precautions in place until the provider restored the zone. Snowflake reported the provider said the issue was largely mitigated, gave an end time of 14:03 UTC, and marked the incident resolved at 15:26.

Affected

Databases, Tables, and Views, Data Loading and Unloading, Applications

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.