INC20000128

Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly.

Customer experience: Customers hosted in the specified region may have experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue was intermittent and did not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection.

Although initial indications were that this issue was affecting multiple deployments, subsequent investigation demonstrated the issue was restricted to the AWS - Asia Pacific (Tokyo) region.

Incident start time: 00:53 UTC August 03, 2026
Incident end time: 06:15 UTC August 03, 2026

Preliminary root cause: An update intended to improve the efficiency of connection handling at the network routing layer was identified and rolled back to restore service.

Current status: We've implemented the fix for this issue, and we'll continue to monitor the environment until we're confident all services are functioning properly.

Customer experience: Customers hosted in the specified region may have experienced intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue was intermittent and did not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection.

Although initial indications were that this issue was affecting multiple deployments, subsequent investigation demonstrated the issue was restricted to the AWS - Asia Pacific (Tokyo) region.

Incident start time: 00:53 UTC August 03, 2026
Incident end time: 06:15 UTC August 03, 2026

Preliminary root cause: An update intended to improve the efficiency of connection handling at the network routing layer was identified and rolled back to restore service.

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 1 hour.

Customer experience: Customers hosted in the specified region may experience intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue is intermittent and does not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection.

Please note that further investigation has demonstrated this issue is restricted to the AWS - Asia Pacific (Tokyo) region.

ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures.

Workaround: There are currently no available workarounds for this issue beyond retrying failed requests.

Incident start time: 00:53 UTC August 03, 2026

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 60 minutes.

Customer experience: Customers hosted in the specified regions may experience intermittent Snowsight login failures, elevated page load times, or session timeouts when accessing the web interface. Affected users may encounter errors such as "Failed to fetch" and "Execution failed", or HTTP 503 Service Unavailable messages. The issue is intermittent and does not affect all users or login attempts simultaneously; retrying failed requests generally results in successful connection.

ETA: An ETA is not yet available. We'll provide one as soon as possible. In the meantime, we recommend that affected customers using replication initiate their failover procedures.

Workaround: There are currently no available workarounds for this issue beyond retrying failed requests.

Incident start time: 00:53 UTC August 03, 2026