Live  /  Snowflake  /  Incident

Snowflake: INC20000336

Snowflake · snowflake.comMinor incidentResolved2026-11-07 02:52 UTC
Public — what happened

Summary

Snowflake said customers in certain regions had trouble resuming or scaling up virtual warehouses, beginning with a report at 23:32 UTC on 2026-11-06. It later added that some serverless tasks ran slowly and that new Snowpark Container Services services, including notebooks, could not be started. Snowflake said a third-party cloud platform provider's problem with provisioning computing resources was the cause, and that warehouses already running might not have been affected. By 01:41 UTC on 2026-11-07 it said the provider had fixed the underlying issue and it was monitoring, and the incident was marked resolved at 02:52 UTC.

Affected

Virtual Warehouses, Virtual Warehouses, Snowpark Container Services, Snowpark Container Services

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 46, 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.