Snowflake status: is it down right now?
Our own check of snowflake.com from Europe and the US, every 3 minutes, with recent history.
snowflake.com responded. The page answered normally in 872 ms.
snowflake.com responded.
The page answered normally in 872 ms.
Checked (just now) from Europe and the US, automatic every 3 minutes.
Follow Snowflake's public website. Free 10-minute checks, no card. This does not check every feature.
Run a website? Check my website
This checks the response from snowflake.com. It does not test playback, login or every Snowflake feature.
- INC20000150 (identified)
Snowflake status history
Our own checks from Europe and the US. Green means every check passed, amber means some checks failed, red means most checks in that period failed.
Outages our checks detected
None since Oct 5. A problem has to fail two checks in a row before we record it.
Watch your site free
This page is for their outage. Your own site can fail the same way. Free plan: 3 monitors, SSL alerts, no card.
Watch your site freeabout this service
About Snowflake
Snowflake is a cloud data platform used by analytics teams to run warehouses, lakehouses, data sharing, and Snowpark ML workloads. It is deployed across AWS, Azure and GCP, and incidents are almost always scoped to a single deployment (e.g. AWS US-East-1 Virginia) rather than the whole product. Warehouse query failures, authentication outages, and Snowpipe ingestion delays are the most common user-visible symptoms. Teams feeding BI dashboards or ML feature stores from Snowflake notice immediately because Looker, Tableau and Mode queries start timing out.
The official Snowflake status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Independent monitoring catches issues faster.
outage patterns
What outages typically look like on Snowflake
Cloud platforms like Snowflake rarely fail in obvious, all-or-nothing ways. The more common pattern is regional degradation: one availability zone or geographic region runs at half capacity while the rest of the platform serves traffic normally. Status pages often show green because the aggregate health check is still passing, even when a customer's specific workload is degraded.
The live tool above checks the public snowflake.com endpoint from EU and US and compares status and response time. That can reveal a regional reachability problem, but it cannot prove that every Snowflake product, API, or customer workload is healthy. Use the provider status reference and test the specific workflow you depend on before drawing a broader conclusion.
Common signs Snowflake is having issues
- Temporarily unavailable pages or requests timing out during normal browsing
- Sustained response-time drift above the Snowflake baseline (usually a precursor to hard failures)
- TLS handshake delays during peak hours that resolve at quieter times
- Regional disparity: one geography returns errors while another stays healthy
What to do when Snowflake is degraded
If Snowflake appears degraded, compare the EU and US endpoint results, open the provider status reference, and test the exact region and workflow your system uses. Preserve failed request IDs and timestamps for support. If only one region fails, use an alternate region only when your own failover policy permits it.
monitor 24/7
Monitor Snowflake automatically.
Get independent alerts when the public Snowflake endpoint fails a confirmed check. Start free with 10-minute checks, or use Business or Agency for 60-second uptime checks.
10-minute free checks
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Email + push on Free
Paid plans unlock additional team and incident channels.
free forever · paid trials last 10 days
why independent monitoring
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Snowflake on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Snowflake uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.
Frequently asked questions
Is Snowflake down right now?
See the latest check of snowflake.com and its timestamp at the top of this page. If Snowflake is down, you can also check the official status page for extra context.
How do I check if Snowflake is having issues?
This page checks the public Snowflake endpoint from EU and US. You can also monitor that endpoint on a schedule and receive confirmed-failure alerts through the channels available on your plan. Test the exact provider feature you use for a complete diagnosis.
How can I get alerted when Snowflake goes down?
Set up a free monitor for snowflake.com on Visual Sentinel for 10-minute checks with email and push alerts. Paid plans add checks as fast as 60 seconds and more notification channels.
Where can I find Snowflake outage context?
The official Snowflake status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Independent monitoring catches issues faster. Visual Sentinel checks the public Snowflake endpoint independently from EU and US. Paid Business and Agency plans support 60-second uptime checks.
Why is my Snowflake warehouse showing green but queries are slow?
Warehouse status reflects availability, not performance. Load-related slowdowns, cold cache after auto-suspend, or contention from other queries on the same warehouse can cause slowness while the service itself is healthy.
Does a Snowflake incident in one region affect other regions?
Generally no. Snowflake deployments are isolated per region and per cloud. An AWS US-East-1 incident should not affect Azure West Europe. Multi-region customers with data replication may see replication lag during a source-region incident.