← Live dashboard

INC20000129

ResolvedcriticalOfficial source confirmedSpecific component onlyFirst recorded update Aug 3, 2026, 02:11 PM · Resolved Aug 3, 2026, 08:58 PM

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).

Snowflake live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Snowflake now? Check the current status

Affected services

Virtual Warehouses

Updates (9)

  1. Aug 11, 2026, 01:02 AM
    INC20000129

    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).

    Snowflake ↗
  2. Aug 3, 2026, 08:58 PM
    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 i

    Snowflake ↗
  3. Aug 3, 2026, 06:15 PM
    INC20000129

    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

    Snowflake ↗
  4. Aug 3, 2026, 05:17 PM
    INC20000129

    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

    Snowflake ↗
  5. Aug 3, 2026, 04:42 PM
    INC20000129

    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 a

    Snowflake ↗
  6. Aug 3, 2026, 03:46 PM
    INC20000129

    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 r

    Snowflake ↗
  7. Aug 3, 2026, 03:15 PM
    INC20000129

    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 runni

    Snowflake ↗
  8. Aug 3, 2026, 02:39 PM
    INC20000129

    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 usin

    Snowflake ↗
  9. Aug 3, 2026, 02:11 PM
    INC20000129

    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

    Snowflake ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Snowflake's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.