Skip to content

Outage tracker / Snowflake

Is Snowflake down?

Short linkrlup.io/down/snowflake

I'm having a problem

Vendor lists an old incident, not shown as liveWhat Snowflake reports

Snowflake still lists an incident opened on 2026-08-28, last updated 2026-10-22; it has been open past 72 hours, so we do not show it as live.

As of the last successful poll, 2026-10-22 21:48 UTC.

Snowflake's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 13 minutes ago

Our checks of Snowflake pass from all 10 regions we check.

As of Oct 22, 2026, 9:39 PM UTC, RealUptime's checks of Snowflake passed in all 10 regions that returned a reading.

Front-door checks

our check readinglive · checked Oct 22, 2026, 9:39 PM UTC
US-East58 msChecks passing
US-West75 msChecks passing
Europe73 msChecks passing
Asia-Pacific276 msChecks passing
US-Central130 msChecks passing
Canada228 msChecks passing
UK89 msChecks passing
Southeast Asia123 msChecks passing
Australia170 msChecks passing
South America191 msChecks passing
their status pagetheir claim, not our reading

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

from Snowflake's own status page, checked Sep 17, 2026, 10:47 PM UTC
Snowflake's status page reports Partially Degraded Service. Our checks of Snowflake currently pass with normal latency. Our checks currently pass from all 10 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 the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

Snowflake's own component breakdown, as they publish it (our last read of their page failed, so this is the previous reading)

  • 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 WarehousesDegraded performance
  • 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
365msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 666ms2026-09-24 UTC: p95 422ms2026-09-25 UTC: p95 366ms2026-09-26 UTC: p95 470ms2026-09-27 UTC: p95 410ms2026-09-28 UTC: p95 398ms2026-09-29 UTC: p95 533ms2026-09-30 UTC: p95 515ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 491ms2026-10-03 UTC: p95 447ms2026-10-04 UTC: p95 647ms2026-10-05 UTC: p95 428ms2026-10-06 UTC: p95 448ms2026-10-07 UTC: p95 228ms2026-10-08 UTC: p95 339ms2026-10-09 UTC: p95 341ms2026-10-10 UTC: p95 354ms2026-10-11 UTC: p95 366ms2026-10-12 UTC: p95 302ms2026-10-13 UTC: p95 323ms2026-10-14 UTC: p95 194ms2026-10-15 UTC: p95 201ms2026-10-16 UTC: p95 540ms2026-10-17 UTC: p95 931ms2026-10-18 UTC: p95 898ms2026-10-19 UTC: p95 243ms2026-10-20 UTC: p95 221ms2026-10-21 UTC: p95 399ms2026-10-22 UTC: p95 365ms
Sep 23Oct 7Oct 22
US-West
240msp95 · 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-09-23 UTC: p95 572ms2026-09-24 UTC: p95 312ms2026-09-25 UTC: p95 293ms2026-09-26 UTC: p95 785ms2026-09-27 UTC: p95 948ms2026-09-28 UTC: p95 972ms2026-09-29 UTC: p95 840ms2026-09-30 UTC: p95 924ms2026-10-01 UTC: p95 790ms2026-10-02 UTC: p95 715ms2026-10-03 UTC: p95 681ms2026-10-04 UTC: p95 717ms2026-10-05 UTC: p95 733ms2026-10-06 UTC: p95 583ms2026-10-07 UTC: p95 579ms2026-10-08 UTC: p95 680ms2026-10-09 UTC: p95 632ms2026-10-10 UTC: p95 672ms2026-10-11 UTC: p95 745ms2026-10-12 UTC: p95 946ms2026-10-13 UTC: p95 880ms2026-10-14 UTC: p95 393ms2026-10-15 UTC: p95 889ms2026-10-16 UTC: p95 256ms2026-10-17 UTC: p95 661ms2026-10-18 UTC: p95 716ms2026-10-19 UTC: p95 394ms2026-10-20 UTC: p95 175ms2026-10-21 UTC: p95 407ms2026-10-22 UTC: p95 240ms
Sep 23Oct 7Oct 22
Europe
247msp95 · 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-09-23 UTC: p95 303ms2026-09-24 UTC: p95 177ms2026-09-25 UTC: p95 163ms2026-09-26 UTC: p95 171ms2026-09-27 UTC: p95 262ms2026-09-28 UTC: p95 294ms2026-09-29 UTC: p95 173ms2026-09-30 UTC: p95 240ms2026-10-01 UTC: p95 184ms2026-10-02 UTC: p95 177ms2026-10-03 UTC: p95 178ms2026-10-04 UTC: p95 122ms2026-10-05 UTC: p95 171ms2026-10-06 UTC: p95 181ms2026-10-07 UTC: p95 381ms2026-10-08 UTC: p95 378ms2026-10-09 UTC: p95 309ms2026-10-10 UTC: p95 280ms2026-10-11 UTC: p95 316ms2026-10-12 UTC: p95 186ms2026-10-13 UTC: p95 341ms2026-10-14 UTC: p95 348ms2026-10-15 UTC: p95 504ms2026-10-16 UTC: p95 344ms2026-10-17 UTC: p95 417ms2026-10-18 UTC: p95 419ms2026-10-19 UTC: p95 291ms2026-10-20 UTC: p95 274ms2026-10-21 UTC: p95 305ms2026-10-22 UTC: p95 247ms
Sep 23Oct 7Oct 22
Asia-Pacific
1.6sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 750ms2026-09-24 UTC: p95 478ms2026-09-25 UTC: p95 550ms2026-09-26 UTC: p95 817ms2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 948ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 985ms2026-10-01 UTC: p95 851ms2026-10-02 UTC: p95 807ms2026-10-03 UTC: p95 842ms2026-10-04 UTC: p95 728ms2026-10-05 UTC: p95 969ms2026-10-06 UTC: p95 876ms2026-10-07 UTC: p95 364ms2026-10-08 UTC: p95 380ms2026-10-09 UTC: p95 389ms2026-10-10 UTC: p95 991ms2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 678ms2026-10-13 UTC: p95 554ms2026-10-14 UTC: p95 397ms2026-10-15 UTC: p95 459ms2026-10-16 UTC: p95 567ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 406ms2026-10-20 UTC: p95 289ms2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
US-Central
276msp95 · latest
500ms250ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 319ms2026-09-24 UTC: p95 430ms2026-09-25 UTC: p95 398ms2026-09-26 UTC: p95 290ms2026-09-27 UTC: p95 242ms2026-09-28 UTC: p95 175ms2026-09-29 UTC: p95 216ms2026-09-30 UTC: p95 232ms2026-10-01 UTC: p95 191ms2026-10-02 UTC: p95 221ms2026-10-03 UTC: p95 253ms2026-10-04 UTC: p95 282ms2026-10-05 UTC: p95 255ms2026-10-06 UTC: p95 265ms2026-10-07 UTC: p95 259ms2026-10-08 UTC: p95 300ms2026-10-09 UTC: p95 423ms2026-10-10 UTC: p95 397ms2026-10-11 UTC: p95 358ms2026-10-12 UTC: p95 257ms2026-10-13 UTC: p95 259ms2026-10-14 UTC: p95 316ms2026-10-15 UTC: p95 249ms2026-10-16 UTC: p95 271ms2026-10-17 UTC: p95 314ms2026-10-18 UTC: p95 311ms2026-10-19 UTC: p95 284ms2026-10-20 UTC: p95 250ms2026-10-21 UTC: p95 304ms2026-10-22 UTC: p95 276ms
Sep 23Oct 7Oct 22
Canada
624msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 296ms2026-09-24 UTC: p95 321ms2026-09-25 UTC: p95 322ms2026-09-26 UTC: p95 290ms2026-09-27 UTC: p95 276ms2026-09-28 UTC: p95 273ms2026-09-29 UTC: p95 272ms2026-09-30 UTC: p95 275ms2026-10-01 UTC: p95 254ms2026-10-02 UTC: p95 249ms2026-10-03 UTC: p95 242ms2026-10-04 UTC: p95 177ms2026-10-05 UTC: p95 263ms2026-10-06 UTC: p95 199ms2026-10-07 UTC: p95 332ms2026-10-08 UTC: p95 340ms2026-10-09 UTC: p95 393ms2026-10-10 UTC: p95 368ms2026-10-11 UTC: p95 372ms2026-10-12 UTC: p95 326ms2026-10-13 UTC: p95 227ms2026-10-14 UTC: p95 264ms2026-10-15 UTC: p95 220ms2026-10-16 UTC: p95 235ms2026-10-17 UTC: p95 209ms2026-10-18 UTC: p95 208ms2026-10-19 UTC: p95 421ms2026-10-20 UTC: p95 242ms2026-10-21 UTC: p95 374ms2026-10-22 UTC: p95 624ms
Sep 23Oct 7Oct 22
UK
165msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 267ms2026-09-24 UTC: p95 260ms2026-09-25 UTC: p95 243ms2026-09-26 UTC: p95 298ms2026-09-27 UTC: p95 289ms2026-09-28 UTC: p95 334ms2026-09-29 UTC: p95 446ms2026-09-30 UTC: p95 273ms2026-10-01 UTC: p95 452ms2026-10-02 UTC: p95 205ms2026-10-03 UTC: p95 218ms2026-10-04 UTC: p95 174ms2026-10-05 UTC: p95 201ms2026-10-06 UTC: p95 183ms2026-10-07 UTC: p95 179ms2026-10-08 UTC: p95 201ms2026-10-09 UTC: p95 315ms2026-10-10 UTC: p95 440ms2026-10-11 UTC: p95 452ms2026-10-12 UTC: p95 194ms2026-10-13 UTC: p95 157ms2026-10-14 UTC: p95 145ms2026-10-15 UTC: p95 163ms2026-10-16 UTC: p95 133ms2026-10-17 UTC: p95 120ms2026-10-18 UTC: p95 122ms2026-10-19 UTC: p95 181ms2026-10-20 UTC: p95 164ms2026-10-21 UTC: p95 195ms2026-10-22 UTC: p95 165ms
Sep 23Oct 7Oct 22
Southeast Asia
404msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 920ms2026-09-24 UTC: p95 744ms2026-09-25 UTC: p95 700ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 687ms2026-09-28 UTC: p95 713ms2026-09-29 UTC: p95 735ms2026-09-30 UTC: p95 568ms2026-10-01 UTC: p95 356ms2026-10-02 UTC: p95 419ms2026-10-03 UTC: p95 413ms2026-10-04 UTC: p95 458ms2026-10-05 UTC: p95 385ms2026-10-06 UTC: p95 450ms2026-10-07 UTC: p95 502ms2026-10-08 UTC: p95 377ms2026-10-09 UTC: p95 565ms2026-10-10 UTC: p95 384ms2026-10-11 UTC: p95 423ms2026-10-12 UTC: p95 423ms2026-10-13 UTC: p95 367ms2026-10-14 UTC: p95 538ms2026-10-15 UTC: p95 440ms2026-10-16 UTC: p95 456ms2026-10-17 UTC: p95 709ms2026-10-18 UTC: p95 356ms2026-10-19 UTC: p95 461ms2026-10-20 UTC: p95 577ms2026-10-21 UTC: p95 911ms2026-10-22 UTC: p95 404ms
Sep 23Oct 7Oct 22
Australia
301msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 583ms2026-09-24 UTC: p95 387ms2026-09-25 UTC: p95 399ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 768ms2026-10-02 UTC: p95 400ms2026-10-03 UTC: p95 460ms2026-10-04 UTC: p95 512ms2026-10-05 UTC: p95 564ms2026-10-06 UTC: p95 383ms2026-10-07 UTC: p95 271ms2026-10-08 UTC: p95 297ms2026-10-09 UTC: p95 269ms2026-10-10 UTC: p95 495ms2026-10-11 UTC: p95 516ms2026-10-12 UTC: p95 269ms2026-10-13 UTC: p95 288ms2026-10-14 UTC: p95 259ms2026-10-15 UTC: p95 236ms2026-10-16 UTC: p95 921ms2026-10-17 UTC: p95 987ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 235ms2026-10-20 UTC: p95 243ms2026-10-21 UTC: p95 538ms2026-10-22 UTC: p95 301ms
Sep 23Oct 7Oct 22
South America
432msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 541ms2026-09-24 UTC: p95 369ms2026-09-25 UTC: p95 576ms2026-09-26 UTC: p95 925ms2026-09-27 UTC: p95 970ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 796ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 659ms2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 891ms2026-10-06 UTC: p95 808ms2026-10-07 UTC: p95 368ms2026-10-08 UTC: p95 297ms2026-10-09 UTC: p95 386ms2026-10-10 UTC: p95 637ms2026-10-11 UTC: p95 632ms2026-10-12 UTC: p95 380ms2026-10-13 UTC: p95 407ms2026-10-14 UTC: p95 418ms2026-10-15 UTC: p95 381ms2026-10-16 UTC: p95 555ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 925ms2026-10-19 UTC: p95 461ms2026-10-20 UTC: p95 475ms2026-10-21 UTC: p95 777ms2026-10-22 UTC: p95 432ms
Sep 23Oct 7Oct 22

Check your own site while you wait on Snowflake

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.

Email me when Snowflake reports an incident on its status page, and again when it reports it resolved.

Get an email when Snowflake reports an incident

Email me when Snowflake reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Snowflake's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 58msstatus code: 200checked: Oct 22, 2026, 9:35 PM 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
      Checks passinglatency: 75msstatus code: 200checked: Oct 22, 2026, 9:37 PM 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.
    • US-Central
      Checks passinglatency: 130msstatus code: 200checked: Oct 22, 2026, 9:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Snowflake normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 228msstatus code: 200checked: Oct 22, 2026, 9:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Snowflake normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 191msstatus code: 200checked: Oct 22, 2026, 9:36 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Snowflake normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 73msstatus code: 200checked: Oct 22, 2026, 9:36 PM 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.
    • UK
      Checks passinglatency: 89msstatus code: 200checked: Oct 22, 2026, 9:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Snowflake normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 276msstatus code: 200checked: Oct 22, 2026, 9:39 PM 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.
    • Southeast Asia
      Checks passinglatency: 123msstatus code: 200checked: Oct 22, 2026, 9:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Snowflake normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 170msstatus code: 200checked: Oct 22, 2026, 9:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Snowflake normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

INC20000301, 5h 3mdeclared on their status page2026-10-21
INC20000299, 51mdeclared on their status page2026-10-21
INC20000294, 8h 52mdeclared on their status page2026-10-20
INC20000290, 44mdeclared on their status page2026-10-19
INC20000287, 29mdeclared on their status page2026-10-16
INC20000277, 24h 4mdeclared on their status page2026-10-14
INC20000263, 1h 13mdeclared on their status page2026-10-06
INC20000239, 1h 1mdeclared on their status page2026-09-27

check 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 check readings and Snowflake's own claim at the time, side by side.

Full check history for Snowflake: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Snowflake uptime by RealUptime's checksLive, from this page's own readings.
[![Snowflake uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Snowflake down?", https://realuptime.io/outages/snowflake. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primary
https://app.snowflake.com/
secondary
https://status.snowflake.com/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: app.snowflake.com

RealUptime is not affiliated with Snowflake; the name identifies what we checked, and nothing here speaks for Snowflake's own team. We send a single web request to Snowflake from 10 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. What we check for Snowflake is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.

Related services

AWS (Amazon Web Services)AkamaiAmplitudeAnthropicAuth0