Live / Incidents / Snowflake
Snowflake: INC20000213
Snowflake · snowflake.comImpact: criticalResolved2026-09-11 11:24 UTC
Public — what happened
Summary
Current status: We've identified additional impact in the AWS - Asia Pacific (Tokyo) region, in which we've applied the same fix for this issue. 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 sign in to Snowsight, and may have receive an error message such as "Something went wrong." This issue was intermittent and did not affect all users; affected users may also have experienced issues executing queries or managing data.
Incident start time: 05:00 UTC September 11, 2026
Incident end time: 11:15 UTC September 11, 2026
Preliminary root cause: A conf
Timeline
- Started — 2026-09-11 07:18 UTC
- Last update — 2026-09-11 11:24 UTC
- Resolved — 2026-09-11 13:22 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 →