- Level
- confirmed
- Worst impact
- Major outage
- Components
- Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications, Applications
- Down Index
- 42of 100
What to do
Check whether you use Snowflake Applications, Applications, Applications, Applications and 26 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 57m it lasted.
Anything that failed between 2026-07-30 03:00 UTC and 2026-07-30 04:56 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 5
- 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 log in to Snowsight. Affected users may encounter HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints.
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 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to log in to Snowsight. Affected users may encounter HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. ETA: Our current estimate is that service will be restored within 1 hour. Workaround: There are currently no available workarounds for this issue.
provider
- monitoring
Current status: We've reverted a recent configuration change and confirmed 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 log in to Snowsight. Affected users may have encountered HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. Workaround: There were no available workarounds for this issue. Incident start time: 00:18 UTC July 30, 2026 Incident end time: 03:52 UTC July 30, 2026 Preliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints.
provider
- resolved
Current status: We've monitored the environment and confirmed that reverting the configuration change restored service. 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 log in to Snowsight. Affected users may have encountered HTTP 404 errors or "Incoming request with IP/Token is not allowed to access Snowflake" errors when attempting to access Snowsight via private endpoints. Workaround: There were no available workarounds for this issue. Incident start time: 00:18 UTC July 30, 2026 Incident end time: 03:52 UTC July 30, 2026 Preliminary root cause: A recent configuration change to a subset of the routing infrastructure caused connectivity failures for customers accessing Snowsight via private endpoints. 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/INC20000115](https://community.snowflake.com/s/article/INC20000115)
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-50fced5604
Is Snowflake still down?
No, this incident was resolved 2026-07-30 04:56 UTC. For Snowflake's live state, see https://down.guide/snowflake.
How long did it last?
1h 57m, from 2026-07-30 03:00 UTC to 2026-07-30 04:56 UTC, by the times Snowflake posted.
What was affected?
Snowflake named Applications, Applications, Applications, Applications and 26 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.