Live / Incidents / Snowflake
Snowflake: INC20000199
Snowflake · snowflake.comImpact: criticalResolved2026-09-04 09:04 UTC
Public — what happened
Summary
Current status: We've implemented the fix for this issue by rolling back a configuration update to the underlying infrastructure. Our telemetry and internal validations indicate that service has been restored. 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 Snowflake services and features using Snowsight.
Workaround: There were no available workarounds for this issue.
Incident start time: 07:00 UTC September 04, 2026
Incident end time: 08:30 UTC September 04, 2026
Preliminary root cause: A configuration update to infrastructure compon
Timeline
- Started — 2026-09-04 07:34 UTC
- Last update — 2026-09-04 09:04 UTC
- Resolved — 2026-09-04 10:33 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 →