Skip to main content
Snowflake logo

Is Snowflake Down?

No — Snowflake is up
Snowflake's status page
No service-wide problems · 2 of 676 locations reporting problems
FlareWarden checks
Website reachable · 8 of 8 regions · 461 ms

Right now

The verdict is the worse of these two. How we decide

Snowflake's status page

status.snowflake.com · read · checked every 3 minutes

No service-wide problems
minor identified since

INC20000150

Current status: Virtual warehouse performance remains stable. For Snowpark Container Services, additional capacity has not yet become available, later than the end-of-October timeframe previously communicated. We now expect the capacity to become available by the end of next week. We will validate service readiness once it arrives and share a more substantive update. 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 to be available by November 13, 2026. Workaround: Customers running Notebooks may continue using a warehouse-based runtime where feasible. There is no general workaround for Snowpark Container Services compute-pool capacity issues; customers experiencing specific failures should contact Snowflake Support. Impact start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses.

Latest update 24 minutes ago

Snowflake's components, as its status page reports them
ComponentStatus
Databases, Tables, and ViewsOperational
Virtual WarehousesOperational
Data Loading and UnloadingOperational
ApplicationsOperational
Snowpark Container ServicesOperational
Security and Privacy FeaturesOperational
AI and MLOperational
Organization and Account ManagementOperational
Listings and CollaborationOperational
Alerts and NotificationsOperational
Developer ToolsOperational
Business ContinuityOperational
676 locations 2 reporting problems
  • Virtual Warehouses · Degraded Performance
  • Snowpark Container Services · Degraded Performance

Locations change the verdict only once a quarter of them are in trouble.

FlareWarden checks

snowflake.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
461 ms
Checked

By region

  • Chicago reachable, 186 ms
  • Johannesburg reachable, 456 ms
  • London reachable, 247 ms
  • Los Angeles reachable, 290 ms
  • San Jose reachable, 330 ms
  • Singapore reachable, 854 ms
  • Sydney reachable, 856 ms
  • Tokyo reachable, 476 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Chicago6 ms1 ms8 ms169 ms
Johannesburg82 ms1 ms5 ms439 ms
London6 ms3 ms12 ms227 ms
Los Angeles72 ms3 ms13 ms270 ms
San Jose32 ms3 ms15 ms298 ms
Singapore351 ms2 ms12 ms840 ms
Sydney365 ms1 ms5 ms846 ms
Tokyo106 ms1 ms10 ms464 ms
We check that snowflake.com loads, not every feature behind it. Test it yourself

History

Incidents Snowflake reported

Since Oct 22, 15 days · from status.snowflake.com

Incidents
5
Major or critical
1
Median to resolve
4h 14m
  1. INC20000321

    minor ·

    lasted 3h 25m
  2. INC20000319

    minor ·

    lasted 21h 27m
  3. INC20000301

    critical ·

    lasted 5h 3m
  4. INC20000299

    minor ·

    lasted 50m
  5. INC20000150

    minor ·

    Ongoing

Snowflake website availability

Measured by FlareWarden · snowflake.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
380ms

Last 30 days

91-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 31 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks, 1 incident
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 24 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of snowflake.com from multiple regions every 6 hours. Snowflake's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Snowflake outage FAQ

Is Snowflake down or is my warehouse suspended?
A suspended warehouse resumes automatically on the next query and adds a short delay rather than failing. An incident produces errors or queries that never return. Check status.snowflake.com for your specific cloud region first. If the region is healthy, look at warehouse sizing and queuing, which explain far more slow queries than outages do.
Which region should I check on the Snowflake status page?
The one your account is deployed in, which is visible in your account URL and in the console. Snowflake lists dozens of regions across AWS, Azure and GCP, and incidents are usually confined to one. Reading the overall page rather than your region is the most common way to misdiagnose a Snowflake problem in either direction.
Will a failed data load leave partial data in my tables?
It can, which is why resubmitting blindly is risky. Loads that fail partway may have committed some files and not others. Check the load history for what actually landed before rerunning, and prefer idempotent loading patterns that tolerate a repeat. Data Loading and Unloading is a separate status component, so it can fail while queries succeed.
Why do my dashboards fail when the Snowflake console works?
The console and the query path are not the same thing. Serving the web interface is far lighter than running a query on a virtual warehouse, so the console frequently loads during an incident that stops compute entirely. Check the Virtual Warehouses component rather than concluding from a working console that Snowflake is healthy.
Do Snowflake outages affect data already stored?
Stored data is not altered by an availability incident; it becomes temporarily unreachable. Snowflake separates storage from compute, so a compute-side problem leaves the underlying data intact and queries succeed again once warehouses recover. The practical risk is to pipelines that were mid-run, not to tables that were already written.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Snowflake itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Snowflake goes down

We check Snowflake every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required