Is Snowflake Down?
Reachable from all 8 checked regions
Average response time: 393ms
Last checked · checks run every 6 hours
Official status page: https://status.snowflake.com
INC20000150
Current status: We've taken additional steps with our warehouse team to reduce provisioning latencies for virtual warehouses, and we've observed some improvement in provisioning latencies as a result. Resource availability remains variable and correlated to overall demand, with some intermittent delays occurring during high-volume times. We're continuing to work closely with our warehouse team to maintain available capacity and keep provisioning times low. Our third-party cloud platform provider has indicated that the additional compute capacity remains on track, and we're continuing to coordinate with them to restore the needed capacity. We'll provide another update within 7 days. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected. Additionally, starting from 04:00 UTC September 04, 2026, customers hosted in the specified region with workloads on second generation (Gen2) warehouses may experience delays or intermittent failures when resuming or starting virtual warehouses. This may result in longer than expected query run times or delays in completing data pipelines. Warehouses that are already running are largely unaffected. ETA: Based on information from our third-party cloud platform provider, we expect additional compute resources to become available in the specified region by mid-October. We'll provide an updated ETA as we receive more information. Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. For customers experiencing impact to virtual warehouses, and who have already performed a failover, we recommend remaining in the alternate region until we have received additional capacity allocation from the third-party provider. Customers who are continuing to experience impact to virtual warehouses may see additional relief by migrating workloads to first generation (Gen1) warehouses, which remain less impacted by this issue. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform provider is experiencing constrained compute capacity, affecting compute resource provisioning, and causing limited availability of compute resources as well as delays and intermittent failures when resuming or starting virtual warehouses in the specified region.
A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Snowflake fail from enough regions to rule out probe noise.
Snowflake uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
32-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Snowflake does
Snowflake is a cloud data warehouse running on AWS, Azure and Google Cloud, separating storage from the virtual warehouses that compute over it. Analytics, dashboards and data pipelines sit downstream of it, so an incident tends to surface as reports that will not refresh and overnight jobs that failed silently.
What an outage looks like
Queries hang in the queue or fail with warehouse errors rather than returning results. Virtual warehouses will not resume from suspension. Data loading and unloading jobs fail, so pipelines break at the ingest step and leave partial datasets. Dashboards built on Snowflake time out, and the web console may load while queries against it do not.
What to do about it
Check status.snowflake.com and find your deployment: Snowflake reports per cloud provider and per region (AWS, Azure and GCP, each with many regions), so a global glance is misleading. Components such as Virtual Warehouses, Data Loading and Unloading, and Databases are tracked separately. Avoid resubmitting large loads until the component recovers, since partial loads are harder to reconcile than none.
Is it down for everyone, or just you?
If this page says Snowflake is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.
Related services
Snowflake outage FAQ
Is Snowflake down or is my warehouse suspended?
Which region should I check on the Snowflake status page?
Will a failed data load leave partial data in my tables?
Why do my dashboards fail when the Snowflake console works?
Do Snowflake outages affect data already stored?
How we measure this
- We request Snowflake's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Snowflake publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Snowflake goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring