INC20000175

What to do

• Check whether you use Snowflake Databases, Tables, and Views, 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 42m it lasted.

  Anything that failed between 2026-08-25 03:53 UTC and 2026-08-25 04:35 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 4

1. investigatingAug 25, 2026, 3:53 AM UTC

   Current status: We're investigating an issue with Snowflake Data Cloud in the Southeast Asia region. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the Southeast Asia region may be unable to access Snowflake services due to infrastructure connectivity issues. All other Snowflake features in other regions are not impacted. 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. Incident start time: 03:09 UTC August 25, 2026

   provider

2. monitoringAug 25, 2026, 4:10 AM UTC

   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. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may have been unable to access Snowflake services due to infrastructure connectivity issues. All other Snowflake features in other regions were not impacted. Workaround: There were no available workarounds for this issue. Incident start time: 03:09 UTC August 25, 2026 Incident end time: 04:05 UTC August 25, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual machine service issue, which caused infrastructure connectivity problems affecting Snowflake services in the region.

   provider

3. resolvedAug 25, 2026, 4:35 AM UTC

   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 been unable to access Snowflake services due to infrastructure connectivity issues. All other Snowflake features in other regions were not impacted. Workaround: There were no available workarounds for this issue. Incident start time: 03:09 UTC August 25, 2026 Incident end time: 04:05 UTC August 25, 2026 Preliminary root cause: A third-party cloud platform experienced a virtual machine service issue, which caused infrastructure connectivity problems affecting Snowflake services in the region. A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

   provider

4. postmortemSep 3, 2026, 1:17 AM 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/INC20000175](https://community.snowflake.com/s/article/INC20000175)

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.