INC20000115
Incident
Report for Snowflake
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.
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.
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.
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.
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.
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.
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.
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.
This incident affected: AWS - US West (Oregon) (Applications), AWS - Canada (Central) (Applications), AWS - US East (Ohio) (Applications), AWS - Europe (London) (Applications), AWS - Europe (Frankfurt) (Applications), AWS - Asia Pacific (Mumbai) (Applications), AWS - Asia Pacific (Singapore) (Applications), AWS - Asia Pacific (Sydney) (Applications), AWS - Asia Pacific (Tokyo) (Applications), Azure - Canada Central (Toronto) (Applications), Azure - Central US (Iowa) (Applications), Azure - Switzerland North (Zürich) (Applications), Azure - Southeast Asia (Singapore) (Applications), Azure - Australia East (New South Wales) (Applications), Azure - North Europe (Ireland) (Applications), AWS - Europe (Stockholm) (Applications), Azure - UAE North (Dubai) (Applications), Azure - South Central US (Texas) (Applications), AWS - Asia Pacific (Osaka) (Applications), AWS - South America (São Paulo) (Applications), AWS - Europe (Paris) (Applications), AWS - Asia Pacific (Jakarta) (Applications), AWS - Europe (Zürich) (Applications), Azure - Mexico (Central) (Applications), Azure - Central Korea (Seoul) (Applications), AWS - Africa (Cape Town) (Applications), Azure - Sweden Central (Gävle) (Applications), AWS - Asia Pacific (Malaysia) (Applications), AWS - Asia Pacific (Thailand) (Applications), and AWS - Asia Pacific (New Zealand) (Applications).