Register methodology · how a status column works · 2026
How WeTheNorth Status Reads on This Register
Checking, Dead, Pending — each word on this page is a specific, narrow claim about one probe, not a verdict on the market. This page explains what those words actually mean, how the register decides when a mirror has failed enough consecutive probes to move state, and why it will not paint a green Online badge just to look reassuring. It embeds the register's current snapshot below, but it is not built to be watched continuously. For a live, refreshing dashboard, see wtn-darknet.vip, the cluster's dedicated status board.
hn2paw7hljeihrk7qm2toniay5bb4cfz46cav5iywnsv64klm45mypqd.onionWhere a WeTheNorth status marker comes from
A WeTheNorth status badge is only worth the check behind it. Ours follows a small pipeline. A probe reaches the WeTheNorth mirror over Tor, the answer gets sorted into a state, and only that honest state goes on the page. No step ever writes a green light by hand for a WeTheNorth address.
This is a snapshot taken by the register, not a refreshing dashboard. It shows the state as of the timestamp above and will not update again until you reload the page. For a live, continuously-refreshing board, use wtn-darknet.vip instead.
These states describe a probe, not an endorsement. Match the full address against the signed register before you rely on any of them.
Reading WeTheNorth status: Checking, Dead, and the rest
Checking is the default for a WeTheNorth mirror. It means a probe has not yet confirmed the mirror, so you treat it as unknown. Dead means the WeTheNorth address stopped answering and should not be used. A confirmed up state, when it appears, still is not a promise for the next hour. Availability of a WeTheNorth onion over Tor moves, and a mirror that answered a minute ago can time out on your circuit. The safe habit is the same at every state. Verify the WeTheNorth key, then decide.
Why a WeTheNorth mirror goes quiet
A WeTheNorth onion timing out is normal more often than it is sinister. Hidden services depend on a chain of relays, and any weak link along the way can stall a request to WeTheNorth. Heavy load, a flood aimed at WeTheNorth, or routine maintenance all read the same way from the outside, as a WeTheNorth page that will not answer. That is why a single failed load is not proof a WeTheNorth link is dead, and one good load is not proof it is safe. States drift, so you re-check rather than trust a badge you saw earlier. When a WeTheNorth link truly stops for good, it moves to Dead here and stays there.
How the official WeTheNorth status grid decides Checking versus Dead
Checking means the most recent probe against that WeTheNorth onion did not get a timely reply — nothing more specific than that. Dead means the pattern has held across enough consecutive probes that a single bad relay hop stops being a plausible explanation. The grid never jumps straight from a live-looking state to Dead on one missed check; it always passes through a run of Checking readings first.
What an honest WeTheNorth status page will never show you
It will never show a green "Online" badge that is hard-coded rather than earned by an actual probe result, and it will never show a fabricated uptime percentage. Both are common shortcuts on clone pages that want to look more reassuring than the underlying reality — a real status page reads Checking or Dead precisely because those are the only two states an honest probe loop can actually prove.
Reading a WeTheNorth status change log without inventing history
A "change log" for a WeTheNorth probe-based status grid is easy to fake with plausible-looking dates and a clean row of green checkmarks. This section explains what an honest version actually looks like for a WeTheNorth mirror, and why it stays sparse rather than polished.
What we can actually attest to
Every entry a probe loop can honestly log is a timestamp, an address, and a result — answered, timed out, or failed — nothing more. We do not log a narrative explanation for why a node went quiet unless it comes from a signed statement tied to the canon key; guessing at a cause and presenting it as fact would be exactly the kind of manufactured confidence this page exists to avoid.
Why gaps in the log are normal, not suspicious
A probe loop is not continuous, and a gap in checks — an hour, sometimes longer — reflects probing cadence, not a hidden outage being concealed. Treat a gap as missing data, the same way a doctor treats a missing lab result: not evidence of anything on its own, just a value that was not measured for that window.
How to use history responsibly when deciding to trust a mirror
A mirror with a long run of consistent Checking-then-answered cycles is a mildly better sign than one that flips to Dead often, but neither pattern substitutes for the PGP fingerprint check described elsewhere on this site. History describes reachability, not authenticity — a clone could in principle answer probes reliably too. Use status history to decide which live address to try first, never to skip verifying that the address is genuine.
What a status grid cannot tell you about legitimacy
A status marker answers exactly one question — did the last probe get a response — and nothing about whether that response came from the genuine WeTheNorth service or a clone squatting on a similar-looking address. A well-resourced clone can run a healthier probe record than the real mirror during a rough week, simply because it has less legitimate traffic competing for its resources. That asymmetry is precisely why this page treats an Online-reading marker as informational rather than as a safety signal, and keeps the PGP fingerprint check as the only step that actually establishes trust.
Reading a WeTheNorth status history instead of one reading in isolation
A single WeTheNorth status check tells you what happened on one probe. A pattern across several checks over hours or days tells you considerably more about a WeTheNorth mirror, if you read it the right way.
Why we do not publish an uptime percentage for WeTheNorth
It would be easy to convert a run of status checks into a clean "99.x% uptime" figure, and it would also overstate the precision of what periodic spot checks against a Tor hidden service can actually measure. A percentage invites treating WeTheNorth's reachability as a settled, precise fact when the underlying data is a set of loosely spaced probes, each vulnerable to circuit noise unrelated to the service itself.
What a short run of Checking readings usually means
One or two Checking results on a WeTheNorth mirror, especially when other mirrors on this register read normally, is most often a Tor-layer artifact — a slow guard relay, a congested circuit, a directory lookup delay on the probing side — not evidence that WeTheNorth itself is having a problem. Re-check after the next probe cycle before drawing any conclusion.
What actually justifies concern
A sustained Dead reading across multiple probe cycles, especially if it affects several WeTheNorth mirrors at once rather than a single address, is the pattern worth taking seriously. Even then, the correct response is patience and re-verification through this register, not searching elsewhere for an alternate WeTheNorth link — that search is exactly where a phishing clone is most likely to be waiting.
What a WeTheNorth status marker does not tell you about the market
A WeTheNorth mirror probe answers one narrow question: did this onion respond just now. It says nothing about the WeTheNorth marketplace running behind that onion — order volume, vendor activity, or escrow health are separate signals this WeTheNorth register does not collect and would not display honestly if it could.
Status is not a WeTheNorth market-health metric
A WeTheNorth mirror can read Checking for reasons that have nothing to do with the WeTheNorth marketplace itself — a congested Tor circuit, a guard relay reshuffle, routine maintenance on the hosting side. Reading a single Checking mark as a verdict on WeTheNorth vendor reliability, listing volume, or the health of the escrow system conflates two different layers. This WeTheNorth register tracks the onion's reachability, not the marketplace's internal state.
Escrow and vendor activity live on WeTheNorth, not on this page
Whether escrow releases are running on schedule, how responsive a given WeTheNorth vendor is, or how deep the current listings run — none of that is visible from outside the onion, and none of it is something a WeTheNorth mirror-status register can probe or attest to. Those questions get answered inside WeTheNorth itself, after a verified connection, not from a status grid on a clearnet reference.
A dead WeTheNorth mirror does not mean a compromised market
When one WeTheNorth mirror goes Dead while a primary or failover WeTheNorth address keeps answering, that is ordinary infrastructure churn, not evidence the WeTheNorth market or its vendor base has been compromised. Panic-selling stored balances or rushing an order onto an unverified alternate link because one address dropped out of the rotation causes far more real harm than the outage itself ever does.
WeTheNorth status questions people ask
Is WeTheNorth up right now?
This register shows a snapshot — the state as of the last probe, not a refreshing answer to "right now." Availability changes hour to hour, so this page shows an honest probe state such as Checking or Dead and never hard-codes a live badge it cannot back. For continuous, refreshing monitoring, use wtn-darknet.vip, the cluster's dedicated live status board.
What does Checking mean?
A probe has not confirmed the mirror yet. Read it as unknown, not as safe or online.
Why not just show Online?
A hard-coded Online badge is the oldest phishing trick. We only report what a probe can back, so an unconfirmed link stays Checking.
Reading a WeTheNorth status check end to end
Worked example: primary checking, failover pending
Say the ticker on this page shows the primary onion as checking and the failover onion as pending. That is not an error state — it is the two-tier design working as intended. A probe runs against the primary WeTheNorth onion address on a fixed interval; while that probe is in flight, or immediately after it, the status legitimately reads checking rather than a canned online label, because this page does not print an uptime number it cannot back up in real time.
The failover WeTheNorth onion sits behind that, checked on its own cycle, and only becomes relevant if the primary onion stops answering across several consecutive probes. If you land on this page mid-cycle, the honest move is to refresh once, a minute or two later, rather than treat a single checking read as bad news.
What you should never do is skip this page and go straight to whichever onion address you last had bookmarked — an onion string, on its own, cannot tell you whether the service behind it is still the real WeTheNorth or has since gone dead, been seized, or been replaced by a phishing clone reusing an old page. The status check and the PGP check are separate tools for separate questions: PGP verifies you have the right onion address, status tells you whether that address is currently answering.
Common mistakes, expanded
Reading “checking” as “down.” Checking means a probe cycle is in progress or was recently inconclusive, not that the WeTheNorth onion address has failed. A dead label, by contrast, is reserved for an onion that has failed enough consecutive checks to be retired from the active list.
Assuming a status page proves a market is legitimate. Status only answers whether a specific onion address is currently reachable over Tor. It says nothing about escrow behavior or vendor quality — those are separate questions this page does not attempt to answer.
Bookmarking a mirror and never rechecking it. Onion addresses on WeTheNorth are not permanent fixtures; a mirror that was primary last month can be marked legacy or dead this month if the operators rotate it. The changelog on this page exists so a returning visitor can see exactly when and why an onion address moved category.
Confusing “legacy” with “safe to try anyway.” A legacy onion is one that used to be current and has since been superseded — it is not a fallback worth attempting just because it once worked. Treat a legacy or dead entry as a signal to return to the primary or failover onion, verified fresh, not as a hidden extra option.
WeTheNorth status glossary: what each marker word means
Five words cover every state this WeTheNorth register will ever print next to an onion address. Each one maps to a specific probe outcome, never to a guess about the marketplace behind it.
Checking
The default WeTheNorth marker. A probe cycle against the onion is either in flight or has not yet returned a confirmed result. Read Checking as unknown, never as a synonym for down or for safe.
Pending
Applied to a failover WeTheNorth address that has not been probed as recently as the primary onion. Pending is a scheduling state, not a health verdict on that mirror.
Up (confirmed)
A WeTheNorth onion that answered its most recent probe. It is printed rarely and only when the probe genuinely returned a response — never hard-coded, and never a promise that the next request will also succeed.
Dead
A WeTheNorth address that has failed enough consecutive probes to be retired from the active rotation. A dead mirror should not be tried again from this register; watch this page for a signed replacement instead.
Legacy
A WeTheNorth onion that used to be current and has since been superseded by a newer signed address. Legacy is not a fallback worth attempting — treat it the same as Dead for connection purposes.
Search the WeTheNorth status glossary and FAQ
This box filters the glossary terms and FAQ entries already on this page — it runs entirely in your browser against the content above, makes no network request, and never leaves this WeTheNorth status page. Try a term such as checking, dead, or primary onion.
Why a WeTheNorth onion times out, in the Tor Project's own words
The probe behavior described above is not specific to WeTheNorth. It follows directly from how Tor hidden services route traffic, and independent documentation explains the mechanism better than a status page summary can.
- The Tor Project — official documentation on how onion services establish and maintain a circuit, including why a reachable service can still time out under load.
- Electronic Frontier Foundation — plain-language background on Tor's relay model and the tradeoffs it makes for anonymity over raw speed.
- Privacy Guides — independent notes on evaluating onion-service reliability without over-trusting a single status check.
- GnuPG — the PGP toolchain behind the fingerprint check this status page repeatedly points back to; a status marker only ever supplements that check, never replaces it.
- Whonix — a Tor-routed operating system whose documentation covers circuit and guard-relay behavior in more depth than a single mirror's status history ever can.
More WeTheNorth verification reading
A reachable onion is not the same as a verified one: pair a Checking or Dead reading here with the PGP fingerprint check before you rely on any WeTheNorth address, and follow the opsec baseline for the session itself. Once an address checks out, the WeTheNorth login page covers what comes next, the Canada page untangles the market from the unrelated sports slogan, and the about page explains how this register itself decides what to publish.
Turn a marker into a decision
A state is useful only once you hold the address it belongs to. That onion, freshly signed, waits on the register. If you have not made the trip before, the access guide lays out each move.