Changes / Snowflake / INC20000175
Snowflake: Critical incident: INC20000175
Summary
Snowflake reported a critical outage in Azure - Southeast Asia (Singapore), where infrastructure connectivity issues may have prevented customers from accessing services. It started at 2026-08-25 03:53 UTC and was resolved at 2026-08-25 04:35 UTC, lasting 41 min; Snowflake implemented a fix and confirmed restoration through monitoring. Other regions were unaffected.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: INC20000175
Before: not present
After: critical
Before: not present
After: postmortem
Before: not present
After: 2026-08-25 03:53 UTC
Before: not present
After: 2026-08-25 04:35 UTC
Before: not present
After: Applications, Azure - Southeast Asia (Singapore) - Applications, Azure - Southeast Asia (Singapore) - Databases, Tables, and Views, Databases, Tables, and Views
Before: not present
After: 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
Before: not present
After: 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.
Before: not present
After: 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.
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/INC20000175](https://community.snowflake.com/s/article/INC20000175)
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: INC20000175 (this change) Snowflake reported a critical outage in Azure - Southeast Asia (Singapore), where infrastructure connectivity issues may have prevented customers from accessing services. It started at 2026-08-25 03:53 UTC and was resolved at 2026-08-25 04:35 UTC, lasting 41 min; Snowflake implemented a fix and confirmed restoration through monitoring. Other regions were unaffected. | Major incident |
All Snowflake changes → · Snowflake profile · Markdown · JSON