Is It Down? lovetorrent.net
DOWN
Current
HTTP Code
6001
Response ms
0%
Uptime (20)
5
Outages
Error Details
Connection timeout after 6000 ms
Response Time Last 5 Checks
UP DOWN
Recent Checks (Last 20 Pings)
| Time (America/New_York) | Status | HTTP Code | Response (ms) | |
|---|---|---|---|---|
| 17:53:28 · 03.06.2026 | DOWN | 6001 | ||
| 15:59:46 · 03.06.2026 | DOWN | 6002 | ||
| 05:53:38 · 03.06.2026 | DOWN | 6001 | ||
| 05:52:17 · 03.06.2026 | DOWN | 6000 | ||
| 05:50:55 · 03.06.2026 | DOWN | 6001 |
17:53:28
03.06.2026
DOWN HTTP · 6001ms
15:59:46
03.06.2026
DOWN HTTP · 6002ms
05:53:38
03.06.2026
DOWN HTTP · 6001ms
05:52:17
03.06.2026
DOWN HTTP · 6000ms
05:50:55
03.06.2026
DOWN HTTP · 6001ms
Last Detected Downtime
Connection timeout after 6000 ms
All Recorded Outages
| Time (America/New_York) | HTTP | Response (ms) | Error | |
|---|---|---|---|---|
| 2026-06-03 17:53:28 | 6001 | |||
| 2026-06-03 15:59:46 | 6002 | |||
| 2026-06-03 05:53:38 | 6001 | |||
| 2026-06-03 05:52:17 | 6000 | |||
| 2026-06-03 05:50:55 | 6001 |
17:53:28
03.06.2026
DOWN
HTTP · 6001ms
15:59:46
03.06.2026
DOWN
HTTP · 6002ms
05:53:38
03.06.2026
DOWN
HTTP · 6001ms
05:52:17
03.06.2026
DOWN
HTTP · 6000ms
05:50:55
03.06.2026
DOWN
HTTP · 6001ms
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| UP | 200 | 340 ms | 100% |
||
| UP | 200 | 735 ms | 100% |
||
| UP | 200 | 95 ms | 100% |
||
| UP | 200 | 302 ms | 100% |
||
| DOWN | 503 | 110 ms | 40% |
||
| UP | 200 | 172 ms | 100% |
||
| UP | 403 | 5052 ms | 100% |
||
| DOWN | 6001 ms | 0% |
|||
| UP | 200 | 459 ms | 100% |
||
| UP | 200 | 347 ms | 100% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to lovetorrent.net. 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.