Skip to main content
Snowflake logo

Is Snowflake Down?

No — Snowflake is up

Reachable from all 8 checked regions

Average response time: 575ms

Last checked · checks run every 6 hours

Official status page: https://status.snowflake.com

Snowflake uptime

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

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 8 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

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

gru
574ms
DNS 20ms TCP 1ms TLS 6ms TTFB 551ms
iad
346ms
DNS 27ms TCP 13ms TLS 4ms TTFB 237ms
jnb
823ms
DNS 274ms TCP 0ms TLS 10ms TTFB 822ms
lax
269ms
DNS 11ms TCP 0ms TLS 14ms TTFB 259ms
lhr
327ms
DNS 20ms TCP 3ms TLS 6ms TTFB 320ms
nrt
1032ms
DNS 63ms TCP 0ms TLS 8ms TTFB 752ms
ord
377ms
DNS 28ms TCP 24ms TLS 20ms TTFB 365ms
sin
853ms
DNS 123ms TCP 4ms TLS 16ms TTFB 843ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

Databricks
Databricks
MongoDB Atlas
MongoDB Atlas
AWS
AWS
Datadog
Datadog

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 — 8 of them answered the most recent check.
  • 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. 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, and let it override us in both directions.

Get alerted when Snowflake goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required