Status / How we check
How we check market status
Uptime on this board is not a guess. Here is exactly what a poll does, what counts as online, and why a single timeout never flips a market to "down".
One circuit per address
Each onion is polled over its own isolated Tor circuit, so a slow relay on one check cannot poison the result for another mirror. A market with several addresses is scored on the set: if any one answers cleanly, the market is reachable, because that is exactly how a user would experience it.
Latency thresholds, not just "did it load"
An onion that answers after thirty seconds is technically up and practically unusable. We record response time and treat a node that consistently crawls as degraded rather than healthy — that is why a market can be "Online" yet still carry a note about slow nodes after an address rotation.
The recheck window
A market moves to Rechecking when its mirrors stop answering consistently. We do not immediately call that an exit — markets go quiet for reindexing, DDoS mitigation, or a planned address change. During recheck we re-poll on a tighter cycle and hold the uptime figure until the set answers across a full window again.
Why the hub link is the safe route
Direct onions drift: addresses rotate, nodes rebuild, bookmarks go stale. Every "Open official link" button on this site routes through the verified hub instead, which points at whatever is confirmed live at that moment. It is the difference between a static list and a tracker.
What a green badge does not promise
- It is a reachability signal, not an endorsement — availability says nothing about how a market treats its users.
- Status reflects the last poll, not this exact second; a market can drop between cycles.
- We track addresses, not operators. An onion answering is not proof the people behind it are trustworthy.