- Level
- confirmed
- Worst impact
- Degraded
- Components
- Applications
- Regions
- apac
- Down Index
- 23of 100
What to do
Check whether you use Snowflake Applications in apac. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 22m it lasted.
Anything that failed between 2026-08-03 05:53 UTC and 2026-08-03 08:15 UTC may need a replay.Subscribe to Snowflake's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=snowflake works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Snowflake 6
- investigating
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
provider
- 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 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
provider
- monitoring
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.
provider
- monitoring
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.
provider
- resolved
Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. 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 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. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.
provider
- 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/INC20000128](https://community.snowflake.com/s/article/INC20000128)
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9c7ab8d2c8
Is Snowflake still down?
No, this incident was resolved 2026-08-03 08:15 UTC. For Snowflake's live state, see https://down.guide/snowflake.
How long did it last?
2h 22m, from 2026-08-03 05:53 UTC to 2026-08-03 08:15 UTC, by the times Snowflake posted.
What was affected?
Snowflake named Applications in apac.
What caused it?
Snowflake hasn't published a root cause. If it does, it shows here.
Where does this come from?
Snowflake's official status page, https://status.snowflake.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.