Status roster
Current Darknet Markets in 2026: Oniongate’s Live Status Roster
This is the onion market roster oniongate watches in 2026, each row with a live reachability reading rather than a score. It is deliberately not a ranking and not a recommendation. The order is fixed, the status comes from a probe, and the mirror count tells you how many endpoints oniongate measures for each onion market on file.
On this page: the roster table · reading mirror counts · the type column · payment rails · how to use this roster · worked example · FAQ
| Market | Type | Status | Mirrors | Last checked |
|---|---|---|---|---|
| torzon | marketplace | Unknown | 5 | n/a |
| mars | marketplace | Unknown | 5 | n/a |
| wethenorth | marketplace | Unknown | 1 | n/a |
| nexus | marketplace | Unknown | 3 | n/a |
| vortex | marketplace | Unknown | 3 | n/a |
| omega | marketplace | Unknown | 1 | n/a |
| drughub | marketplace | Unknown | 1 | n/a |
What this oniongate list is, and is not
Every row here points at a service oniongate actively probes, and clicking a name takes you to its full status page with the onion addresses shown in plain text. What you will not find is a best-of order, a star rating, or a claim that any market is safe. oniongate measures reachability and latency; oniongate does not vouch for what happens once you connect, and oniongate takes no payment to move a name up or down. There is no up or down to move it to.
Why a status reads unknown on oniongate
Until the live feed is attached, every row rests at unknown, which is the honest default rather than a placeholder oniongate forgot to fill. A service reads unknown whenever oniongate holds no fresh measurement for it, including right after a restart or a mirror change. When the loop is reporting, the last-checked column shows how old each reading is, so a stale timestamp warns you before an out-of-date status can mislead you.
Reading the mirror count
Some markets run a single onion; others publish several so that one failed endpoint does not take the whole service offline. A higher mirror count is not a quality signal, only a sign that the operator spread their risk. Each mirror is probed on its own and carries its own reading on the service page, which is where you should verify the exact address before trusting any of them.
Why this oniongate roster changes over the year
A market list is never static. Operators add mirrors, rotate addresses after a scare, or shut down entirely, and a roster that never changes is more likely stale than stable. oniongate updates this page as its own signed directory changes, not on a fixed calendar, so treat the "2026" in the title as the vintage of this snapshot, not a promise that nothing here will move before the year is out.
How a market gets added to this roster
A market appears here only once oniongate holds a verified address for it in the signed directory referenced on the methodology page — oniongate does not list a market on a rumor or a single forum post. That verification step is also why a handful of well-known names are absent: oniongate tracks them with interest but has not yet independently confirmed a current address worth standing behind on a live status page.
How the "type" column is classified
Every entry on this roster currently reads "marketplace," meaning a general-goods darknet market with vendor accounts, listings, and an escrow-based checkout — as opposed to a forum, a single-vendor shop, or a pure information index, none of which oniongate currently tracks. The type column exists so this roster can grow into other categories later without quietly redefining what a row means; for now, every tracked service falls into the same bucket.
Why oniongate does not yet separate markets by specialty
Some tracked markets lean toward a particular product category, others run broader; the type column deliberately does not encode that distinction, because a specialty label ages faster than a reachability reading and would need constant upkeep to stay accurate. Reachability and mirror count are facts a probe can verify on a schedule; a specialty label is closer to editorial judgment, and this roster tries to minimize the number of claims here that are not directly measured.
How to actually use this oniongate roster
A table of seven rows is simple enough to misuse in a couple of predictable ways. Here is how oniongate intends this roster to be read, and what it is not built for.
Use it to jump to a market's own status page, not to decide anything here
This roster's real job is routing: it tells you which markets oniongate tracks and gets you one click away from each one's own status page, mirror list, and copyable onion addresses. Nothing on this table itself should be treated as the final word — the per-market page carries the 24h/7d/30d bands and the actual signed addresses this roster only summarizes.
Do not treat a stale "last checked" time as a current status
Every reading here has an age, shown in the last-checked column once the probe feed is live. A status that was accurate an hour ago can be stale now — a market can go down or recover in the gap between visits. Re-open a market's own status page for the freshest reading rather than trusting a cached glance at this roster from earlier in a session.
Cross-check against the signed directory before trusting any address
This roster shows which markets oniongate tracks and how many mirrors each one runs — it does not itself carry the full onion strings to copy and paste. Follow through to the per-market status page, where each address sits next to the verification steps described on the methodology page, before you ever use one.
Onion market payment rails, in general terms
oniongate does not process payments, hold funds, or advise on any onion market's checkout flow — that is entirely between a visitor and the market's own operator. It is still worth naming, in general terms, the two rails that show up across most onion markets on this roster, since the vocabulary matters when reading a market's own documentation.
Bitcoin, the default across most onion markets
Most onion markets on this roster support Bitcoin as a base payment method, typically routed through an escrow or multisig arrangement the market itself documents. oniongate does not track wallet balances or transaction history for any market; for the mechanics of how Bitcoin transactions and addresses actually work, the reference is Bitcoin.org, not a status board.
Monero as the privacy-focused alternative
A growing share of the markets oniongate tracks also accept Monero, chosen specifically for the transaction-graph privacy Bitcoin does not provide by default. Monero's own project site documents how that privacy model actually works at the protocol level, which is a better source than a secondhand summary on a reachability board.
Why oniongate's onion market roster stays narrow
Plenty of directories list far more than seven onion markets. oniongate's roster is narrower on purpose, and the reason ties back to the same rule that governs every other page on this site: nothing appears here without a verified, signed address behind it.
A wide directory and a narrow roster answer different questions
A broad link directory optimizes for coverage — more names, more addresses, more chance a visitor finds what they were searching for. oniongate's onion market roster optimizes for something narrower: every row here is actively probed, on a fixed cadence, from an address oniongate can trace back to a signed, 2-of-3 verified source. That trade-off means fewer rows, not more.
What a missing market on this roster does and does not mean
An onion market absent from this page is not a claim that the market is fake, unsafe, or defunct — it usually just means oniongate has not yet independently verified a current address for it worth standing behind with a live probe. Absence here is a statement about oniongate's own verification pipeline, not a verdict on the market itself.
Current markets roster: frequently asked questions
Why does every row read Unknown right now?
The probe feed has not reported its first confirmed cycle yet, and this roster follows the same honesty rule as the live board: no fresh measurement means Unknown, never a guessed or carried-over reading.
Does a higher position on this table mean anything?
No. The table order is fixed and alphabetical-adjacent by how services were added to the signed directory, not a ranking. Nothing about row order reflects size, trust, or performance.
Will oniongate add more markets to this roster over time?
Only once each one has an independently verified address in the signed directory referenced on the methodology page. The roster grows deliberately, not automatically, so a market's absence here is not itself a signal about that market.
How is this roster different from the live board on the homepage?
The homepage board is a compact glance at all tracked services plus two informational-only external tiles; this roster is the fuller table view with market type and mirror count columns, scoped to the seven markets in oniongate's own signed directory.
A worked example: how a market gets added to this roster, and how one gets removed
What earns a row on this list
A market is added when its onion address appears in the signed directory oniongate draws from — not when it is popular, not when someone requests it, and not on any schedule tied to how new or established it is. That is a narrower bar than it sounds: a market can be widely discussed without ever making it onto a signed, 2-of-3 verified list, and oniongate would rather leave a well-known name off this roster than add an address nobody has independently verified.
What actually happens when a market disappears
A row is not deleted the moment a market stops answering. The onion address stays listed, its status reads Down and then, after enough quiet cycles, ages toward Unknown rather than being scrubbed from the page. Removing a row entirely only happens when the signed directory itself drops the address — oniongate is an annotation layer on that directory, not an independent authority deciding a market is dead and erasing the evidence. A visitor checking back weeks later can still see the last known reading rather than finding the row silently gone with no trace of what happened.
Reading this roster against the individual status pages
The seven rows here compress a lot of detail from seven separate status pages into a glance. That compression is useful for scanning, and it is also exactly why this page should not be the last stop before connecting to anything. The type column, the mirror count and the last-checked age are each a summary of a fuller picture that lives one click away — the actual probe history, the 24h/7d/30d uptime bands, and the full signed onion addresses as copyable text all live on the per-market page, not here.
A practical habit: use this roster to decide which market's status page to open next, not to decide whether a market is safe to visit. The roster answers “which markets does oniongate track and where do I find more,” while the individual status page answers the narrower, more load-bearing question of whether a specific onion address is reachable right now.
This distinction matters most for the two summary columns oniongate keeps deliberately thin. Type and mirror count are here to help you scan seven onion market rows quickly, not to substitute for the fuller probe history, endpoint-by-endpoint breakdown, and copyable addresses that live one click away on each market's own oniongate status page.