- Level
- confirmed
- Worst impact
- Major outage
- Components
- Databases, Tables, and Views, Applications
- Down Index
- 38of 100
What to do
Check whether you use Snowflake Databases, Tables, and Views, Applications. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 29m it lasted.
Anything that failed between 2026-10-16 01:14 UTC and 2026-10-16 01:43 UTC may need a replay.Subscribe to Snowflake's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=snowflake works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
Preliminary root cause: A routine software update caused a large number of background setup operations to run at the same time, which exhausted the resources of a subset of infrastructure responsible for processing queries in the affected region, resulting in intermittent delays and query failures.Read the postmortem
Updates from Snowflake 3
- monitoring
Current status: We identified that a subset of infrastructure responsible for processing queries and Snowsight requests in the affected region experienced elevated load, which caused intermittent delays and query failures. The load has since subsided, and query processing and Snowsight performance have returned to normal. 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 experienced intermittent delays when loading Snowsight or running queries, and some queries may have failed. Workaround: There were no available workarounds for this issue. Incident start time: 23:50 UTC October 15, 2026 Incident end time: 00:40 UTC October 16, 2026 Preliminary root cause: A routine software update caused a large number of background setup operations to run at the same time, which exhausted the resources of a subset of infrastructure responsible for processing queries in the affected region, resulting in intermittent delays and query failures.
provider
- resolved
Current status: We've monitored the environment and confirmed 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 experienced intermittent delays when loading Snowsight or running queries, and some queries may have failed. Workaround: There were no available workarounds for this issue. Incident start time: 23:50 UTC October 15, 2026 Incident end time: 00:40 UTC October 16, 2026 Preliminary root cause: A routine software update caused a large number of background setup operations to run at the same time, which exhausted the resources of a subset of infrastructure responsible for processing queries in the affected region, resulting in intermittent delays and query failures. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.
provider
- postmortem
[https://community.snowflake.com/s/article/INC20000287](https://community.snowflake.com/s/article/INC20000287)
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-0d1ddbbf30
Is Snowflake still down?
No, this incident was resolved 2026-10-16 01:43 UTC. For Snowflake's live state, see https://down.guide/snowflake.
How long did it last?
29m, from 2026-10-16 01:14 UTC to 2026-10-16 01:43 UTC, by the times Snowflake posted.
What was affected?
Snowflake named Databases, Tables, and Views, Applications.
What caused it?
Snowflake wrote: "Preliminary root cause: A routine software update caused a large number of background setup operations to run at the same time, which exhausted the resources of a subset of infrastructure responsible for processing queries in the affected region, resulting in intermittent delays and query failures." The postmortem: https://stspg.io/n0m38q7cfp4y
Where does this come from?
Snowflake's official status page, https://status.snowflake.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.