- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views
- Down Index
- 28of 100
What to do
Check whether you use Snowflake Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views and 2 more. 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 21m it lasted.
Anything that failed between 2026-09-14 04:48 UTC and 2026-09-14 06:09 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 1 hour. Customer experience: Customers in the affected regions may experience performance degradation or issues logging into Snowflake, including delayed sign-ins, query execution failures, and errors managing data. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 23:35 UTC September 13, 2026
provider
- identified
Current status: We've identified the source of the issue, and we're developing and implementing a fix to restore service. We'll provide another update within 1 hour. Customer experience: Customers hosted in the affected deployments may experience performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures. Workaround: There are currently no available workarounds for this issue. Incident start time: 23:35 UTC September 13, 2026
provider
- monitoring
Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly. Customer experience: Customers hosted in the affected deployments may have experienced performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. Incident start time: 23:35 UTC September 13, 2026 Incident end time: 05:18 UTC September 14, 2026 Preliminary root cause: An update intended to improve authentication handling caused a subset of single sign-on (SSO) sign-in attempts across multiple regions to fail or loop, preventing affected users from logging in to Snowflake.
provider
- resolved
Current status: We've implemented the fix for this issue and monitored the environment to confirm 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 affected deployments may have experienced performance degradation or issues logging into Snowflake, including delayed sign-ins, and SSO login loops. Incident start time: 22:22 UTC September 13, 2026 Incident end time: 05:18 UTC September 14, 2026 Preliminary root cause: An update intended to improve authentication handling caused a subset of single sign-on (SSO) sign-in attempts across multiple regions to fail or loop, preventing affected users from logging in to Snowflake. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.
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-65751d5b7f
Is Snowflake still down?
No, this incident was resolved 2026-09-14 06:09 UTC. For Snowflake's live state, see https://down.guide/snowflake.
How long did it last?
1h 21m, from 2026-09-14 04:48 UTC to 2026-09-14 06:09 UTC, by the times Snowflake posted.
What was affected?
Snowflake named Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views, Databases, Tables, and Views and 2 more.
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.