Per-service status
DrugHub Onion Status 2026: Is DrugHub Market Reachable Right Now?
Oniongate tracks whether the drughub darknet market answers on Tor and how long it takes to respond. The status is produced by a probe, not written by an editor. To be unambiguous: this concerns the onion marketplace called drughub, not a licensed pharmacy, a health service hub, or any legitimate clearnet business. Oniongate tracks this drughub onion market the same way it tracks every other listed service, on one shared, honest probe loop.
How to read drughub's status numbers
Why Oniongate tracks DrugHub instead of just linking to it
Oniongate exists because a link alone tells a visitor nothing about whether DrugHub actually answers right now. Every DrugHub mirror on oniongate is probed on the same recurring loop as the other six markets Oniongate follows, scored independently, and shown with an honest Unknown state rather than a guess. Oniongate does not operate DrugHub and cannot vouch for anything past the network layer — only whether the listed DrugHub addresses responded to the last probe.
What the 24h, 7d and 30d uptime windows mean
Each uptime card is a rolling percentage of successful probes over that window, recalculated every cycle rather than fixed to a calendar day. The 24h figure reacts fastest and swings the most on a single bad stretch; the 30d figure smooths past a short outage and reflects the longer pattern. Read the 24h card for "is anything wrong right now" and the 30d card for "how reliable has drughub actually been."
Reading drughub's per-mirror breakdown
drughub has 1 endpoint on file in the signed directory below, each probed and scored independently rather than rolled into one shared number. A single mirror reading Down while the others read Online usually points at that specific mirror, not at drughub as a whole — check whether the pattern is isolated to one address or shared across all of them before drawing a conclusion.
What to do if drughub reads unknown
Unknown means the probe loop has no fresh result to report for drughub, not that anything is wrong. It shows up right after this status page is first added to oniongate, and it shows up if the probe feed itself goes offline — in both cases every service on oniongate reads unknown together, not just this one. Wait for the next cycle and refresh rather than treating an unknown reading as a sign the market itself is in trouble.
Probe timeline
last 30 checksEach cell is one probe, newest on the right. The strip fills as the loop runs; with no feed attached yet, every check reads unknown rather than a colour oniongate cannot stand behind.
Mirrors — monitored endpoint
1 endpoint on filedrughubdk5bmh4w6q3uubnkd3rgo2hjydjf5t6yphzmqfbrgplbs7fid.onionThis address comes from the signed 2-of-3 directory. oniongate measures the drughub endpoint; it does not mint addresses. A drughub address that is not on this signed list is not one oniongate monitor or endorse.
Honest answers
Is drughub reachable right now?
The banner shows it. Down means oniongate's latest probe could not complete a request to the listed drughub endpoint; unknown means oniongate have no fresh check to summarise. Both describe oniongate's probe over Tor, not the marketplace, and a reading decays to unknown if the loop stops reporting rather than holding a stale green.
Is the drughub link on oniongate genuine?
It is the one in oniongate's signed source, and it still deserves your own check. Copy the full onion string above and confirm it, character by character, against a second trusted source before connecting. The complete address is shown as plain text so you never rely on a shortened or pre-clicked link.
Why only one drughub address?
Oniongate monitor whatever the signed directory lists, and for drughub that is currently one onion. If the signed source publishes additional mirrors, they will appear here on their own, each with its own dot and timestamp, because oniongate measure the listed set rather than adding endpoints ourselves.
What does a high drughub latency indicate?
Latency is the round-trip time of a successful probe over Tor, in milliseconds. Tor routing adds real delay, so a few hundred milliseconds is expected and not a defect. Oniongate report the median of recent successful checks, which keeps a single slow circuit from skewing the number you see.
Does Oniongate probe DrugHub more than once a day?
Yes, on a recurring loop rather than a single daily check. DrugHub's mirrors are probed repeatedly through the day so a row here reflects a recent measurement, not a stale one from hours earlier. The exact interval varies with probing load across all seven tracked markets.
If DrugHub shows Unknown across every mirror, does that mean it is seized?
No — treat an all-Unknown reading as a monitoring gap, not a seizure claim. It usually means the probing loop for DrugHub has not reported recently, whether from a restart, a Tor circuit issue on oniongate's end, or a temporary gap in the feed. A seizure is a specific claim oniongate does not make without a signed statement to back it.
What this oniongate drughub status page cannot tell you
A reachability reading is a narrow, specific claim. Here is what it does and does not cover, so a green dot next to drughub is not mistaken for more than it actually says.
Reachability is not the same as legitimacy
A probe reaching drughub's onion address confirms the service answered a network request within the timeout window. It says nothing about escrow practices, vendor vetting, or whether a specific listing inside drughub is genuine — those questions belong on drughub's own reference and verification pages, not on a reachability board. Treat oniongate as one input among several, not a verdict on whether drughub itself is trustworthy.
Why one mirror's reading is not the whole picture
drughub may publish more than one onion endpoint, and each one is probed independently. A single dead mirror does not mean drughub itself is down if other mirrors on file are still answering — check the full mirror table below rather than reading one row as the complete state of the service. Conversely, one live mirror during a wider outage is not proof everything is fine; it only means that one specific address is currently reachable.
How to use oniongate alongside drughub's own verification steps
Before trusting any drughub address copied from oniongate or anywhere else, verify it against drughub's own signed record — a PGP fingerprint match, not a status dot, is what actually establishes that an address is genuine. This status page exists to answer "is it reachable right now," a question drughub's own reference site is not built to answer continuously; the two pages do different jobs and neither replaces the other.
Reading drughub's single-mirror setup on oniongate
drughub is tracked here with one monitored onion endpoint, the same lean footprint as omega and wethenorth among the seven markets on oniongate.
Why a single-mirror reading deserves extra caution
Without a second tracked drughub address to cross-check against, a Checking or Down reading here is the only signal oniongate has for the service — there is no fallback mirror to consult before drawing a conclusion. Re-checking after the next probe cycle, rather than acting on one reading, matters more for a single-mirror market like drughub than for a market with several endpoints.
What oniongate does not verify about drughub
A reachable reading confirms the tracked address answered a probe within the timeout — it says nothing about drughub's vendor vetting, dispute process, or how the operator runs the service day to day. Verify the address itself against drughub's own signed record before treating reachability as more than that.
A worked example: reading drughub’s history when only one onion address is on file
What a single onion endpoint means for oniongate's design
drughub is tracked with one monitored onion address rather than a mirror set, so oniongate's mirror table is intentionally short — one row, one reading, no split to reconcile across multiple endpoints. That simplicity is honest about what is actually being measured: a single hidden service, checked on the same cadence as every other market on oniongate, with nothing padded in to make the page look busier than the underlying data supports.
Why the changelog matters more here than the live tile
With only one drughub address to watch, the single current status word carries a lot of weight on its own. The changelog and the 24h/7d/30d uptime bands on oniongate exist to add context a single live tile cannot: whether today's reading is consistent with drughub's recent pattern or a break from it, which is the more useful question for anyone deciding whether to trust the address right now.
Reading drughub’s status honestly when the picture is incomplete
A single monitored onion address means oniongate can only ever describe one endpoint's behavior, not drughub's infrastructure as a whole. If drughub operates additional addresses that are not yet part of the signed directory oniongate draws from, they simply do not appear here — an absence from oniongate is not evidence a mirror does not exist, only that oniongate has no verified record of it to measure.
Drughub onion market: mirror & incident log
Like wethenorth and omega, drughub runs a single mirror, and this section is oniongate's dedicated record for it — separate from the shared status banner above and written for drughub specifically rather than copied across every tracked market's page.
Incident log
No incidents are logged for drughub in the current window. With one address on file, oniongate's bar for an entry here is the same as for omega and wethenorth: several consecutive failed cycles, not a single miss, before anything gets recorded as more than routine circuit noise over Tor.
Mirror history
Drughub is tracked with exactly one onion endpoint, the smallest footprint among the seven markets oniongate watches alongside omega and wethenorth. A single-mirror market that later moves to a second address would show up here as a mirror-count change rather than silently replacing the old entry, which is also why sending a file through a reviewed, independent tool like OnionShare is a better habit for anything sensitive than trusting a single onion address's reachability reading as a stand-in for actual verification. oniongate logs a mirror-count change here the moment drughub's signed directory entry adds a second address, the same rule applied to every other market this board tracks.
DrugHub as a darknet market: what oniongate's status actually verifies
DrugHub is one of seven darknet markets oniongate probes on the same Tor loop, and the status word on this page describes exactly one thing: whether DrugHub's onion address answered a Tor request within the timeout window on the most recent probe cycle. Nothing about DrugHub's inventory, its vendor base, or any uptime claim DrugHub makes on its own front page factors into this reading — oniongate did not consult DrugHub's marketing, it consulted a stopwatch and a Tor circuit.
Why "darknet market status" means something narrow here
A lot of pages use the phrase "darknet market status" to mean a vague blend of reputation, activity level, and uptime folded into one score. oniongate's DrugHub status page does not do that. Reachability over Tor is the only signal this page reports, and every other question about DrugHub — whether it is a good market to use, whether its escrow is sound, whether its vendor base is currently active — belongs to DrugHub's own reference material, not to this status reading.
How often DrugHub's Tor status actually changes
Most probe cycles produce no change at all: DrugHub's onion address answers the way it answered last cycle, and the status word simply repeats. A change only gets logged on this darknet market's page when DrugHub's status genuinely flips between Online, Checking, Down and Unknown — oniongate does not manufacture drama by treating an unchanged Tor reading as new information about the market.