INC20000150
Snowflake reports degraded service on Virtual Warehouses and Snowpark Container Services in GCP US Central 1 (Iowa). Snowflake identified the issue and states that virtual warehouse performance is stable with the impact mitigated. Snowpark Container Services continues to improve, and workloads that need new or resumed capacity may stay affected.
A language model wrote this summary from the updates of Snowflake.
State
Identified
Started
65 d ago
2026-08-28 00:07 UTC
Ongoing for
65 days
Worst impact
Degraded
Timeline
1 updateIdentified
65 days 100%
Updates
Times in UTCAs posted by Snowflake
Current status: We continue to see stable virtual warehouse performance and consider the impact mitigated. Additional information about virtual warehouse impact is available in previous updates. Snowpark Container Services continues to show improvement. We expect to receive additional capacity within the next several days and will validate service readiness as it becomes available. Until then, workloads that require new or resumed capacity may remain affected. We will provide another update within seven days, or sooner if there is a significant change. Customer experience: Customers using Snowpark Container Services may still experience delays, timeouts, or failures when starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. Existing workloads generally continue to run normally; the remaining risk is concentrated in workloads that require new or resumed capacity. ETA: We expect additional capacity within the next several days. We will v
Affected components
4Snowflake in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
66
Median duration
Not enough data
This incident
Not comparable
Follow Snowflake
Your coding agent knows when Snowflake is down, and tells you when a failure is theirs, not yours. You can also get Snowflake incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "snowflake" and tell me if Snowflake has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=snowflake/feed subscribe https://outages.cc/feed.xml?providers=snowflakeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane