Live / Snowflake / Incident
Snowflake: INC20000319
Snowflake · snowflake.comMinor incidentResolved2026-10-30 01:57 UTC
Public — what happened
Summary
Snowflake said customers in certain regions may see delays or intermittent failures when starting or managing virtual warehouses, and that serverless tasks may be slow to begin, while warehouses already running may be unaffected. The company reported the impact began at 03:00 UTC on October 29, 2026, and posted its first notice at 04:29 UTC. Snowflake said the problem comes from a third-party cloud platform provider that was slow to respond to requests for computing resources, and that the provider is rolling out a fix. By its 09:04 UTC update, Snowflake said it expected most customer impact to be reduced, estimated the provider's fix within 2 hours, and listed no workaround. The incident was not marked resolved.
Affected
Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses, Virtual Warehouses
Timeline
- Started — 2026-10-29 04:29 UTC
- Investigating — 2026-10-29 04:29 UTC (3 updates)
- Identified — 2026-10-29 07:04 UTC (7 updates)
- Monitoring — 2026-10-30 00:47 UTC
- Resolved — 2026-10-30 01:57 UTC · 21h 28m 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 45, 2026, our weekly internet health report.