Live / Snowflake / Incident
Snowflake: INC20000277
Snowflake · snowflake.comMinor incidentResolved2026-10-15 21:51 UTC
Public — what happened
Summary
Snowflake said that customers in one of its regions had trouble with scheduled and manual tasks starting on October 13, 2026, with some tasks stuck waiting, failing to start, or being marked as failed even though their queries had actually finished. The company reported that its early findings pointed to inconsistent task records in its metadata system, and it later gave a preliminary explanation that a portion of infrastructure in the region had a problem. After first working on a data fix, Snowflake said on October 14 that it switched to restarting infrastructure in the region, which lowered failure rates, though it warned that some task run history might be missing or incomplete and some tasks might fail once more. The incident is marked resolved as of October 15, 2026.
Affected
Data Loading and Unloading
Timeline
- Started — 2026-10-13 15:53 UTC
- Investigating — 2026-10-13 15:53 UTC (8 updates)
- Identified — 2026-10-14 21:47 UTC (2 updates)
- Monitoring — 2026-10-15 21:03 UTC
- Resolved — 2026-10-15 21:51 UTC · 2 days 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 43, 2026, our weekly internet health report.