Snowflake reported this critical-impact incident on its official status page on Aug 3, 2026, 14:11 UTC. It was resolved after 6h 47m.
Right now Snowflake is degraded. Live Snowflake status →
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/INC20000129](https://community.snowflake.com/s/article/INC20000129).
Current status: We've confirmed that this issue has been resolved, and we have monitored the environment to confirm that the affected functionality is now working as expected. 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 start, resume, or manage virtual warehouses. The impact occurred during the periods of 13:33 to 15:20 UTC, and 16:05 to 16:36 UTC on August 03, 2026. Virtual warehouses may have appeared as stuck in the associated state. Existing warehouses that were already running may have been unaffected. Customers may also have seen queued or delayed queries for workloads running on affected warehouses. Additionally, some serverless tasks may have experienced residual queuing or failures until the backlog of requests which accumulated during the impact windows was processed. Incident start time: 13:33
Current status: We've confirmed that our service has remained stable since 16:35 UTC, following our mitigation action; however, we're continuing to monitor the environment to confirm that the affected functionality continues to work as expected. Customer experience: Customers hosted in the specified region may have been unable to start, resume, or manage virtual warehouses. Virtual warehouses may have appeared as stuck in the associated state. Existing warehouses that were already running may have been unaffected. Customers may also have seen queued or delayed queries for workloads running on affected warehouses. Workaround: There were no available workarounds for this issue. Incident start time: 13:35 UTC August 03, 2026 Incident end time: 16:36 UTC August 03, 2026 Preliminary root cause: A Cloud Services component responsible for virtual warehouse management became unhealthy. This caused failures in the internal workflows used to allocate and manage compute resources for warehous
Current status: We have identified that the previously affected Cloud Services component became unhealthy again, which is preventing virtual warehouses from starting or resuming. We've implemented an additional fix and we're continuing to monitor to confirm that we have fully recovered. We'll provide another update within 60 minutes. Customer experience: Customers hosted in the specified region may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that were already running may be unaffected. Customers may also see queued or delayed queries for workloads running on affected warehouses. Workaround: There were no available workarounds for this issue. Incident start time: 13:35 UTC August 03, 2026 Incident end time: 16:36 UTC August 03, 2026 Preliminary root cause: An internal system component became unhealthy, causing virtual warehouse management operations to fail, resulting in customer impact
Current status: While we observed a period of recovery, our telemetry identified a recurrence of impact. We are implementing a mitigation to restore warehouse functionality, and we’ll provide another update within 30 minutes. Customer experience: Customers hosted in the specified region may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that were already running may be unaffected. Customers may also see queued or delayed queries for workloads running on affected warehouses. ETA: An ETA is not yet available. We'll provide one as soon as possible. Workaround: There are no available workarounds for this issue. Incident start time: 13:35 UTC August 03, 2026
Current status: We have identified an unhealthy Cloud Services component that is preventing virtual warehouses from starting or resuming. We are implementing a fix and will continue to monitor to confirm that we have fully recovered. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Customers may also see queued or delayed queries for workloads running on affected warehouses. ETA: We are actively monitoring recovery, and customers should be starting to see improvement. Workaround: There were no available workarounds for this issue. Incident start time: 13:35 UTC August 03, 2026 Incident end time: 15:20 UTC August 03, 2026 Preliminary root cause: An internal system component became unhealthy, causing virtual warehouse management operat
Current status: We have so far not identified any recent changes directly contributing to this problem and are currently focused on investigating performance issues affecting the system that controls virtual warehouse management. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Customers may also see queued or delayed queries for workloads running on affected warehouses. 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: 13:35 UTC August 03, 2026
Current status: We're continuing to investigate the issue with Snowflake Data Cloud, and we're analyzing recent changes and telemetry to determine a mitigation plan. We'll provide another update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. 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. Workaround: There are currently no available workarounds for this issue. Incident start time: 13:35 UTC August 03, 2026
Current status: We're investigating an issue with Snowflake Data Cloud. We'll provide an update within 30 minutes. Customer experience: Customers hosted in the specified regions may be unable to start, resume, or manage virtual warehouses. Virtual warehouses may appear as stuck in the associated state. Existing warehouses that are already running may be unaffected. Incident start time: 13:35 UTC August 03, 2026
Our 5-minute checks didn't record a change in Snowflake's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Snowflake reported 23 incidents in the last 90 days, 18 of them major or critical. A typical incident lasted 1h 56m. See Snowflake's uptime and incident history