Live / Snowflake / Incident
Snowflake: INC20000337
Snowflake · snowflake.comMinor incidentResolved2026-11-07 04:44 UTC
Public — what happened
Summary
Snowflake said it began investigating a minor issue with its Data Cloud at 02:38 UTC on November 7, 2026, which it said could slow down starting or enlarging warehouses for customers in one region, and cause occasional delays with Snowpark Container Services compute pools. By 03:47 UTC the company said it had kept existing warehouse resources in place and that service had recovered, giving an impact window of 01:50 to 03:14 UTC. Snowflake described a preliminary cause as a problem with resource provisioning in that region and said it was working with its third-party cloud provider to find the source. The incident was marked resolved at 04:44 UTC.
Affected
Virtual Warehouses, Snowpark Container Services
Timeline
- Started — 2026-11-07 02:38 UTC
- Investigating — 2026-11-07 02:38 UTC
- Monitoring — 2026-11-07 03:47 UTC
- Resolved — 2026-11-07 04:44 UTC · 2h 05m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.