- Level
- confirmed
- Worst impact
- Major outage
- Components
- Databases, Tables, and Views, Applications, Developer Tools
- Down Index
- 42of 100
What to do
Check whether you use Snowflake Databases, Tables, and Views, Applications, Developer Tools. 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 2h 36m it lasted.
Anything that failed between 2026-09-04 07:34 UTC and 2026-09-04 10:10 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 6
- 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. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are currently no available workarounds for this issue. Incident start time: 07:00 UTC September 04, 2026
provider
- investigating
Current status: We're continuing to investigate the issue with Snowflake Data Cloud. We'll provide another 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. 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: 07:00 UTC September 04, 2026
provider
- investigating
Current status: We're continuing to actively investigate the issue with Snowflake Data Cloud. The specific focus at this time is on infrastructure components responsible for authorizing incoming traffic. We'll provide another 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. 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: 07:00 UTC September 04, 2026
provider
- monitoring
Current status: We've implemented the fix for this issue by rolling back a configuration update to the underlying infrastructure. Our telemetry and internal validations indicate that service has been restored. 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. Workaround: There were no available workarounds for this issue. Incident start time: 07:00 UTC September 04, 2026 Incident end time: 08:30 UTC September 04, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic.
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 specified regions may have been unable to access or use Snowflake services and features using Snowsight. Workaround: There were no available workarounds for this issue. Incident start time: 07:00 UTC September 04, 2026 Incident end time: 08:30 UTC September 04, 2026 Preliminary root cause: A configuration update to infrastructure components responsible for authorizing incoming network traffic caused the components to restrict this traffic. 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/INC20000199](https://community.snowflake.com/s/article/INC20000199)
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-8ff40fa9e5
Is Snowflake still down?
No, this incident was resolved 2026-09-04 10:10 UTC. For Snowflake's live state, see https://down.guide/snowflake.
How long did it last?
2h 36m, from 2026-09-04 07:34 UTC to 2026-09-04 10:10 UTC, by the times Snowflake posted.
What was affected?
Snowflake named Databases, Tables, and Views, Applications, Developer Tools.
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.