Live / Snowflake / Incident
Snowflake: INC20000188
Snowflake · snowflake.comCritical outageResolved2026-08-31 18:45 UTC
Public — what happened
Summary
Snowflake reported a critical incident in which customers in one region may have lost access to several core services, such as logging in to Snowsight, running queries, moving data in and out, and using Snowpark Container Services, with some also seeing slower Snowpipe Streaming ingestion and more Snowsight errors. The company said the problem began at 16:58 UTC on August 31, 2026, that most of it was cleared by 17:25 UTC, and that lingering errors or slowness may have continued until about 18:10 UTC. Snowflake said its early finding was that a recent change to the affected infrastructure unintentionally caused increased competition for resources. It said a fix for the remaining effects was in place and it was continuing to watch the systems.
Timeline
- Started — 2026-08-31 17:20 UTC
- Resolved — 2026-08-31 19:52 UTC · 2h 32m 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 37, 2026, our weekly internet health report.