Darknet market status: which markets are up, down or unverified
This board shows the honest reachability status for every project we track. It is not a live monitor yet, so every row reads either checking or unknown — never a confident up we cannot back up with a fresh measurement. When live probing is wired in, the words here will change on their own; until then they stay conservative on purpose.
| Market | Status | Addresses | Last review |
|---|---|---|---|
| Torzon | Checking | 5 | last reviewed 2026-08-24 |
| Mars | Checking | 5 | last reviewed 2026-08-24 |
| We The North | Checking | 1 | last reviewed 2026-08-24 |
| Nexus | Checking | 3 | last reviewed 2026-08-24 |
| Vortex | Unknown | 3 | last reviewed 2026-08-24 |
| Omega | Unknown | 1 | last reviewed 2026-08-24 |
| DrugHub | Checking | 1 | last reviewed 2026-08-24 |
What each status word promises
Checking means an address is on file and a measurement is expected, but no current probe result stands behind it. Unknown means our most recent reading is too old to report as fact. Down — which no row shows today — would mean a fresh probe tried and failed. We deliberately do not carry an "up" word on this page, because an up claim without a live measurement is the single most common lie a status page tells.
Why Deep Web Wire would rather say unknown than up
A stale up is worse than an honest unknown. It tells a reader the coast is clear at the exact moment a market may have dropped and the fake-link scramble has begun. By refusing to print up without a current reading, this board removes the one signal a phishing operator would most like us to fake on their behalf. If you need certainty, cross-check the address on the market record and connect through Tor Browser yourself.
Status readings last reviewed 2026-08-24; this reference page was last expanded 2026-08-25. Statuses are conservative pending live probing.
How to read this Deep Web Wire board correctly right now
This board's honesty depends on readers understanding exactly what stage it is at: addresses are on file and cross-checked manually, but automated live reachability probing is not yet wired into the status column shown here.
What that means for the words on this page today
Every row currently shows checking or unknown rather than a fresh up/down reading, because printing up or down without a live probe behind it would be a guess dressed up as a measurement. That is a deliberate limitation of this board's current stage, not an oversight, and it is worth knowing before you treat any row here as a live signal.
What changes once live probing goes live
When automated probing is wired in, rows on this board will be able to show a genuinely current down reading backed by a failed connection attempt, not just an absence of a fresh check. Until then, treat this board as a directory of addresses on file with conservative status labels, and confirm reachability yourself through Tor for anything time-sensitive.
How to use the Deep Web Wire status board before you connect
The status board is a starting point, not a substitute for checking the specific darknet market onion address you are about to use. This is the sequence Deep Web Wire recommends every time.
Step 1 — Read the row for your market, not the whole board
One row at a time
Find the specific darknet market you need on this Deep Web Wire status board and read only that row. The board as a whole has no single verdict; each row is its own claim about its own project.
Step 2 — Open the full record for the address itself
The status board doesn't carry addresses
Click through to the project's market record for the actual onion address and its sourcing note; this board intentionally keeps only the status word and a link, not the full string.
Step 3 — Cross-check before you connect
Status word plus independent check
Combine what this board says with your own comparison against a second independent source, as described in verifying an onion address before you deposit, before opening anything in Tor Browser.
How the Deep Web Wire status board compares to other trackers
Plenty of darknet market directories print a confident up or down for every listing, all the time. Deep Web Wire deliberately does not match that format, and it is worth explaining why rather than treating it as an oversight.
Why most trackers show fewer status words than Deep Web Wire
Fewer words, more confidence than the data supports
A directory offering only "online" or "offline" for every darknet market listing is choosing simplicity over honesty when its underlying check cannot actually support that binary. Deep Web Wire uses three words — Checking, Unknown, Down — specifically because the honest answer is sometimes "we don't currently know," and collapsing that into a fake binary would throw away real information.
What Deep Web Wire's status board deliberately does not do
No uptime percentages, no rankings
This board does not print uptime percentages, does not rank markets by reliability, and does not badge any project as recommended. Those presentations look more authoritative than a plain status word, which is exactly why Deep Web Wire avoids them — see how Deep Web Wire verifies links for the full editorial reasoning.
How often this board actually refreshes
A status board that never says when it was last touched invites a reader to assume it is more current than it is. Every row here carries an explicit last-reviewed date rather than a vague "recently checked" claim, and the page itself notes when it was last substantively edited, separate from when the underlying readings were confirmed. Those are two different dates for a reason: this reference page's wording can be revised without every row's status having changed, and conflating the two would blur which kind of freshness a reader is actually looking at.
Frequently asked questions
- Is any darknet market up right now?
- This board will not claim a confident up without a live measurement, so every row reads checking or unknown. Open a market record and cross-check the address, then test reachability yourself through Tor.
- What is the difference between checking and unknown?
- Checking means an address is on file and a measurement is expected but not yet standing behind the row. Unknown means our last reading is too old to report as current fact.
- Why does no market show as down?
- Down would require a fresh probe that tried and failed. Because live probing is not wired to this page yet, we do not assert down any more than we assert up.
- Will this status board eventually show real-time uptime percentages?
- Automated, frequent reachability probing is on the roadmap alongside the signed mirror list described on the PGP page. Until that is live, this board will keep publishing dated, honest snapshots rather than a percentage that would imply more precision than the underlying data actually supports.
- Why not just mark everything unknown until live probing exists?
- Because Checking is a meaningfully different, more useful claim: it says a specific address was confirmed reachable on a specific date, which unknown does not say. Collapsing that distinction would throw away real information this deepweb reference already has, just to make the status vocabulary simpler.
Why this status board avoids a single "system status: operational" banner
Plenty of status pages compress everything into one headline judgment — a green banner, a single word, a traffic-light icon at the top. This board deliberately does not do that, because seven different markets rarely share one true status at once, and a single banner would necessarily paper over the market-by-market differences that actually matter to a reader checking one specific address. Read the row for the market you care about; the board as a whole has no single verdict to offer.
How a status changes on this board
A row's status updates when a new reachability sweep completes for that project, or when a market-specific event — a seizure notice, a confirmed shutdown, an address rotation — is verified through the same sourcing standard described on the mirrors page. Nothing on this board changes because of a claim alone; a status word moves only after the same check every other record on this site goes through.
What happens when a market's fate is more complicated than three words
Checking, Unknown, and Down cover the ordinary reachability cases, but darknet market history includes outcomes that do not fit neatly into a binary of reachable or not — a law-enforcement seizure with a fake replacement page left running, or a project that vanishes without any confirmable event at all. This board's approach to those messier cases is worth spelling out rather than quietly forcing them into whichever of the three words is least wrong.
Seized, but the page still loads
Reachable is not the same as legitimate
A seized onion service sometimes keeps resolving through Tor, now under law-enforcement control, sometimes with a banner and sometimes silently logging visitors. A row showing Checking or Unknown for a market in this state would be actively misleading, so a confirmed seizure gets its own explicit note tied to the record rather than being folded into the ordinary three-word vocabulary.
Gone without a confirmable event
Silence is its own category
Some projects simply stop being reachable with no announcement, no seizure banner, and no operator statement explaining why. This board does not guess between exit scam, quiet retirement, or technical failure in that situation — it records that reachability stopped and the date it was last confirmed, and leaves the interpretation to the reader rather than manufacturing a specific narrative it cannot support.
A market that announces its own shutdown
The cleanest case, still verified the same way
When a project posts its own signed announcement that it is closing, that announcement gets the same sourcing treatment as any other claim on this wire before the record reflects it — checked against the project's established channel, not taken at face value from a forum repost, even when the news is exactly what everyone expected.
Why the addresses column matters as much as the status column
It is easy to focus entirely on the status word and skim past the addresses column next to it, but the two numbers interact in ways worth understanding. A market with five listed addresses and a Checking status is a different situation than a market with one address and the same status word.
More addresses means more surface area to verify, not more safety
A five-mirror market is not inherently safer than a one-mirror project; it simply has five separate strings a reader needs to individually cross-check rather than one. Treating a longer addresses count as a reassurance on its own, without doing the character-by-character comparison on whichever specific mirror you intend to use, misses the point of publishing the count at all.
A single-address project carries a different, sharper risk
A project like DrugHub or Omega running one onion address has no fallback entrance if that specific address becomes unreachable or is rotated without notice reaching every channel at once. That is a legitimate operational trade-off some projects make deliberately, not a red flag by itself, but it does mean a reader following a single-address project should check the status row more often than they would for a project with several standby mirrors.