Skip to content

Outage tracker / TikTok

Is TikTok down?

I'm having a problem

Checks passingchecked moments ago

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

As of Oct 22, 2026, 8:56 PM UTC, RealUptime's checks of TikTok passed in all 10 regions that returned a reading.

Front-door checks

Our checks of TikTok did not fail from two or more distant regions in the 63 days we have checked it (since Aug 20, 2026). This does not show TikTok works for users.

Email me when our checks of TikTok fail from two or more distant regions

One email when our checks of TikTok fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not TikTok's official status.

our check readinglive · checked Oct 22, 2026, 8:56 PM UTC
US-East578 msChecks passing
US-West1816 msChecks passing
Europe383 msChecks passing
Asia-Pacific4476 msChecks passing
US-Central1061 msChecks passing
Canada1437 msChecks passing
UK968 msChecks passing
Southeast Asia880 msChecks passing
Australia2541 msChecks passing
South America1011 msChecks passing
their status pagetheir claim, not our reading

TikTok publishes no status feed we can read, so the only reading here is our check reading on the left.

TikTok response time, by region

US-East
846msp95 · 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 506ms2026-09-24 UTC: p95 679ms2026-09-25 UTC: p95 475ms2026-09-26 UTC: p95 510ms2026-09-27 UTC: p95 484ms2026-09-28 UTC: p95 480ms2026-09-29 UTC: p95 538ms2026-09-30 UTC: p95 571ms2026-10-01 UTC: p95 876ms2026-10-02 UTC: p95 734ms2026-10-03 UTC: p95 619ms2026-10-04 UTC: p95 831ms2026-10-05 UTC: p95 841ms2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 816ms2026-10-08 UTC: p95 692ms2026-10-09 UTC: p95 586ms2026-10-10 UTC: p95 609ms2026-10-11 UTC: p95 597ms2026-10-12 UTC: p95 650ms2026-10-13 UTC: p95 647ms2026-10-14 UTC: p95 595ms2026-10-15 UTC: p95 782ms2026-10-16 UTC: p95 814ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 846ms
Sep 23Oct 7Oct 22
US-West
2.7sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 936ms2026-09-24 UTC: p95 687ms2026-09-25 UTC: p95 668ms2026-09-26 UTC: p95 703ms2026-09-27 UTC: p95 557ms2026-09-28 UTC: p95 670ms2026-09-29 UTC: p95 664ms2026-09-30 UTC: p95 730ms2026-10-01 UTC: p95 2.0s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 2.6s2026-10-05 UTC: p95 2.8s2026-10-06 UTC: p95 2.4s2026-10-07 UTC: p95 2.6s2026-10-08 UTC: p95 2.2s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.7s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.7s
Sep 23Oct 7Oct 22
Europe
1.0sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 778ms2026-09-24 UTC: p95 808ms2026-09-25 UTC: p95 790ms2026-09-26 UTC: p95 767ms2026-09-27 UTC: p95 804ms2026-09-28 UTC: p95 778ms2026-09-29 UTC: p95 774ms2026-09-30 UTC: p95 922ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 3.6s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 3.6s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 3.2s2026-10-22 UTC: p95 1.0s
Sep 23Oct 7Oct 22
Asia-Pacific
4.3sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 3.6s2026-10-02 UTC: p95 3.6s2026-10-03 UTC: p95 3.5s2026-10-04 UTC: p95 3.6s2026-10-05 UTC: p95 3.7s2026-10-06 UTC: p95 2.7s2026-10-07 UTC: p95 2.5s2026-10-08 UTC: p95 3.5s2026-10-09 UTC: p95 3.7s2026-10-10 UTC: p95 3.8s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 3.6s2026-10-13 UTC: p95 3.6s2026-10-14 UTC: p95 3.8s2026-10-15 UTC: p95 3.9s2026-10-16 UTC: p95 3.7s2026-10-17 UTC: p95 3.9s2026-10-18 UTC: p95 4.3s2026-10-19 UTC: p95 4.3s2026-10-20 UTC: p95 4.3s2026-10-21 UTC: p95 4.3s2026-10-22 UTC: p95 4.3s
Sep 23Oct 7Oct 22
US-Central
2.1sp95 · latest
5s2.5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 677ms2026-09-24 UTC: p95 880ms2026-09-25 UTC: p95 701ms2026-09-26 UTC: p95 695ms2026-09-27 UTC: p95 605ms2026-09-28 UTC: p95 632ms2026-09-29 UTC: p95 577ms2026-09-30 UTC: p95 785ms2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 961ms2026-10-03 UTC: p95 888ms2026-10-04 UTC: p95 2.4s2026-10-05 UTC: p95 2.6s2026-10-06 UTC: p95 2.0s2026-10-07 UTC: p95 2.4s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 852ms2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 960ms2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.1s
Sep 23Oct 7Oct 22
Canada
2.0sp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 631ms2026-09-24 UTC: p95 751ms2026-09-25 UTC: p95 683ms2026-09-26 UTC: p95 595ms2026-09-27 UTC: p95 627ms2026-09-28 UTC: p95 592ms2026-09-29 UTC: p95 586ms2026-09-30 UTC: p95 661ms2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 2.3s2026-10-08 UTC: p95 2.0s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 982ms2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 917ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.0s
Sep 23Oct 7Oct 22
UK
1.3sp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 698ms2026-09-24 UTC: p95 699ms2026-09-25 UTC: p95 662ms2026-09-26 UTC: p95 637ms2026-09-27 UTC: p95 680ms2026-09-28 UTC: p95 693ms2026-09-29 UTC: p95 720ms2026-09-30 UTC: p95 772ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 951ms2026-10-03 UTC: p95 923ms2026-10-04 UTC: p95 932ms2026-10-05 UTC: p95 924ms2026-10-06 UTC: p95 935ms2026-10-07 UTC: p95 928ms2026-10-08 UTC: p95 938ms2026-10-09 UTC: p95 948ms2026-10-10 UTC: p95 965ms2026-10-11 UTC: p95 984ms2026-10-12 UTC: p95 3.6s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 961ms2026-10-16 UTC: p95 976ms2026-10-17 UTC: p95 965ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 3.4s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
Southeast Asia
1.7sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 2.3s2026-10-02 UTC: p95 2.0s2026-10-03 UTC: p95 2.2s2026-10-04 UTC: p95 3.1s2026-10-05 UTC: p95 2.4s2026-10-06 UTC: p95 2.9s2026-10-07 UTC: p95 2.5s2026-10-08 UTC: p95 2.9s2026-10-09 UTC: p95 2.4s2026-10-10 UTC: p95 2.2s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 2.1s2026-10-13 UTC: p95 2.4s2026-10-14 UTC: p95 2.5s2026-10-15 UTC: p95 2.6s2026-10-16 UTC: p95 2.1s2026-10-17 UTC: p95 3.0s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 3.0s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
Australia
2.7sp95 · 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-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.9s2026-09-25 UTC: p95 1.8s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 2.0s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.7s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.7s
Sep 23Oct 7Oct 22
South America
2.5sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 2.4s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 2.0s2026-10-04 UTC: p95 3.1s2026-10-05 UTC: p95 2.6s2026-10-06 UTC: p95 3.2s2026-10-07 UTC: p95 3.3s2026-10-08 UTC: p95 2.6s2026-10-09 UTC: p95 1.8s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 2.1s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 2.0s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.6s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.5s
Sep 23Oct 7Oct 22

Check your own site while you wait on TikTok

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 TikTok. It cannot diagnose TikTok's own systems.

What we measured, function by function

TikTok answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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: 578msstatus code: 200checked: Oct 22, 2026, 8:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach TikTok normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1816msstatus code: 200checked: Oct 22, 2026, 8:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach TikTok normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 1061msstatus code: 200checked: Oct 22, 2026, 8:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach TikTok normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1437msstatus code: 200checked: Oct 22, 2026, 8:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach TikTok normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1011msstatus code: 200checked: Oct 22, 2026, 8:52 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach TikTok 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: 383msstatus code: 200checked: Oct 22, 2026, 8:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach TikTok normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 968msstatus code: 200checked: Oct 22, 2026, 8:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach TikTok 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: 4476msstatus code: 200checked: Oct 22, 2026, 8:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach TikTok normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 880msstatus code: 200checked: Oct 22, 2026, 8:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach TikTok normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2541msstatus code: 200checked: Oct 22, 2026, 8:52 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach TikTok 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 TikTok, 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 TikTok on September 12, 2026.

Recent probe events

No probe events on record yet for TikTok.

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

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

Full check history for TikTok: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

TikTok uptime by RealUptime's checksLive, from this page's own readings.
[![TikTok uptime by RealUptime's checks](https://realuptime.io/outages/tiktok/badge.svg?days=30)](https://realuptime.io/outages/tiktok)
<a href="https://realuptime.io/outages/tiktok"><img src="https://realuptime.io/outages/tiktok/badge.svg?days=30" alt="TikTok 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 TikTok down?", https://realuptime.io/outages/tiktok. 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.

How our checks compare with TikTok's stated SLA

At or above your target

Our checks of TikTok failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from TikTok'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.tiktok.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: www.tiktok.com

RealUptime is not affiliated with TikTok; the name identifies what we checked, and nothing here speaks for TikTok's own team. We send a single web request to TikTok from 10 regions on our own schedule and time the response. We do not see inside TikTok's systems, do not use an account or real transaction, and are not the same signal TikTok's own team has access to. Treat this as one external data point, not a verdict. What we check for TikTok 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.