# INC20000115

- Provider: [Snowflake](https://down.guide/snowflake)
- Level: confirmed
- Impact: Major outage
- lasted 1h 57m
- started 2026-07-30 03:00 UTC
- Applications, Applications, Applications +27
- id: DWN-50fced5604
- Official page: https://stspg.io/2jfpk15p29pd

## Updates from Snowflake
### 2026-07-30 03:00 UTC: 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.

### 2026-07-30 03:30 UTC: 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.

### 2026-07-30 04:17 UTC: 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.

### 2026-07-30 04:56 UTC: 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.

### 2026-08-10 04:31 UTC: 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)

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).