Changes / Snowflake / INC20000115
Snowflake: Critical incident: INC20000115
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 diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: INC20000115
Before: not present
After: critical
Before: not present
After: postmortem
Before: not present
After: 2026-07-30 03:00 UTC
Before: not present
After: 2026-07-30 04:56 UTC
Before: not present
After: Applications, AWS - Africa (Cape Town) - Applications, AWS - Asia Pacific (Jakarta) - Applications, AWS - Asia Pacific (Malaysia) - Applications, AWS - Asia Pacific (Mumbai) - Applications, AWS - Asia Pacific (New Zealand) - Applications, AWS - Asia Pacific (Osaka) - Applications, AWS - Asia Pacific (Seoul) - Applications, AWS - Asia Pacific (Singapore) - Applications, AWS - Asia Pacific (Sydney) - Applications, AWS - Asia Pacific (Thailand) - Applications, AWS - Asia Pacific (Tokyo) - Applications, AWS - Canada (Central) - Applications, AWS - Europe (Frankfurt) - Applications, AWS - Europe (London) - Applications, AWS - Europe (Paris) - Applications, AWS - Europe (Stockholm) - Applications, AWS - Europe (Zürich) - Applications, AWS - South America (São Paulo) - Applications, AWS - US East (Ohio) - Applications, AWS - US West (Oregon) - Applications, Azure - Australia East (New South Wales) - Applications, Azure - Canada Central (Toronto) - Applications, Azure - Central Korea (Seoul) - Applications, Azure - Central US (Iowa) - Applications, Azure - Japan East (Tokyo, Saitama) - Applications, Azure - Mexico (Central) - Applications, Azure - North Europe (Ireland) - Applications, Azure - South Central US (Texas) - Applications, Azure - Southeast Asia (Singapore) - Applications, Azure - Sweden Central (Gävle) - Applications, Azure - Switzerland North (Zürich) - Applications, Azure - UAE North (Dubai) - Applications
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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)
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: INC20000115 (this change) 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. | Major incident |
All Snowflake changes → · Snowflake profile · Markdown · JSON