oniongate 2026: What Is Actually Up on the Darknet, Right Now

How the oniongate probe loop works

Every tile on OnionGate above is the output of the same short loop, run against the same address, on the same schedule. There is no manual entry anywhere in this pipeline — a human does not type "online" next to a market name. The loop measures, and the tile reflects whatever it measured last.

What a single probe actually does

A probe opens a fresh circuit over Tor to the onion address on file for a given service, requests the front page or a known-lightweight endpoint, and times how long a valid response takes to arrive. If the response comes back inside the timeout window, the probe records a latency figure in milliseconds and marks the service reachable for that cycle. If the timeout expires with no response, or the circuit itself fails to build, the probe records a miss. Neither outcome is interpreted beyond that single cycle — a miss is a miss, not a verdict.

Why the cadence is roughly four seconds, not continuous

Probing too aggressively looks like an attack from the perspective of the relays and the destination service, and it risks getting the monitoring host rate-limited or blocked outright, which would make every reading on OnionGate worse, not better. A cadence in the few-second range is fast enough to catch most real outages within a reasonable window while staying inside the range Tor circuits can sustain without abuse flags.

How one probe becomes a status word

No single probe result flips a tile straight to Online or Down. The board looks at a short run of recent cycles before it commits to a status word, specifically to avoid one slow relay hop or one congested circuit reading as a full outage. A service has to fail consistently across several consecutive cycles before OnionGate calls it Down, and it has to answer consistently before OnionGate calls it Online. That lag is deliberate — it trades a little responsiveness for a lot fewer false alarms.

What happens when the probe feed itself goes offline

The probe feed is a separate process from the page you are reading, and it can go down independently of every market it watches. When that happens, every tile on OnionGate reads Unknown rather than continuing to show the last real reading, because a stale number presented as current is worse than an honest gap. The gauge in the pill will read awaiting feed exactly like it does right now, before the feed was first wired up.

Why a probe checks reachability, not content

A probe intentionally stops at "did a valid response arrive," and never parses what the response actually contains. Checking page content would mean the monitoring host renders JavaScript, follows redirects, and potentially executes whatever a compromised or hostile mirror serves back — a meaningfully larger attack surface for a service whose entire job is watching infrastructure it does not control. The tradeoff is a narrower signal: oniongate can tell you a market's front door answered, not that the page behind it loaded correctly or matches what a real visitor would see, which is exactly why every status page here recommends checking the market's own reference site for anything beyond raw reachability.

What each oniongate status word means

Four words appear on OnionGate, and each one has a specific, narrow meaning tied to the probe loop above. None of them are marketing language, and none of them are guesses dressed up as facts.

Online

The service answered a probe inside the timeout window across the most recent run of cycles. Online says the front door opened when we knocked a few times in a row. It says nothing about whether the market itself is trustworthy, whether an individual page inside it loads, or whether a login or checkout flow works — only that the address itself is currently reachable.

Checking

The loop has an address queued and is actively cycling probes against it, but has not yet accumulated enough consistent results in either direction to commit to Online or Down. Checking is the default state for anything newly added to OnionGate, and it is also where a service sits during the short window right after it starts failing, before enough consecutive misses have piled up to call it Down.

Down

The service has missed enough consecutive probe cycles that a single bad relay hop stops being a plausible explanation. Down does not distinguish between a service that is temporarily overloaded, one going through maintenance, and one that has been seized or shut down permanently — it only says the address was unreachable across a sustained run of checks. Read the per-service status page for the longer uptime history before drawing a conclusion about which of those it is. A market that has read Down for several consecutive cycles, with no recovery, is a reasonable prompt to check that market's own status page and mirror directory for a signed announcement before assuming it will come back on its own.

Unknown

There is no fresh measurement to report, for one of a few honest reasons: the probe feed itself is offline, the service was only just added and has not completed its first cycle, or the address is monitored informationally without being in oniongate's own signed directory. Unknown is not a euphemism for Down. It means exactly what it says — we do not currently know, and we would rather tell you that than guess.

Reading the uptime bands on an oniongate service page

Each market's own status page carries three uptime figures — 24h, 7d and 30d — and reading them side by side tells you more than any single number.

Why three windows instead of one

A single uptime percentage flattens a lot of real variation. A market that had one bad hour this week and a clean month otherwise looks identical, on a 30-day figure alone, to one that has been degrading steadily. Showing 24h, 7d and 30d together lets a visitor see whether a dip is fresh, whether it has been recovering, or whether it has been sliding for a while — three snapshots instead of one blended average.

What a gap between the windows usually means

A 24h figure noticeably worse than the 30d figure points at something recent — a mirror rotation, a maintenance window, or an early sign of trouble. A 24h figure noticeably better than a rough 7d figure usually means a market that had a bad stretch and has since stabilized. Neither pattern is a verdict on its own; both are a reason to look at the per-mirror breakdown on that market's own status page before drawing a conclusion.

What oniongate does not do

A monitoring board earns trust as much by what it refuses to claim as by what it measures.

No ranking, no recommendation

Oniongate does not rank the seven markets it tracks against each other, does not label any of them "best," and does not take payment to feature one more prominently than another. A reachability board that also sells placement stops being a reachability board — it becomes an ad unit wearing a status board's interface, which is exactly the pattern this project set out to avoid.

No vouching for what happens after the door opens

A green Online reading means a probe request completed. It says nothing about a market's escrow practices, its vendor vetting, or whether a specific listing inside it is legitimate. Oniongate measures reachability at the network layer only — everything past that point is the visitor's own judgment to make, informed by whatever that market's own trust signals turn out to be.

Recently changed on oniongate

A status board is only useful if a status change is visible, not buried under the current reading. Once the probe feed is attached, this section becomes a short reverse-chronological log of state transitions — a service moving from Online to Down, from Down to Checking, or from Unknown to a confirmed reading for the first time.

What counts as a change worth logging

Only a transition between the four status words above gets logged here, not every individual probe cycle. A service that stays Online across a hundred consecutive checks produces zero log entries; a service that flips from Online to Down produces exactly one, timestamped to the cycle where the transition was confirmed. This keeps the log short and genuinely informative rather than a noisy dump of raw probe data.

Why this section is quiet right now

This board is newly wired up, and honestly labeled as such in the summary bar above: the probe feed has not reported its first confirmed cycle yet, so there is no transition history to show. We would rather ship the section with nothing in it and say so plainly than backfill it with invented events to make the page look more active than it is. Check back once the feed has been live for a full cycle or two.

Full market list oniongate monitors

The board above shows nine services in two tiers. The first tier — torzon, mars, wethenorth, nexus, vortex, omega and drughub — sits in oniongate's own signed directory, meaning we hold a verified address for each and probe it directly ourselves. The second tier — archetyp and abacus — is tracked informationally without a directory entry of our own, which is why those two tiles read Unknown by default rather than Checking: we have not verified an address to probe them against yet.

What "in our signed directory" actually means

A directory entry means oniongate holds a specific onion address for that service, checked against the same kind of PGP-signed verification process used across the sister sites in this project, and probes that exact address on the standard cadence. The verified marker on a tile is shorthand for that: an address we stand behind enough to probe directly, not a claim about the market's trustworthiness or legality.

What "external" means, and why it is not a downgrade

An external tile is a service we track with interest but have not added to our own signed directory, usually because we have not independently verified a current address for it. External is a statement about our own verification coverage, not a judgment about the service itself — plenty of external services are perfectly real, we simply have not done the work to stand behind a specific address yet.

How to read a per-service status page

Each market name on OnionGate links through to its own status page, which carries a longer history than the compact tile can show: a 24-hour hourly breakdown, a 7-day daily rollup, and a 30-day summary, alongside the full onion address as copyable text. Start on OnionGate for a fleet-wide glance; move to the per-service page when you need the longer history behind a single reading.

How oniongate relates to other reference sites in this space

Oniongate is deliberately narrow: reachability and latency, measured, nothing else. Address verification, mirror directories, and phishing-pattern write-ups for individual markets live on each market's own signed reference — a status board and a verification desk are different jobs, and conflating them is how a site ends up making claims it cannot actually back up. If you came here looking for a PGP fingerprint to check an onion address against rather than an uptime reading, that lookup belongs on the market's own reference page, not here. A signed mirror directory covering more markets than OnionGate tracks lives at torindex.watch, and a dedicated PGP walkthrough lives at torverify.online — both narrower in scope than oniongate, and neither one measures uptime.

oniongate's list of tools worth knowing before you connect to any onion market

A reachability reading from oniongate answers one narrow question: did the address respond. Everything that happens after a market's front door opens depends on a small toolchain most experienced onion users already carry, and oniongate would rather name that toolchain plainly than assume every visitor already has it.

Verifying an address, not just trusting a green dot

Oniongate can confirm a market's onion address answered a probe; it cannot confirm the address is genuinely operated by the market it claims to be. That distinction belongs to PGP, not to a status board. GnuPG remains the reference implementation most onion market guides point to for checking a signed fingerprint against a market's published key, and once you are holding several long PGP fingerprints and market-specific credentials, a dedicated vault such as KeePassXC is a safer place to keep them than a plaintext note next to a browser bookmark.

Running Tor from an isolated, amnesiac environment

Oniongate itself runs over plain Tor and makes no claim about which operating system a visitor should use to reach any onion market it tracks, but two projects come up in nearly every serious guide. Tails boots from removable media and forgets everything on shutdown, which matters if the device itself is ever seized. Whonix takes a different approach, isolating the Tor process from the workstation in separate virtual machines so a single application bug in a browser cannot leak a real IP address back through the connection oniongate is measuring.

Reading beyond a single onion market's own status claim

A market's own front page will tell you it is trustworthy; it has every incentive to. Privacy Guides maintains an actively updated, non-market-specific set of operational-security recommendations that go well past what any single status board like oniongate can cover on one page, and the Tor Project's own support portal documents exactly how a Tor circuit builds, times out, and fails — useful background for interpreting why an onion market's latency looks the way it does on oniongate.

Payment rails an onion market typically expects

Most markets oniongate tracks price listings in Bitcoin, Monero, or both, and neither is optional background reading if you plan to transact rather than just browse a status board. Bitcoin.org is the project's own plain-language introduction to how the underlying ledger and wallets work, and Monero's own project site, getmonero.org, explains the privacy properties that lead a number of onion markets to prefer it over Bitcoin for anything beyond a simple purchase.

Sharing a file without opening another market account

Not every exchange with a vendor or a market's support channel needs to happen inside that market's own messaging system. OnionShare lets two Tor users share a file or a short message directly, peer to peer, over a temporary onion address, without either side needing an account anywhere — a tool oniongate does not build or bundle, but one worth knowing exists before you assume a market's own inbox is the only option.

Reading what your connection to an onion market actually protects

The EFF's own Surveillance Self-Defense guide breaks down, layer by layer, what Tor and HTTPS each protect and what neither one does, which pairs directly with the reachability oniongate reports: a market reading Online on oniongate means the network layer answered, not that everything above it is automatically safe.

Where an oniongate probe result stops and network reality begins

Everything oniongate measures happens inside the Tor network, and understanding a little about that network's own scale helps put a single probe reading in context.

Onion services sit on real, documented infrastructure

Tor is not a black box — the Tor Project's own metrics portal publishes independently measured statistics on relay counts, bandwidth, and onion-service usage across the whole network. It has no visibility into any specific hidden service's status, which is exactly the gap oniongate's own probe loop exists to fill for the seven markets it tracks — the two sources answer different questions and neither substitutes for the other.

Why latency varies more on Tor than on the open web

A request to a clearnet site typically takes one hop. A request to an onion service takes several, routed through independently operated relays with no guaranteed capacity or geography — the Tor Project's own documentation covers why this design trades raw speed for the anonymity properties onion services depend on. A latency reading on OnionGate that looks high compared to a normal website is not a sign anything is wrong; it is the baseline cost of the network these services are built on.

Reading, not replacing, independent verification

Nothing on OnionGate substitutes for verifying an onion address yourself against a signed record before you trust it. The EFF's Tor and HTTPS explainer is a useful primer on what each layer of a connection does and does not protect, and it pairs well with the per-market methodology OnionGate follows: measure reachability honestly, and leave authenticity verification to the signed directory each market maintains.

What OnionGate deliberately does not measure

A monitoring board earns trust as much by what it refuses to claim as by what it reports. OnionGate is scoped narrowly on purpose, and naming the boundary plainly is part of keeping the numbers it does publish honest.

OnionGate does not measure order volume, vendor count, or listing freshness

A market can be fully reachable on OnionGate and still be quiet inside — few active listings, a slow vendor response time, a thin catalog. Reachability and latency say nothing about what is actually happening on the other side of a working connection. Treat an Online reading on OnionGate as "the door opened," not as "there is a lot going on inside."

OnionGate does not measure trust, safety, or vendor reputation

Nothing OnionGate reports should be read as an opinion about whether a market is safe to use, whether its escrow works as described, or whether its vendors are trustworthy. Those questions belong to each market's own signed directory and community track record, not to a probe that only checks whether an address answers.

OnionGate does not measure historical uptime as a percentage

The board shows a current status and a limited recent-change log, not a computed uptime percentage over weeks or months. A percentage implies a precision that periodic Tor probing, with its inherent circuit-level noise, cannot honestly deliver. OnionGate would rather show fewer numbers that are true than a clean-looking figure that overstates what was actually measured.

Why OnionGate states these boundaries instead of letting them stay implicit

A monitoring board that quietly expands its claims over time — adding a trust score here, an uptime badge there — is the same slow drift that turns a useful reference into a misleading one. Writing the boundary down, and keeping OnionGate inside it, is the mechanism that keeps every other claim on this board worth checking.

Darknet market status glossary: terms oniongate uses on every page

A few words carry precise, narrow meanings across every reading on oniongate. This short glossary spells each one out once, so the rest of the board can use them without re-explaining.

Onion service

An onion service is a server reachable only through Tor, at a .onion address rather than a normal clearnet domain. Every darknet market oniongate tracks runs one or more onion services, and a probe on oniongate targets that onion address directly, never a clearnet mirror standing in for it.

Darknet market

A darknet market, in the narrow sense oniongate uses the term, is a marketplace reachable only as an onion service on the Tor network, distinct from a clearnet storefront that merely sells restricted goods. Every market on the oniongate board is a darknet market in this specific sense — an onion-only listing platform, not a general online store with a Tor mirror bolted on.

Tor circuit

A Tor circuit is the chain of relays a request travels through before it reaches an onion address. oniongate's probe loop opens a fresh circuit over Tor for each check rather than reusing one, which is part of why a single slow circuit does not, on its own, flip a market's status word.

Status word

A status word is one of exactly four values — Online, Checking, Down, or Unknown — the only vocabulary oniongate uses to describe an onion market's reachability. No fifth word, no percentage badge, no "partially up" hedge; every status reading on oniongate resolves to one of those four words or it does not resolve at all.

Mirror

A mirror is a second, third, or fifth onion address the same darknet market operates in parallel, usually to survive one address being seized, blocked, or simply going stale. oniongate probes every mirror on file independently rather than collapsing a market's whole mirror set into a single dot.

Signed directory

A signed directory is the PGP-verified source oniongate draws every onion address from before probing it for status. An address that is not in that signed directory is not one oniongate measures, no matter what onion market it claims to mirror.

oniongate frequently asked questions

Why does oniongate never show a fake Online badge?

Because a hard-coded badge defeats the entire point of a measurement board. Every status word on OnionGate traces back to an actual probe cycle against a real address, and when that chain breaks — feed offline, address unverified, service newly added — the tile says so honestly as Checking or Unknown rather than defaulting to a reassuring green that nobody actually measured.

Does oniongate rank or endorse any market?

No. The board is sorted by which tier a service sits in and then by name, never by a score, a paid placement, or an editorial opinion about which market is "best." Reachability and latency are the only two things OnionGate claims to know.

How do I add a service to the board?

Read the methodology page for how a check is scored and what we need to verify an address before adding it to the signed directory. We add services deliberately, not automatically, because each one requires us to independently confirm the onion address we would be probing.

Why does oniongate track only seven markets?

Because every market on the board requires an independently verified onion address before it is added, and that verification step does not scale to hundreds of listings run by one small project. Seven, tracked carefully with a signed directory behind each one, is more useful than a much longer list nobody actually checked.

Is oniongate itself a marketplace?

No. Oniongate has no listings, no vendor accounts, and no payment flow of its own. It is a monitoring board and a signed directory of onion addresses for the markets it tracks — nothing here can be bought, sold, or ordered.

What happens if oniongate's own probe feed goes down?

Every board tile reverts to Unknown rather than freezing on its last reading or defaulting to Online. A visitor should never mistake a stale oniongate outage for information about whether a tracked market itself is reachable — Unknown across the whole board is a signal about oniongate's own feed, not about the seven markets it watches.

A worked example: reading the oniongate board during an actual incident

Say two of the seven markets oniongate tracks go quiet within the same hour. The first thing oniongate's board does is what it always does — nothing gets hand-set, nothing gets hidden, and both tiles simply follow their own probe results into Down and then, if the quiet continues across enough cycles, toward Unknown. There is no oniongate operator deciding in the moment how the incident should be framed; the board is downstream of the probe loop, not the other way around.

A visitor landing on oniongate mid-incident sees exactly that: two tiles reading Down, five reading whatever their own independent probes produced, and a last-checked timestamp on each row showing how fresh that specific reading is. oniongate does not bundle the two Down markets into a single “partial outage” banner or editorialize about what might be happening — each onion address gets its own reading, because oniongate has no reliable way to know whether two markets going quiet in the same window share a cause or are simply coincidental.

What oniongate does next is nothing dramatic: the next scheduled probe cycle runs on the same cadence it always does, for the two affected markets and the five unaffected ones alike. If both come back, their tiles follow the same rule every other reading follows — a fresh successful probe, and only a fresh successful probe, moves a tile back toward Online. oniongate does not shorten the wait because an incident feels urgent, and it does not extend it out of caution either. The interval is the interval, published on the methodology page, regardless of what is or is not happening on any given day.

That flatness is deliberate. A status board that speeds up, slows down, or adds commentary depending on how dramatic a moment feels is a board a reader has to interpret on top of trusting. oniongate is built to be boring in exactly this way: the same measurement, run the same way, whether nothing is happening or two markets just went dark at once.

oniongate in one paragraph, for anyone landing here for the first time

oniongate is a status board, not a market and not a directory. oniongate does not sell anything, oniongate does not rank anything, and oniongate does not accept payment for a friendlier reading. What oniongate does is narrow: oniongate probes a fixed list of onion addresses over Tor on a repeating cadence, and oniongate shows exactly what each probe returned — Online, Checking, Down, or Unknown, never a guess dressed up as a fact. If oniongate has no fresh measurement, oniongate says so instead of showing a stale green. That is the entire premise oniongate is built on, and every page on this board exists to make that premise checkable rather than just claimed.