Live / Incidents / Snowflake
Snowflake: INC20000239
Snowflake · snowflake.comImpact: criticalResolved2026-09-27 03:16 UTC
Public — what happened
Summary
Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.
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.
Incident start time: 00:25 UTC September 27, 2026
Incident end time: 01:00 UTC September 27, 2026
Preliminary root cause: An issue with our third-p
Timeline
- Started — 2026-09-27 02:15 UTC
- Last update — 2026-09-27 03:16 UTC
- Resolved — 2026-09-27 03:16 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 →