Is It Down? tiktok.com
UP
Current
200
HTTP Code
460
Response ms
100%
Uptime (20)
4
Outages
Response Time Last 20 Checks
UP DOWN
Recent Checks (Last 20 Pings)
| Time (America/New_York) | Status | HTTP Code | Response (ms) | |
|---|---|---|---|---|
| 20:53:59 · 12.05.2026 | UP | 200 | 460 | |
| 20:40:04 · 12.05.2026 | UP | 200 | 337 | |
| 20:20:06 · 12.05.2026 | UP | 200 | 267 | |
| 20:00:07 · 12.05.2026 | UP | 200 | 461 | |
| 19:40:05 · 12.05.2026 | UP | 200 | 276 | |
| 19:20:05 · 12.05.2026 | UP | 200 | 420 | |
| 19:00:06 · 12.05.2026 | UP | 200 | 291 | |
| 18:40:05 · 12.05.2026 | UP | 200 | 329 | |
| 18:20:06 · 12.05.2026 | UP | 200 | 584 | |
| 18:00:06 · 12.05.2026 | UP | 200 | 305 | |
| 17:40:05 · 12.05.2026 | UP | 200 | 309 | |
| 17:20:06 · 12.05.2026 | UP | 200 | 283 | |
| 17:00:07 · 12.05.2026 | UP | 200 | 393 | |
| 16:40:06 · 12.05.2026 | UP | 200 | 292 | |
| 16:20:06 · 12.05.2026 | UP | 200 | 1285 | |
| 16:00:06 · 12.05.2026 | UP | 200 | 455 | |
| 15:40:05 · 12.05.2026 | UP | 200 | 456 | |
| 15:20:06 · 12.05.2026 | UP | 200 | 396 | |
| 15:00:09 · 12.05.2026 | UP | 200 | 1142 | |
| 14:40:06 · 12.05.2026 | UP | 200 | 418 |
20:53:59
12.05.2026
UP HTTP 200 · 460ms
20:40:04
12.05.2026
UP HTTP 200 · 337ms
20:20:06
12.05.2026
UP HTTP 200 · 267ms
20:00:07
12.05.2026
UP HTTP 200 · 461ms
19:40:05
12.05.2026
UP HTTP 200 · 276ms
19:20:05
12.05.2026
UP HTTP 200 · 420ms
19:00:06
12.05.2026
UP HTTP 200 · 291ms
18:40:05
12.05.2026
UP HTTP 200 · 329ms
18:20:06
12.05.2026
UP HTTP 200 · 584ms
18:00:06
12.05.2026
UP HTTP 200 · 305ms
17:40:05
12.05.2026
UP HTTP 200 · 309ms
17:20:06
12.05.2026
UP HTTP 200 · 283ms
17:00:07
12.05.2026
UP HTTP 200 · 393ms
16:40:06
12.05.2026
UP HTTP 200 · 292ms
16:20:06
12.05.2026
UP HTTP 200 · 1285ms
16:00:06
12.05.2026
UP HTTP 200 · 455ms
15:40:05
12.05.2026
UP HTTP 200 · 456ms
15:20:06
12.05.2026
UP HTTP 200 · 396ms
15:00:09
12.05.2026
UP HTTP 200 · 1142ms
14:40:06
12.05.2026
UP HTTP 200 · 418ms
Last Detected Downtime
Could not resolve host: www.tiktok.com
All Recorded Outages
| Time (America/New_York) | HTTP | Response (ms) | Error | |
|---|---|---|---|---|
| 2026-04-08 03:00:08 | 301 | 1469 | ||
| 2026-03-30 18:00:12 | 301 | 6063 | ||
| 2026-03-30 05:20:17 | 6002 | |||
| 2026-03-26 05:40:11 | 301 | 6158 |
03:00:08
08.04.2026
DOWN
HTTP 301 · 1469ms
18:00:12
30.03.2026
DOWN
HTTP 301 · 6063ms
05:20:17
30.03.2026
DOWN
HTTP · 6002ms
05:40:11
26.03.2026
DOWN
HTTP 301 · 6158ms
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| DOWN | 6001 ms | 0% |
|||
| DOWN | 22 ms | 0% |
|||
| UP | 200 | 602 ms | 87.5% |
||
| UP | 200 | 60 ms | 100% |
||
| DOWN | 406 | 501 ms | 0% |
||
| UP | 200 | 4301 ms | 100% |
||
| UP | 200 | 46 ms | 100% |
||
| UP | 200 | 145 ms | 100% |
||
| UP | 200 | 332 ms | 15% |
||
| UP | 200 | 85 ms | 100% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to tiktok.com. A response of HTTP 200–399 within 10 seconds = UP. Any timeout, DNS failure, or error code = DOWN. A rolling history of the last 20 checks is stored and displayed above.
If the site shows UP here but you can't access it, the issue is local flush your DNS cache (ipconfig /flushdns on Windows / sudo dscacheutil -flushcache on macOS) or try a different network.
For community-reported outage data and user comments, check DownDetector tiktok.com.