Live / Snowflake / Incident
Snowflake: INC20000287
Snowflake · snowflake.comCritical outageResolved2026-10-16 01:43 UTC
Public — what happened
Summary
Snowflake said that some customers in one affected region had intermittent slowness loading Snowsight or running queries, and that some queries failed. The company reported that part of the infrastructure handling these requests came under heavy load, and said the problem began at 23:50 UTC on October 15, 2026 and ended at 00:40 UTC on October 16. As a preliminary cause, Snowflake said a routine software update triggered many background setup tasks at once, using up resources. It said performance returned to normal, that no workaround was available, and the incident is marked resolved as of 01:43 UTC on October 16 after monitoring.
Affected
Databases, Tables, and Views
Timeline
- Started — 2026-10-16 01:14 UTC
- Monitoring — 2026-10-16 01:14 UTC
- Resolved — 2026-10-16 01:43 UTC · 29 min 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 43, 2026, our weekly internet health report.