Skip to content

Outage tracker / Snapchat

Is Snapchat down?

I'm having a problem

Operationalchecked 5 minutes ago

We reached Snapchat from all 10 regions we check.

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

Reachability verified

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

Email me the next time we see Snapchat go down

Measured by our own probes from ten regions, not Snapchat's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:11 PM UTC
US-East396 msOperational
US-West624 msOperational
Europe289 msOperational
Asia-Pacific2365 msOperational
US-Central241 msOperational
Canada269 msOperational
UK111 msOperational
Southeast Asia1657 msOperational
Australia1313 msOperational
South America457 msOperational
their status pagetheir claim, not our reading

Snapchat publishes no status feed we can read, so the only independent reading here is ours on the left.

Snapchat response time, by region

US-East
600msp95 · 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-09-06 UTC: p95 505ms2026-09-07 UTC: p95 464ms2026-09-08 UTC: p95 402ms2026-09-09 UTC: p95 459ms2026-09-10 UTC: p95 546ms2026-09-11 UTC: p95 549ms2026-09-12 UTC: p95 462ms2026-09-13 UTC: p95 476ms2026-09-14 UTC: p95 450ms2026-09-15 UTC: p95 502ms2026-09-16 UTC: p95 603ms2026-09-17 UTC: p95 680ms2026-09-18 UTC: p95 674ms2026-09-19 UTC: p95 515ms2026-09-20 UTC: p95 559ms2026-09-21 UTC: p95 484ms2026-09-22 UTC: p95 602ms2026-09-23 UTC: p95 774ms2026-09-24 UTC: p95 812ms2026-09-25 UTC: p95 685ms2026-09-26 UTC: p95 593ms2026-09-27 UTC: p95 564ms2026-09-28 UTC: p95 586ms2026-09-29 UTC: p95 668ms2026-09-30 UTC: p95 611ms2026-10-01 UTC: p95 666ms2026-10-02 UTC: p95 601ms2026-10-03 UTC: p95 562ms2026-10-04 UTC: p95 562ms2026-10-05 UTC: p95 600ms
Sep 6Sep 20Oct 5
US-West
1.0sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 593ms2026-09-10 UTC: p95 521ms2026-09-11 UTC: p95 523ms2026-09-12 UTC: p95 638ms2026-09-13 UTC: p95 597ms2026-09-14 UTC: p95 659ms2026-09-15 UTC: p95 767ms2026-09-16 UTC: p95 825ms2026-09-17 UTC: p95 744ms2026-09-18 UTC: p95 858ms2026-09-19 UTC: p95 837ms2026-09-20 UTC: p95 857ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 902ms2026-09-24 UTC: p95 896ms2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 841ms2026-09-28 UTC: p95 936ms2026-09-29 UTC: p95 981ms2026-09-30 UTC: p95 829ms2026-10-01 UTC: p95 930ms2026-10-02 UTC: p95 641ms2026-10-03 UTC: p95 893ms2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
Europe
469msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 722ms2026-09-07 UTC: p95 802ms2026-09-08 UTC: p95 795ms2026-09-09 UTC: p95 658ms2026-09-10 UTC: p95 523ms2026-09-11 UTC: p95 505ms2026-09-12 UTC: p95 619ms2026-09-13 UTC: p95 734ms2026-09-14 UTC: p95 602ms2026-09-15 UTC: p95 897ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 955ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 804ms2026-09-27 UTC: p95 642ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 967ms2026-09-30 UTC: p95 671ms2026-10-01 UTC: p95 517ms2026-10-02 UTC: p95 503ms2026-10-03 UTC: p95 583ms2026-10-04 UTC: p95 478ms2026-10-05 UTC: p95 469ms
Sep 6Sep 20Oct 5
Asia-Pacific
2.2sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.0s2026-09-07 UTC: p95 2.1s2026-09-08 UTC: p95 2.2s2026-09-09 UTC: p95 2.3s2026-09-10 UTC: p95 2.4s2026-09-11 UTC: p95 2.2s2026-09-12 UTC: p95 2.1s2026-09-13 UTC: p95 2.2s2026-09-14 UTC: p95 2.1s2026-09-15 UTC: p95 2.2s2026-09-16 UTC: p95 2.2s2026-09-17 UTC: p95 2.3s2026-09-18 UTC: p95 2.3s2026-09-19 UTC: p95 2.3s2026-09-20 UTC: p95 2.1s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.2s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.3s2026-09-25 UTC: p95 2.1s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 2.2s2026-09-29 UTC: p95 2.1s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 2.4s2026-10-02 UTC: p95 2.5s2026-10-03 UTC: p95 2.3s2026-10-04 UTC: p95 2.3s2026-10-05 UTC: p95 2.2s
Sep 6Sep 20Oct 5
US-Central
528msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 637ms2026-09-07 UTC: p95 719ms2026-09-08 UTC: p95 907ms2026-09-09 UTC: p95 682ms2026-09-10 UTC: p95 661ms2026-09-11 UTC: p95 659ms2026-09-12 UTC: p95 508ms2026-09-13 UTC: p95 631ms2026-09-14 UTC: p95 845ms2026-09-15 UTC: p95 703ms2026-09-16 UTC: p95 527ms2026-09-17 UTC: p95 663ms2026-09-18 UTC: p95 650ms2026-09-19 UTC: p95 544ms2026-09-20 UTC: p95 586ms2026-09-21 UTC: p95 518ms2026-09-22 UTC: p95 550ms2026-09-23 UTC: p95 691ms2026-09-24 UTC: p95 644ms2026-09-25 UTC: p95 613ms2026-09-26 UTC: p95 518ms2026-09-27 UTC: p95 686ms2026-09-28 UTC: p95 740ms2026-09-29 UTC: p95 599ms2026-09-30 UTC: p95 656ms2026-10-01 UTC: p95 513ms2026-10-02 UTC: p95 559ms2026-10-03 UTC: p95 548ms2026-10-04 UTC: p95 450ms2026-10-05 UTC: p95 528ms
Sep 6Sep 20Oct 5
Canada
671msp95 · 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-06 UTC: p95 786ms2026-09-07 UTC: p95 821ms2026-09-08 UTC: p95 801ms2026-09-09 UTC: p95 762ms2026-09-10 UTC: p95 800ms2026-09-11 UTC: p95 716ms2026-09-12 UTC: p95 755ms2026-09-13 UTC: p95 949ms2026-09-14 UTC: p95 860ms2026-09-15 UTC: p95 676ms2026-09-16 UTC: p95 749ms2026-09-17 UTC: p95 634ms2026-09-18 UTC: p95 506ms2026-09-19 UTC: p95 545ms2026-09-20 UTC: p95 580ms2026-09-21 UTC: p95 642ms2026-09-22 UTC: p95 701ms2026-09-23 UTC: p95 839ms2026-09-24 UTC: p95 948ms2026-09-25 UTC: p95 825ms2026-09-26 UTC: p95 779ms2026-09-27 UTC: p95 819ms2026-09-28 UTC: p95 778ms2026-09-29 UTC: p95 822ms2026-09-30 UTC: p95 766ms2026-10-01 UTC: p95 590ms2026-10-02 UTC: p95 667ms2026-10-03 UTC: p95 693ms2026-10-04 UTC: p95 698ms2026-10-05 UTC: p95 671ms
Sep 6Sep 20Oct 5
UK
401msp95 · 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 439ms2026-09-07 UTC: p95 432ms2026-09-08 UTC: p95 447ms2026-09-09 UTC: p95 637ms2026-09-10 UTC: p95 718ms2026-09-11 UTC: p95 618ms2026-09-12 UTC: p95 687ms2026-09-13 UTC: p95 806ms2026-09-14 UTC: p95 762ms2026-09-15 UTC: p95 691ms2026-09-16 UTC: p95 621ms2026-09-17 UTC: p95 687ms2026-09-18 UTC: p95 561ms2026-09-19 UTC: p95 642ms2026-09-20 UTC: p95 598ms2026-09-21 UTC: p95 775ms2026-09-22 UTC: p95 679ms2026-09-23 UTC: p95 806ms2026-09-24 UTC: p95 829ms2026-09-25 UTC: p95 808ms2026-09-26 UTC: p95 730ms2026-09-27 UTC: p95 485ms2026-09-28 UTC: p95 491ms2026-09-29 UTC: p95 423ms2026-09-30 UTC: p95 668ms2026-10-01 UTC: p95 460ms2026-10-02 UTC: p95 442ms2026-10-03 UTC: p95 438ms2026-10-04 UTC: p95 385ms2026-10-05 UTC: p95 401ms
Sep 6Sep 20Oct 5
Southeast Asia
1.8sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 1.8s2026-09-09 UTC: p95 1.9s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.9s2026-09-12 UTC: p95 1.8s2026-09-13 UTC: p95 1.8s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 2.0s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 2.1s2026-09-21 UTC: p95 2.3s2026-09-22 UTC: p95 2.4s2026-09-23 UTC: p95 2.4s2026-09-24 UTC: p95 2.4s2026-09-25 UTC: p95 2.4s2026-09-26 UTC: p95 2.4s2026-09-27 UTC: p95 2.2s2026-09-28 UTC: p95 2.5s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 2.0s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 2.0s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.8s
Sep 6Sep 20Oct 5
Australia
1.8sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.8s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 2.4s2026-09-09 UTC: p95 2.9s2026-09-10 UTC: p95 2.4s2026-09-11 UTC: p95 2.7s2026-09-12 UTC: p95 2.6s2026-09-13 UTC: p95 2.6s2026-09-14 UTC: p95 2.6s2026-09-15 UTC: p95 2.5s2026-09-16 UTC: p95 2.5s2026-09-17 UTC: p95 2.5s2026-09-18 UTC: p95 2.2s2026-09-19 UTC: p95 2.1s2026-09-20 UTC: p95 2.5s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.8s
Sep 6Sep 20Oct 5
South America
1.6sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.1s2026-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 1.9s2026-09-09 UTC: p95 2.3s2026-09-10 UTC: p95 2.0s2026-09-11 UTC: p95 1.9s2026-09-12 UTC: p95 1.8s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 2.0s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.6s
Sep 6Sep 20Oct 5

Is it Snapchat, 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 Snapchat -- it cannot diagnose Snapchat'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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 396msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Snapchat normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 624msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Snapchat normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 241msstatus code: 200checked: Oct 5, 2026, 8:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Snapchat normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 269msstatus code: 200checked: Oct 5, 2026, 8:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Snapchat normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 457msstatus code: 200checked: Oct 5, 2026, 8:06 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Snapchat normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 289msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Snapchat normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 111msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Snapchat 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: 2365msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Snapchat normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1657msstatus code: 200checked: Oct 5, 2026, 7:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Snapchat normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1313msstatus code: 200checked: Oct 5, 2026, 8:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Snapchat 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 Snapchat, 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 started counting reports for Snapchat on September 22, 2026.

Recent outages

No outages on record yet for Snapchat.

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

We have been measuring Snapchat 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 Snapchat covering any window you pick, with our measurements and Snapchat's own claim at the time, side by side.

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

Put this badge in your README

Snapchat uptime measured by RealUptimeLive, from this page's own readings.
[![Snapchat uptime measured by RealUptime](https://realuptime.io/outages/snapchat/badge.svg?days=30)](https://realuptime.io/outages/snapchat)
<a href="https://realuptime.io/outages/snapchat"><img src="https://realuptime.io/outages/snapchat/badge.svg?days=30" alt="Snapchat 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 Snapchat's SLA implies, from our measurement

At or above your target

We measured none of downtime for Snapchat 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 Snapchat'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://www.snapchat.com/
RealUptime is not affiliated with Snapchat; the name identifies what we measured, and nothing here speaks for Snapchat's own team. We send a single web request to Snapchat from 10 regions on our own schedule and time the response. We do not see inside Snapchat's systems, do not use an account or real transaction, and are not the same signal Snapchat's own team has access to. Treat this as one external data point, not a verdict. What we check for Snapchat proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.