Per-service status
Torzon Onion Status 2026: Is Torzon Market Reachable Right Now?
This page tracks whether the torzon onion market is reachable and how quickly it answers. It reads straight from oniongate's own probe loop. Oniongate does not decide the state by hand, and oniongate never prints online without a fresh, successful check to back it.
How to read torzon's status numbers
Why Oniongate tracks Torzon instead of just linking to it
Oniongate exists because a link alone tells a visitor nothing about whether Torzon actually answers right now. Every Torzon mirror on this board 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 Torzon and cannot vouch for anything past the network layer — only whether the listed Torzon 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 torzon actually been."
Reading torzon's per-mirror breakdown
torzon has 5 endpoints 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 torzon 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 torzon reads unknown
Unknown means the probe loop has no fresh result to report for torzon, not that anything is wrong. It shows up right after this page is first added to the board, 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 endpoints
5 endpoints on filetorzonguqmlfy2kfi5tjbnt4bp3idtkjzi4qtupmhpdihjftomjtdzqd.onion2vycvnjtqco2tavovk5ozrqa57jlwpwujlbp2ifooenqcktqwm3qe5yd.onion3t6qm72c4vgkgb2hwho5bdutlf2ztoey66qunmkrstqr6zmstadhmuqd.onion45bgvcy7or2rvv3jall5peal4jsf4ikgp5to755oky3x3do6ecved4ad.onion5anlnmvtbrcjxg6cdid2ov2efwoleeuhgghiy32wze2oelvmppt3nhad.onionThese addresses come from the signed 2-of-3 directory. oniongate measures them, it does not mint them. Any torzon address you find outside that signed list is not ours.
Honest answers
Is torzon down?
Check the banner at the top. If it reads down, oniongate's last probe could not complete a request to any listed endpoint. If it reads unknown, oniongate simply has no fresh measurement to report, which is common right after a restart or before the feed is attached. Neither state is a verdict on the service itself, only on what oniongate's probe could reach.
Why does it say unknown?
Unknown means no recent successful or failed check exists to summarise. oniongate would rather show a blank than invent a green light. Once the loop records a result, the banner switches to online, checking or down, and the timestamp next to it tells you how fresh that reading is.
How often do you check?
The probe runs on a short loop, roughly every few seconds per endpoint, over Tor. Each endpoint carries its own dot, so a single dead mirror does not drag the whole service into a false red, and a single lucky mirror does not paint over a wider outage.
Which address should I trust?
Trust the ones in the signed directory, and verify the string yourself. Copy the full address, compare it character by character against a second independent source, and never accept a shortened or pre-clicked link. oniongate publishes the complete text here for exactly that reason.
Does Oniongate probe Torzon more than once a day?
Yes, on a recurring loop rather than a single daily check. Torzon'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 markets oniongate tracks.
If Torzon 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 Torzon 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 torzon status page cannot tell you
A reachability reading is a narrow, specific claim. Here is what oniongate does and does not cover for this onion market, so a green dot next to torzon is not mistaken for more than it actually says.
Reachability is not the same as legitimacy
A probe reaching torzon'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 torzon is genuine — those questions belong on torzon's own reference and verification pages, not on oniongate's reachability board. Treat oniongate as one input among several, not a verdict on whether torzon itself is trustworthy.
Why one mirror's reading is not the whole picture on oniongate
torzon may publish more than one onion endpoint, and each one is probed independently by oniongate. A single dead mirror does not mean torzon 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 this page alongside torzon's own verification steps
Before trusting any torzon address copied from this page or anywhere else, verify it against torzon'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 torzon's own reference site is not built to answer continuously; the two pages do different jobs and neither replaces the other.
Reading torzon's mirror count on oniongate
torzon is tracked on oniongate with five separate onion endpoints on file, the largest mirror set of the seven markets oniongate watches. That number is not a quality score — it mainly reflects how torzon's own operator has chosen to spread risk across multiple addresses rather than a single front door.
What a five-mirror spread changes for a visitor
With five independently probed endpoints, a single mirror going Down on torzon's status page is less likely to mean the whole service is unreachable, compared to a market running only one address. Check the mirror table below for the specific endpoint reading before assuming a torzon-wide outage from one row alone.
Why more mirrors is not automatically safer
Each additional torzon mirror is one more address a phishing clone can imitate, and one more string a visitor has to verify correctly rather than memorize. A larger mirror set trades single-point-of-failure risk for a larger surface to check carefully — verify whichever torzon address you intend to use against its signed record, not just against this reachability reading.
Torzon onion market: mirror & incident log
This section is oniongate's running record for the torzon onion market specifically — a place for anything about torzon's mirror set worth logging separately from the live status banner above, rather than a generic paragraph copied across all seven tracked markets.
Incident log
No incidents are logged for torzon in the current window. oniongate only adds an entry here once a pattern shows up across several consecutive probe cycles, not from a single anomalous reading — a lone Down result rolls into the 24h uptime figure above and does not, by itself, earn a line in this log. When an entry is added, it names which of torzon's five endpoints was affected and for roughly how long, rather than a vague "there was an issue."
Mirror history
Torzon currently carries five monitored onion endpoints on file, the largest set among the seven markets oniongate tracks, and that count is itself a data point worth logging over time: an operator who consistently maintains five working mirrors is making a different operational bet than one running a single address. oniongate records mirror-count changes here when the signed directory oniongate draws from adds or drops a torzon address, so this log is the place to check whether today's five-mirror figure has held steady or shifted recently.
A worked example: reading a split reading across torzon’s five mirrors
What it looks like when two mirrors disagree
Say three of torzon's five monitored onion addresses read Online in the same cycle while two read Down. That is not a contradiction to resolve into one headline number — it is five independent probe results, and the honest summary is exactly that split, not an average that would obscure which specific endpoints actually failed. Check the mirror table below this section for which of the five addresses is affected before assuming torzon itself is having a bad day.
Why picking the first mirror in the list is not a strategy
With five addresses on file, it is tempting to just try the top one and move on if it fails. A better habit is checking this page's current per-mirror readings first, since the list order here reflects when each address was added to the signed directory, not which one is currently most reachable. The mirror actually reading Online right now is the one worth trying, regardless of where it sits in the table.
Before you copy a torzon onion address from anywhere else
oniongate only vouches for a torzon onion address that appears in the signed directory referenced on the about page. If you found a torzon address on a forum, a paid ad, or a search result, treat oniongate's status page as one input among several — a reading of Online here confirms the specific address you check reaches something, it does not confirm that something is genuinely torzon's own infrastructure rather than a convincing copy sharing the same reachability profile.
Torzon as a darknet market: what oniongate's status actually verifies
Torzon 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 Torzon's onion address answered a Tor request within the timeout window on the most recent probe cycle. Nothing about Torzon's inventory, its vendor base, or any uptime claim Torzon makes on its own front page factors into this reading — oniongate did not consult Torzon'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 Torzon status page does not do that. Reachability over Tor is the only signal this page reports, and every other question about Torzon — whether it is a good market to use, whether its escrow is sound, whether its vendor base is currently active — belongs to Torzon's own reference material, not to this status reading.
How often Torzon's Tor status actually changes
Most probe cycles produce no change at all: Torzon'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 Torzon'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.
Torzon's mirror count and what it means for this status page
Torzon currently ties mars for the largest mirror set oniongate tracks across the seven markets on the board, which means torzon's overall status on oniongate reflects several independent Tor probes rather than one. A market with more mirrors on file gives a status page like this one a fuller picture of the market's own reachability, since a single onion address going quiet is weighed against the others rather than standing in for the whole market's status by itself.