Snowflake: INC20000115

Impact: criticalStatus: postmortemStarted 2026-07-30 03:00 UTCResolved 2026-07-30 04:56 UTC (1.9 h)5 updatesSource: stspg.io

Summary

Snowflake reported a critical incident preventing some customers in listed AWS and Azure regions from logging in to Snowsight via private endpoints, with HTTP 404 or IP/Token access errors. It started at 2026-07-30 03:00 UTC and was resolved at 2026-07-30 04:56 UTC after reverting a recent configuration change.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: ApplicationsAzure - UAE North (Dubai) - ApplicationsApplicationsAWS - Asia Pacific (Osaka) - ApplicationsApplicationsAzure - North Europe (Ireland) - ApplicationsApplicationsAWS - Asia Pacific (Thailand) - ApplicationsApplicationsAWS - Europe (Paris) - ApplicationsApplicationsAzure - Southeast Asia (Singapore) - ApplicationsApplicationsAzure - South Central US (Texas) - ApplicationsApplicationsAWS - US West (Oregon) - ApplicationsApplicationsAWS - Asia Pacific (Sydney) - ApplicationsApplicationsAWS - Europe (Frankfurt) - ApplicationsApplicationsAWS - US East (Ohio) - ApplicationsApplicationsAWS - Africa (Cape Town) - ApplicationsApplicationsAzure - Sweden Central (Gävle) - ApplicationsApplicationsAWS - Asia Pacific (Malaysia) - ApplicationsAWS - Asia Pacific (Seoul) - ApplicationsApplicationsAWS - Asia Pacific (Mumbai) - ApplicationsApplicationsAWS - Asia Pacific (New Zealand) - ApplicationsApplicationsAWS - Asia Pacific (Jakarta) - ApplicationsApplicationsAzure - Mexico (Central) - ApplicationsApplicationsAWS - Asia Pacific (Singapore) - ApplicationsApplicationsAWS - Europe (London) - ApplicationsApplicationsAWS - Europe (Stockholm) - ApplicationsApplicationsAzure - Canada Central (Toronto) - ApplicationsApplicationsAzure - Switzerland North (Zürich) - ApplicationsApplicationsAWS - Canada (Central) - ApplicationsApplicationsAzure - Central Korea (Seoul) - ApplicationsApplicationsAzure - Central US (Iowa) - ApplicationsAzure - Japan East (Tokyo, Saitama) - ApplicationsApplicationsAzure - Australia East (New South Wales) - ApplicationsApplicationsAWS - Europe (Zürich) - ApplicationsApplicationsAWS - South America (São Paulo) - ApplicationsApplicationsAWS - Asia Pacific (Tokyo) - Applications

Timeline of updates

investigating2026-07-30 03:00 UTC
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.
identified2026-07-30 03:30 UTC
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.
monitoring2026-07-30 04:17 UTC
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.
resolved2026-07-30 04:56 UTC
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.
postmortem2026-08-10 04:31 UTC
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)

Rewindex changes for this incident

Critical incident: INC20000115 2026-07-30 03:00 UTC

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Snowflake profile · Recent Snowflake incidents · Markdown · JSON