- Level
- confirmed
- Worst impact
- Degraded
- Components
- Databases, Tables, and Views, Applications
- Down Index
- 17of 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 51m it lasted.
Anything that failed between 2026-10-21 07:45 UTC and 2026-10-21 08:36 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.
Updates from Snowflake 3
- monitoring
Current status: We identified that a subset of infrastructure responsible for routing service traffic in the affected region became intermittently unhealthy, which caused some requests to fail. We removed the affected infrastructure from service and are monitoring the environment to confirm that all services are functioning properly. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified regions may have experienced intermittent failures when using Snowsight. Symptoms may have included slow page loads or brief errors when accessing Snowsight. Retrying the operation may have succeeded in most cases, as the issue was intermittent in nature. Impact start time: 06:18 UTC October 21, 2026 Impact end time: 07:06 UTC October 21, 2026 Preliminary root cause: A subset of infrastructure responsible for routing incoming traffic in the affected region became unavailable, resulting in intermittent failures when loading Snowsight.
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 failures when using Snowsight. Symptoms may have included slow page loads or brief errors when accessing Snowsight. Retrying the operation may have succeeded in most cases, as the issue was intermittent in nature. Impact start time: 06:18 UTC October 21, 2026 Impact end time: 07:06 UTC October 21, 2026 Preliminary root cause: A subset of infrastructure responsible for routing incoming traffic in the affected region became unavailable, resulting in intermittent failures when loading Snowsight. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.
provider
- postmortem
Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000299](https://community.snowflake.com/s/article/INC20000299)
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-4932d71cc2
Is Snowflake still down?
No, this incident was resolved 2026-10-21 08:36 UTC. For Snowflake's live state, see https://down.guide/snowflake.
How long did it last?
51m, from 2026-10-21 07:45 UTC to 2026-10-21 08:36 UTC, by the times Snowflake posted.
What was affected?
Snowflake named Databases, Tables, and Views, Applications.
What caused it?
Snowflake hasn't published a root cause. If it does, it shows here.
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.