http://tracker.x6c.co:6969/announce
Is it down? Yes: no answer for 2d 22h · last checked 1h ago
Down
Score 74
· United States
· Show in the table · Map
· Follow
What's wrong: Down: connection refused
- Not working (down or Up/Bad) for 2 days in all: a tracker that doesn't work for 5 days, either way, is removed and banned.
- Last error: HTTP connection failed
- Last successful check: 2d 22h ago.
How to fix it
Uptime, last 30 days
30 days agonow
Long-term uptime
Up 96.7% of the time over 58 days, since 2026-09-24.
2026-09-242026-11-20
| Month | Uptime | Typical latency |
| Nov 2026 (20 d) | 90.3% |
Oceania 201 ms · Asia 175 ms · Europe 99 ms · North America 26 ms |
| Oct 2026 | 100.0% |
Oceania 194 ms · Asia 183 ms · Europe 107 ms · North America 25 ms |
| Sep 2026 (7 d) | 100.0% |
– |
Last 48 hours
48 h agonow
Latency by region
From Oceania: 252 ms nowFrom Asia: 179 ms nowFrom Europe: 105 ms nowFrom North America: 11 ms now
Announce round trip, in ms, from each place latency is measured. Recorded every 2 hours, kept 30 days.
Score
Recent availability74.5%Stability× 99.7%Reliability score= 74Latency penaltynoneScore74Last 7 daysanswered 60.1% of checks · 1 outageSince addedanswered 90.7% over 30.0 days · longest outage 67.0 h
The tracker's own stats
Not read while it's down; last read 3d 4h ago. About this
Details
- IP addresses
- 23.165.136.98
- Network
- x6c
- Located in
- United States
- IPv4 / IPv6
- ok / not published
- Peer test
- n/a (passed 6 of the last 6)
- Last peer test saw
IPv4 (2d 22h ago): our second test client was handed our first one, with its real address: clients find each other.
- Delayed peer test
IPv4: passed 6 of 6; last 3d 2h ago, asking 6 min after our first client announced: it was still handed out.
About once a day, the same test with a wait, like real clients that announce minutes apart. For information only for now.
- Checked every
- 240 min, last 1h ago
- Announce interval
- 29 min
- Added
- 24-9-2026 (58d 19h ago)
Recent events
| 2d 18h ago | went Down (HTTP connection failed) |