Skip to content
Snowflake · Data and observabilityOct 20, 2025, 08:36 UTC

INC0145263

CriticalDependencyUpdated 20h ago
Oct 20, 08:36 UTCOct 21, 01:57 UTC
Duration
17h 21m
Impact
Critical
Root cause
Dependency
Snowflake, 90 days
22 incidents
Affected
Not listed by the vendor.
Status page

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

  1. 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
StartedIncidentDuration
Sep 1404:48 UTCINC200002171h 21m
Sep 1107:18 UTCINC200002136h 1m
Sep 921:53 UTCINC200002111h 58m
Sep 407:34 UTCINC200001992h 36m
Sep 109:58 UTCINC200001903h 52m
Aug 3117:20 UTCINC200001882h 24m

Also caused by third-party dependency

All
StartedIncidentDuration
Sep 1609:48 UTCSupport Portal Service DisruptionDigitalOcean11h 21m
Sep 1608:31 UTCSupport Helpdesk Availability IssuesCloudflare6h 27m
Sep 417:03 UTCDegradation of Hosted Grafana in US Central RegionGrafana Labs3h 39m
Sep 416:05 UTCElevated Linux worker queue timesExpo15h 4m
Sep 115:25 UTCInvestigating issues in US Central (prod-us-central-0, prod-us-central-5)Grafana Labs4h 54m
Aug 3106:26 UTCPacket loss in ORDFly.io1h 44m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.