INC20000085

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 regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected.

Incident start time: 16:35 UTC July 11, 2026
Incident end time: 18:10 UTC July 11, 2026

Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup.

A root cause analysis (RCA) will be conducted and a summary will be shared on the Snowflake status page within 5 business days.

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 regions may have experienced delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that were already running may have been unaffected.

Incident start time: 16:35 UTC July 11, 2026
Incident end time: 18:10 UTC July 11, 2026

Preliminary root cause: Resource exhaustion in the binary download service caused delays when virtual warehouses attempted to download required software components during startup.

Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 1 hour.

Customer experience: Customers hosted in the specified regions may experience delays or intermittent failures when resuming or managing virtual warehouses. Existing warehouses that are already running may be unaffected.

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.

Incident start time: 16:30 UTC July 11, 2026