Live / Snowflake / Incident
Snowflake: INC20000213
Snowflake · snowflake.comCritical outageResolved2026-09-11 11:24 UTC
Public — what happened
Summary
Snowflake reported a critical incident in which some customers in the affected regions, including AWS Asia Pacific (Tokyo), intermittently could not log in to Snowsight and might have seen a generic error, with some also having trouble running queries or managing data. The company said the problem began at 05:00 UTC on September 11, 2026 and ended at 11:15 UTC the same day, and that not every user was affected. Snowflake said its preliminary finding was that a configuration change to systems that authorize incoming network traffic caused them to block that traffic. After finding further impact in the Tokyo region and applying the same fix there, the company said it was continuing to monitor its services.
Timeline
- Started — 2026-09-11 07:18 UTC
- Resolved — 2026-09-11 13:22 UTC · 6h 04m 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 38, 2026, our weekly internet health report.