Skip to content

Outage tracker / Snowflake

Is Snowflake down?

I'm having a problem

Operationalchecked moments ago

We reached Snowflake from all 10 regions we check.

As of Oct 5, 2026, 8:16 PM UTC, Snowflake answered RealUptime's probes in all 10 regions that returned a reading.

Reachability verified

No outage recorded in the 46 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 Oct 5, 2026, 8:16 PM UTC
US-East364 msOperational
US-West247 msOperational
Europe181 msOperational
Asia-Pacific613 msOperational
US-Central50 msOperational
Canada202 msOperational
UK143 msOperational
Southeast Asia359 msOperational
Australia216 msOperational
South America488 msOperational
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 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 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 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 (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
440msp95 · 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-06 UTC: p95 244ms2026-09-07 UTC: p95 275ms2026-09-08 UTC: p95 334ms2026-09-09 UTC: p95 429ms2026-09-10 UTC: p95 249ms2026-09-11 UTC: p95 242ms2026-09-12 UTC: p95 216ms2026-09-13 UTC: p95 241ms2026-09-14 UTC: p95 264ms2026-09-15 UTC: p95 238ms2026-09-16 UTC: p95 274ms2026-09-17 UTC: p95 279ms2026-09-18 UTC: p95 223ms2026-09-19 UTC: p95 246ms2026-09-20 UTC: p95 252ms2026-09-21 UTC: p95 256ms2026-09-22 UTC: p95 261ms2026-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 440ms
Sep 6Sep 20Oct 5
US-West
738msp95 · 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-06 UTC: p95 800ms2026-09-07 UTC: p95 781ms2026-09-08 UTC: p95 773ms2026-09-09 UTC: p95 686ms2026-09-10 UTC: p95 152ms2026-09-11 UTC: p95 284ms2026-09-12 UTC: p95 436ms2026-09-13 UTC: p95 455ms2026-09-14 UTC: p95 368ms2026-09-15 UTC: p95 374ms2026-09-16 UTC: p95 299ms2026-09-17 UTC: p95 463ms2026-09-18 UTC: p95 401ms2026-09-19 UTC: p95 430ms2026-09-20 UTC: p95 389ms2026-09-21 UTC: p95 386ms2026-09-22 UTC: p95 708ms2026-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 738ms
Sep 6Sep 20Oct 5
Europe
172msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 190ms2026-09-07 UTC: p95 155ms2026-09-08 UTC: p95 137ms2026-09-09 UTC: p95 150ms2026-09-10 UTC: p95 120ms2026-09-11 UTC: p95 140ms2026-09-12 UTC: p95 211ms2026-09-13 UTC: p95 171ms2026-09-14 UTC: p95 299ms2026-09-15 UTC: p95 418ms2026-09-16 UTC: p95 357ms2026-09-17 UTC: p95 272ms2026-09-18 UTC: p95 149ms2026-09-19 UTC: p95 154ms2026-09-20 UTC: p95 136ms2026-09-21 UTC: p95 146ms2026-09-22 UTC: p95 246ms2026-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 172ms
Sep 6Sep 20Oct 5
Asia-Pacific
943msp95 · 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-06 UTC: p95 579ms2026-09-07 UTC: p95 488ms2026-09-08 UTC: p95 502ms2026-09-09 UTC: p95 594ms2026-09-10 UTC: p95 436ms2026-09-11 UTC: p95 448ms2026-09-12 UTC: p95 709ms2026-09-13 UTC: p95 328ms2026-09-14 UTC: p95 332ms2026-09-15 UTC: p95 445ms2026-09-16 UTC: p95 442ms2026-09-17 UTC: p95 409ms2026-09-18 UTC: p95 377ms2026-09-19 UTC: p95 420ms2026-09-20 UTC: p95 514ms2026-09-21 UTC: p95 447ms2026-09-22 UTC: p95 444ms2026-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 943ms
Sep 6Sep 20Oct 5
US-Central
259msp95 · 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-06 UTC: p95 275ms2026-09-07 UTC: p95 245ms2026-09-08 UTC: p95 251ms2026-09-09 UTC: p95 214ms2026-09-10 UTC: p95 247ms2026-09-11 UTC: p95 366ms2026-09-12 UTC: p95 275ms2026-09-13 UTC: p95 291ms2026-09-14 UTC: p95 357ms2026-09-15 UTC: p95 171ms2026-09-16 UTC: p95 255ms2026-09-17 UTC: p95 270ms2026-09-18 UTC: p95 315ms2026-09-19 UTC: p95 329ms2026-09-20 UTC: p95 169ms2026-09-21 UTC: p95 258ms2026-09-22 UTC: p95 257ms2026-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 259ms
Sep 6Sep 20Oct 5
Canada
244msp95 · latest
500ms250ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 304ms2026-09-07 UTC: p95 227ms2026-09-08 UTC: p95 366ms2026-09-09 UTC: p95 328ms2026-09-10 UTC: p95 215ms2026-09-11 UTC: p95 327ms2026-09-12 UTC: p95 303ms2026-09-13 UTC: p95 278ms2026-09-14 UTC: p95 419ms2026-09-15 UTC: p95 430ms2026-09-16 UTC: p95 368ms2026-09-17 UTC: p95 385ms2026-09-18 UTC: p95 459ms2026-09-19 UTC: p95 320ms2026-09-20 UTC: p95 253ms2026-09-21 UTC: p95 256ms2026-09-22 UTC: p95 258ms2026-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 244ms
Sep 6Sep 20Oct 5
UK
208msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 202ms2026-09-07 UTC: p95 129ms2026-09-08 UTC: p95 131ms2026-09-09 UTC: p95 106ms2026-09-10 UTC: p95 104ms2026-09-11 UTC: p95 92ms2026-09-12 UTC: p95 161ms2026-09-13 UTC: p95 181ms2026-09-14 UTC: p95 107ms2026-09-15 UTC: p95 105ms2026-09-16 UTC: p95 140ms2026-09-17 UTC: p95 114ms2026-09-18 UTC: p95 127ms2026-09-19 UTC: p95 193ms2026-09-20 UTC: p95 149ms2026-09-21 UTC: p95 870ms2026-09-22 UTC: p95 243ms2026-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 208ms
Sep 6Sep 20Oct 5
Southeast Asia
395msp95 · 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-06 UTC: p95 601ms2026-09-07 UTC: p95 544ms2026-09-08 UTC: p95 514ms2026-09-09 UTC: p95 476ms2026-09-10 UTC: p95 545ms2026-09-11 UTC: p95 546ms2026-09-12 UTC: p95 533ms2026-09-13 UTC: p95 604ms2026-09-14 UTC: p95 694ms2026-09-15 UTC: p95 568ms2026-09-16 UTC: p95 605ms2026-09-17 UTC: p95 803ms2026-09-18 UTC: p95 917ms2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 834ms2026-09-21 UTC: p95 943ms2026-09-22 UTC: p95 1.1s2026-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 395ms
Sep 6Sep 20Oct 5
Australia
582msp95 · 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-06 UTC: p95 854ms2026-09-07 UTC: p95 873ms2026-09-08 UTC: p95 889ms2026-09-09 UTC: p95 854ms2026-09-10 UTC: p95 486ms2026-09-11 UTC: p95 428ms2026-09-12 UTC: p95 371ms2026-09-13 UTC: p95 542ms2026-09-14 UTC: p95 387ms2026-09-15 UTC: p95 491ms2026-09-16 UTC: p95 504ms2026-09-17 UTC: p95 605ms2026-09-18 UTC: p95 749ms2026-09-19 UTC: p95 764ms2026-09-20 UTC: p95 691ms2026-09-21 UTC: p95 602ms2026-09-22 UTC: p95 662ms2026-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 582ms
Sep 6Sep 20Oct 5
South America
917msp95 · 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-06 UTC: p95 746ms2026-09-07 UTC: p95 606ms2026-09-08 UTC: p95 719ms2026-09-09 UTC: p95 687ms2026-09-10 UTC: p95 447ms2026-09-11 UTC: p95 517ms2026-09-12 UTC: p95 390ms2026-09-13 UTC: p95 390ms2026-09-14 UTC: p95 473ms2026-09-15 UTC: p95 403ms2026-09-16 UTC: p95 520ms2026-09-17 UTC: p95 826ms2026-09-18 UTC: p95 643ms2026-09-19 UTC: p95 972ms2026-09-20 UTC: p95 609ms2026-09-21 UTC: p95 492ms2026-09-22 UTC: p95 630ms2026-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 917ms
Sep 6Sep 20Oct 5

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.

Get an email when we see Snowflake go down, and when it is back

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.

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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 364msstatus code: 200checked: Oct 5, 2026, 7:53 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
      Operationallatency: 247msstatus code: 200checked: Oct 5, 2026, 7:47 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
      Operationallatency: 50msstatus code: 200checked: Oct 5, 2026, 7:33 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
      Operationallatency: 202msstatus code: 200checked: Oct 5, 2026, 8:09 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
    Operationallatency: 488msstatus code: 200checked: Oct 5, 2026, 8:11 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 181msstatus code: 200checked: Oct 5, 2026, 7:51 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
      Operationallatency: 143msstatus code: 200checked: Oct 5, 2026, 8:07 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 613msstatus code: 200checked: Oct 5, 2026, 8:16 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
      Operationallatency: 359msstatus code: 200checked: Oct 5, 2026, 7:39 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
      Operationallatency: 216msstatus code: 200checked: Oct 5, 2026, 8:15 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 outages

INC20000239, 1h 1mdeclared on their status page2026-09-27
INC20000237, 1h 20mdeclared on their status page2026-09-25
INC20000217, 1h 21mdeclared on their status page2026-09-14
INC20000213, 6h 1mdeclared on their status page2026-09-11
INC20000211, 1h 58mdeclared on their status page2026-09-09
INC20000199, 2h 36mdeclared on their status page2026-09-04
INC20000190, 3h 52mdeclared on their status page2026-09-01
INC20000188, 2h 24mdeclared on their status page2026-08-31

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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

primary
https://app.snowflake.com/
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 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 proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.