- Level
- confirmed
- Worst impact
- Major outage
- Components
- Applications
- Down Index
- 40of 100
What to do
Check whether you use Snowflake 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 1h 17m it lasted.
Anything that failed between 2026-06-08 15:23 UTC and 2026-06-08 16:40 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 4
- investigating
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to access or use Snowflake services and features using Snowsight.
provider
- monitoring
Current status: During our investigation, the service self-recovered. 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 been unable to access or use Snowflake services and features using Snowsight. Customers may have experienced page not found errors or general login failures. Workaround: There are currently no available workarounds for this issue. Incident start time: 14:58 UTC June 08, 2026
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 been unable to access or use Snowflake services and features using Snowsight. Customers may have experienced page not found errors or general login failures. Incident start time: 14:58 UTC June 08, 2026 Incident end time: 15:20 UTC June 08, 2026 Preliminary root cause: An internal system degradation occurred within backend database infrastructure that supports Snowsight in the affected region, causing Snowsight request failures. The issue was detected by system health monitoring, and automated recovery systems performed scaling and targeted infrastructure restart operations that helped to restore service. We’re continuing to investigate to confirm the underlying root cause details and the contributing factors. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page 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/INC20000030](https://community.snowflake.com/s/article/INC20000030)
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-1305c73dd1
Is Snowflake still down?
No, this incident was resolved 2026-06-08 16:40 UTC. For Snowflake's live state, see https://down.guide/snowflake.
How long did it last?
1h 17m, from 2026-06-08 15:23 UTC to 2026-06-08 16:40 UTC, by the times Snowflake posted.
What was affected?
Snowflake named 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.