Skip to content

Outage tracker / TikTok

Is TikTok down?

I'm having a problem

Awaiting datachecked moments ago

Our checks of TikTok pass from 7 of the 10 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.

As of Nov 5, 2026, 3:03 PM UTC, RealUptime's checks of TikTok passed in all 7 regions that returned a reading. RealUptime could not obtain a reading from Asia-Pacific, Australia and South America, which is a fact about our own checks there and is not evidence about TikTok.

Front-door checks

Last time our checks failed from two or more distant regions: 4h 7m on Nov 5, 2026 (web surface, from South America, Asia-Pacific, Southeast Asia and Australia, intermittent).

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 Nov 5, 2026, 3:03 PM UTC
US-East428 msChecks passing
US-West1057 msChecks passing
Europe401 msChecks passing
Asia-Pacific4132 msCheck failed
US-Central568 msChecks passing
Canada1824 msChecks passing
UK736 msChecks passing
Southeast Asia1272 msChecks passing
Australia1374 msCheck failed
South America717 msCheck failed
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
1.1sp95 · 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-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 841ms2026-10-23 UTC: p95 843ms2026-10-24 UTC: p95 820ms2026-10-25 UTC: p95 763ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 870ms2026-10-28 UTC: p95 968ms2026-10-29 UTC: p95 844ms2026-10-30 UTC: p95 900ms2026-10-31 UTC: p95 924ms2026-11-01 UTC: p95 949ms2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
US-West
1.2sp95 · 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-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.6s2026-10-23 UTC: p95 2.6s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 2.6s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 2.6s2026-10-30 UTC: p95 2.7s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 3.1s2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Europe
1.3sp95 · 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-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.0s2026-10-23 UTC: p95 939ms2026-10-24 UTC: p95 888ms2026-10-25 UTC: p95 901ms2026-10-26 UTC: p95 967ms2026-10-27 UTC: p95 936ms2026-10-28 UTC: p95 985ms2026-10-29 UTC: p95 924ms2026-10-30 UTC: p95 889ms2026-10-31 UTC: p95 876ms2026-11-01 UTC: p95 961ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Asia-Pacific
4.6sp95 · 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-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.3s2026-10-23 UTC: p95 4.4s2026-10-24 UTC: p95 4.5s2026-10-25 UTC: p95 4.2s2026-10-26 UTC: p95 4.5s2026-10-27 UTC: p95 4.7s2026-10-28 UTC: p95 4.2s2026-10-29 UTC: p95 4.3s2026-10-30 UTC: p95 4.3s2026-10-31 UTC: p95 4.3s2026-11-01 UTC: p95 4.2s2026-11-02 UTC: p95 4.2s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 4.7s2026-11-05 UTC: p95 4.6s
Oct 7Oct 21Nov 5
US-Central
1.4sp95 · 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-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.2s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.4s2026-11-01 UTC: p95 2.6s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Canada
2.9sp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.0s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 2.9s
Oct 7Oct 21Nov 5
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-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.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Southeast Asia
2.9sp95 · 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-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.6s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 2.8s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.9s
Oct 7Oct 21Nov 5
Australia
3.3sp95 · 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-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.7s2026-10-23 UTC: p95 2.7s2026-10-24 UTC: p95 2.7s2026-10-25 UTC: p95 2.6s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.7s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 3.2s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 3.7s2026-11-04 UTC: p95 3.4s2026-11-05 UTC: p95 3.3s
Oct 7Oct 21Nov 5
South America
3.5sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-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.5s2026-10-23 UTC: p95 8.3s2026-10-24 UTC: p95 2.6s2026-10-25 UTC: p95 2.6s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 3.3s2026-10-29 UTC: p95 2.5s2026-10-30 UTC: p95 2.7s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.8s2026-11-02 UTC: p95 3.4s2026-11-03 UTC: p95 4.0s2026-11-04 UTC: p95 3.8s2026-11-05 UTC: p95 3.5s
Oct 7Oct 21Nov 5

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: Awaiting dataUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Awaiting dataSouth America: Awaiting data
  • 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
  • EmbedsUS-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
  • ExploreUS-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
  • LIVEUS-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
  • ProfilesUS-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: 428msstatus code: 200checked: Nov 5, 2026, 3:02 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: 1057msstatus code: 200checked: Nov 5, 2026, 3:03 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: 568msstatus code: 200checked: Nov 5, 2026, 3:03 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: 1824msstatus code: 200checked: Nov 5, 2026, 3:03 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
    Awaiting datalatency: no responsestatus code: nonechecked: no data yet
    0 people in the last 5 minutesNot enough reports to sayWe hold no current probe reading for TikTok from South America, and not enough reports from there to say anything on their own.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 401msstatus code: 200checked: Nov 5, 2026, 3:03 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: 736msstatus code: 200checked: Nov 5, 2026, 3:03 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
    Awaiting dataAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Awaiting datalatency: no responsestatus code: nonechecked: no data yet
      0 people in the last 5 minutesNot enough reports to sayWe hold no current probe reading for TikTok from Asia-Pacific, and not enough reports from there to say anything on their own.
    • Southeast Asia
      Checks passinglatency: 1272msstatus code: 200checked: Nov 5, 2026, 3:00 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
      Awaiting datalatency: no responsestatus code: nonechecked: no data yet
      0 people in the last 5 minutesNot enough reports to sayWe hold no current probe reading for TikTok from Australia, and not enough reports from there to say anything on their own.

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

Checks failing, 4h 7mour checks · South America and Asia-Pacific and Southeast Asia and Australia2026-11-05
Checks failing, 2h 7mour checks · South America and Asia-Pacific and Southeast Asia and Australia2026-11-05
Checks failing, 4h 22mour checks · South America and Asia-Pacific and Southeast Asia and Australia2026-11-04
Checks failing, 2h 13mour checks · South America and Asia-Pacific and Southeast Asia and Australia2026-11-04
Checks failing, 2h 9mour checks · South America and Asia-Pacific and Southeast Asia and Australia2026-11-04
Checks failing, 3h 50mour checks · South America and Asia-Pacific and Southeast Asia and Australia2026-11-04
Checks failing, 1h 3mour checks · South America and Asia-Pacific and Southeast Asia and Australia2026-11-04
Checks failing, 5h 37mour checks · South America and Asia-Pacific and Southeast Asia and Australia2026-11-03

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>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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.

How our checks compare with TikTok's stated SLA

Below your target

Our checks of TikTok failed for 25h 29m over the last 30 days, which is 96.4594% uptime by our checks. A 99.9% target allows 43 minutes over that period.

That is 24h 46m more than the target allows. The figure above is the pro-rata share of one month's fee for the time our checks failed, an estimate from our checks. TikTokdecides what counts. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.

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/
secondary
https://www.tiktok.com/oembed?url=https%3A%2F%2Fwww.tiktok.com%2F%40scout2015%2Fvideo%2F6718335390845095173
secondary
https://www.tiktok.com/@tiktok
secondary
https://www.tiktok.com/explore
secondary
https://www.tiktok.com/live

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.