INC0145263
Final update
Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. We have observed stable and healthy performance across the Snowflake service since 21:18 UTC. Failback operations to origin regions may now be initiated by customers who previously failed over. In light of the recent operational severity, we provide guidance for customers to cautiously evaluate their failback criticality and determine the appropriate timing. If the failback is not strictly time-sensitive or immediately critical to your business operations, postponing the procedure until the next business day will minimize potential transition risks. If you experience additional issues or have questions, please open a support case via Snowflake Community. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 07:20 UTC October 20, 2025 Incident end time: 21:18 UTC October 20, 2025 Preliminary root cause: A third-p
Timeline
- Resolved · Oct 21, 01:57 UTC
Current status: We've coordinated with our third-party cloud platform to implement the fix for this issue, and we've monitored the environment to confirm that service was restored. We have observed stable and healthy performance across the Snowflake service since 21:18 UTC. Failback operations to origin regions may now be initiated by customers who previously failed over. In light of the recent operational severity, we provide guidance for customers to cautiously evaluate their failback criticality and determine the appropriate timing. If the failback is not strictly time-sensitive or immediately critical to your business operations, postponing the procedure until the next business day will minimize potential transition risks. If you experience additional issues or have questions, please open a support case via Snowflake Community. Customer experience: Customers hosted in the specified regions may have been unable to access or use multiple core Snowflake services and features. Affected users may have been unable to sign in, execute queries, or manage data. Incident start time: 07:20 UTC October 20, 2025 Incident end time: 21:18 UTC October 20, 2025 Preliminary root cause: A third-party cloud platform experienced networking issues, which were traced to the failure of an underlying internal subsystem responsible for monitoring the health of its network load balancers. This ultimately caused access issues for Snowflake services and features, impacting customers hosted in the spe
More from Snowflake
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1404:48 UTC | INC20000217 | major | 1h 21m |
| Sep 1107:18 UTC | INC20000213 | critical | 6h 1m |
| Sep 921:53 UTC | INC20000211 | critical | 1h 58m |
| Sep 407:34 UTC | INC20000199 | critical | 2h 36m |
| Sep 109:58 UTC | INC20000190 | major | 3h 52m |
| Aug 3117:20 UTC | INC20000188 | critical | 2h 24m |
Also caused by third-party dependency
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 1609:48 UTC | Support Portal Service Disruption | minor | 11h 21m | |
| Sep 1608:31 UTC | Support Helpdesk Availability Issues | minor | 6h 27m | |
| Sep 417:03 UTC | Degradation of Hosted Grafana in US Central Region | major | 3h 39m | |
| Sep 416:05 UTC | Elevated Linux worker queue times | major | 15h 4m | |
| Sep 115:25 UTC | Investigating issues in US Central (prod-us-central-0, prod-us-central-5) | minor | 4h 54m | |
| Aug 3106:26 UTC | Packet loss in ORD | minor | 1h 44m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.