Live / Snowflake / Incident
Snowflake: INC20000150
Snowflake · snowflake.comMinor incidentResolved2026-11-12 20:08 UTC
Public — what happened
Summary
Snowflake reported that customers in one unnamed region could intermittently fail to use Snowpark Container Services, seeing errors, timeouts or delays when starting or resuming Notebooks or setting up compute pools, while Notebooks on virtual warehouses were unaffected. The company said the problem began at 08:41 UTC on August 9, 2026, and attributed it to a shortage of computing capacity at its third-party cloud provider; it later added that from 04:00 UTC on September 4, Gen2 warehouses in that region could also be slow or fail to start. Snowflake said it was prioritizing Business Critical accounts, pausing non-essential work and preparing a software update to allow more compute options. As of its latest update the issue was not resolved, and Snowflake said the provider expected to add capacity by mid-October.
Affected
Virtual Warehouses, Snowpark Container Services
Timeline
- Started — 2026-08-28 00:07 UTC
- Identified — 2026-08-28 00:07 UTC (13 updates)
- Resolved — 2026-11-12 20:08 UTC · 77 days 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