Skip to content

Outage tracker / Snowflake

Is Snowflake down?

I'm having a problem

Partially degradedchecked 2 minutes ago

Snowflake is answering our probes, but running at least 4x its 7-day median from Europe. The rest of the regions we check answered at their usual speed.

Functional endpoints verified

No outage recorded in the 14 days we have measured Snowflake (since Aug 20, 2026).

Snowflake reports an active incident: "INC20000150" (minor incident, since Aug 28, 2026, 12:07 AM UTC). That is their claim, not our measurement: our probes are currently reaching Snowflake, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Sep 3, 2026, 1:27 AM UTC
US-East276 msOperational
US-West43 msOperational
Europe317 msDegraded
Asia-Pacific710 msOperational
their status pagetheir claim, not our reading

Snowflake reports: Minor incident (“Partially Degraded Service”)

from Snowflake's own status page, checked Sep 3, 2026, 12:26 AM UTC

Snowflake reports an active incident: INC20000150 (minor incident, since Aug 28, 2026, 12:07 AM UTC)

Snowflake's status page reports Partially Degraded Service. Our probes are currently reaching Snowflake successfully with normal latency. RealUptime's independent checks are currently succeeding from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

Snowflake's own component breakdown, as they publish it

  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Databases, Tables, and ViewsOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational
  • Virtual WarehousesOperational

These are Snowflake's components, named and scored by Snowflake. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Snowflake's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Snowflake response time, by region

US-East
254msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 423ms2026-08-21 UTC: p95 244ms2026-08-22 UTC: p95 456ms2026-08-23 UTC: p95 615ms2026-08-24 UTC: p95 542ms2026-08-25 UTC: p95 231ms2026-08-26 UTC: p95 396ms2026-08-27 UTC: p95 387ms2026-08-28 UTC: p95 228ms2026-08-29 UTC: p95 270ms2026-08-30 UTC: p95 235ms2026-08-31 UTC: p95 260ms2026-09-01 UTC: p95 303ms2026-09-02 UTC: p95 300ms2026-09-03 UTC: p95 254ms
Aug 5Aug 19Sep 3
US-West
52msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 383ms2026-08-21 UTC: p95 394ms2026-08-22 UTC: p95 278ms2026-08-23 UTC: p95 261ms2026-08-24 UTC: p95 248ms2026-08-25 UTC: p95 234ms2026-08-26 UTC: p95 149ms2026-08-27 UTC: p95 362ms2026-08-28 UTC: p95 649ms2026-08-29 UTC: p95 642ms2026-08-30 UTC: p95 584ms2026-08-31 UTC: p95 522ms2026-09-01 UTC: p95 193ms2026-09-02 UTC: p95 380ms2026-09-03 UTC: p95 52ms
Aug 5Aug 19Sep 3
Europe
354msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 187ms2026-08-21 UTC: p95 177ms2026-08-22 UTC: p95 205ms2026-08-23 UTC: p95 290ms2026-08-24 UTC: p95 313ms2026-08-25 UTC: p95 172ms2026-08-26 UTC: p95 222ms2026-08-27 UTC: p95 252ms2026-08-28 UTC: p95 171ms2026-08-29 UTC: p95 155ms2026-08-30 UTC: p95 182ms2026-08-31 UTC: p95 156ms2026-09-01 UTC: p95 187ms2026-09-02 UTC: p95 707ms2026-09-03 UTC: p95 354ms
Aug 5Aug 19Sep 3
Asia-Pacific
414msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 480ms2026-08-21 UTC: p95 437ms2026-08-22 UTC: p95 822ms2026-08-23 UTC: p95 736ms2026-08-24 UTC: p95 611ms2026-08-25 UTC: p95 708ms2026-08-26 UTC: p95 693ms2026-08-27 UTC: p95 724ms2026-08-28 UTC: p95 653ms2026-08-29 UTC: p95 730ms2026-08-30 UTC: p95 907ms2026-08-31 UTC: p95 535ms2026-09-01 UTC: p95 622ms2026-09-02 UTC: p95 756ms2026-09-03 UTC: p95 414ms
Aug 5Aug 19Sep 3

Is it Snowflake, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Snowflake -- it cannot diagnose Snowflake's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 276msstatus code: 200checked: Sep 3, 2026, 1:03 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Snowflake normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 43msstatus code: 200checked: Sep 3, 2026, 1:05 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Snowflake normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Degradedlatency: 317msstatus code: 200checked: Sep 3, 2026, 1:27 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Snowflake normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 710msstatus code: 200checked: Sep 3, 2026, 1:08 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Snowflake normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionSnowflake is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionSnowflake is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionSnowflake is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionSnowflake is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionSnowflake is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionSnowflake is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Snowflake, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Snowflake yet, which is not evidence that nothing is wrong.

Recent outages

INC20000190, 3h 52mdeclared on their status page2026-09-01
INC20000188, 2h 24mdeclared on their status page2026-08-31
INC20000150declared on their status page2026-08-28
INC20000182, 1h 21mdeclared on their status page2026-08-27
INC20000175, 42mdeclared on their status page2026-08-25
INC20000173, 1h 41mdeclared on their status page2026-08-24
INC20000168, 1h 56mdeclared on their status page2026-08-20
INC20000163, 1h 54mdeclared on their status page2026-08-18

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Snowflake since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Snowflake covering any window you pick, with our measurements and Snowflake's own claim at the time, side by side.

Full availability history for Snowflake: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Snowflake, and again when they can reach it again. That is our own measurement from ten regions, not Snowflake's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Snowflake uptime measured by RealUptimeLive, from this page's own readings.
[![Snowflake uptime measured by RealUptime](https://realuptime.io/outages/snowflake/badge.svg?days=30)](https://realuptime.io/outages/snowflake)
<a href="https://realuptime.io/outages/snowflake"><img src="https://realuptime.io/outages/snowflake/badge.svg?days=30" alt="Snowflake uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Snowflake's SLA implies, from our measurement

At or above your target

We measured none of downtime for Snowflake over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Snowflake's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://status.snowflake.com/api/v2/status.json
secondary
https://status.snowflake.com/
RealUptime is not affiliated with Snowflake; the name identifies what we measured, and nothing here speaks for Snowflake's own team. We send a single web request to Snowflake from 4 regions on our own schedule and time the response. We do not see inside Snowflake's systems, do not use an account or real transaction, and are not the same signal Snowflake's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Snowflake is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Snowflake operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.