Live / Snowflake / Incident
Snowflake: INC20000263
Snowflake · snowflake.comMajor incidentResolved2026-10-06 15:57 UTC
Public — what happened
Summary
Snowflake reported a major incident in which some users could not connect properly to its service, with accounts hosted in Azure UAE North seeing pages that never finished loading and users connecting from places including parts of the Middle East seeing an "Origin is unreachable" error. The company said the problem depended on the user's location rather than where the account was hosted, and that programmatic access such as drivers and SQL clients was not affected. Snowflake said the issue began at 11:55 UTC on October 6, 2026, and preliminarily attributed it to a network problem at a third-party edge network provider that disrupted routing of some Snowsight traffic. After the provider rolled out a fix, Snowflake said impact ended at 14:29 UTC, and the incident was marked resolved at 15:57.
Affected
Applications, Applications, Applications
Timeline
- Started — 2026-10-06 14:44 UTC
- Investigating — 2026-10-06 14:44 UTC
- Monitoring — 2026-10-06 15:17 UTC
- Resolved — 2026-10-06 15:57 UTC · 1h 13m 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 42, 2026, our weekly internet health report.