Live / Incidents / Snowflake
Snowflake: INC20000211
Snowflake · snowflake.comImpact: criticalResolved2026-09-09 23:05 UTC
Public — what happened
Summary
Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly.
Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data.
Workaround: There were no available workarounds for this issue.
Incident start time: 21:26 UTC September 09, 2026
Incident end time: 21:55 UTC September 09, 2026
Preliminary root cause: A subset of our metadata database infrastructure became unavailable, resulting in failures across multiple Snowflake
Timeline
- Started — 2026-09-09 21:53 UTC
- Last update — 2026-09-09 23:05 UTC
- Resolved — 2026-09-09 23:58 UTC
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 →