Every torzon market link change we have ever recorded, in one table, with the date we first noticed it and the date it dropped. Plus monthly uptime percentages from our own 5-minute ping job, plus a short (and honest) recap of every incident we saw. We keep it like a changelog, because that's what it is.
Why bother? Because when a user lands on Google and sees five “TorZon” blog posts, three of them are referencing an onion that stopped responding 14 months ago. Knowing that a link went dark in, say, June 2023 is the difference between trusting a guide and throwing it out.
3
infra migrations
2
onion rotations
99.1%
rolling 30-day uptime
1.8s
avg response (onion)
Link-change log
Old addresses first. If you see one of the red "offline" rows being used anywhere as a “fresh” TorZon link, that’s a red flag — it’s a clone or an old cached listing.
From
To
Address (tail)
Type
Status
2022-09
2023-05
…sduqk7vnhlewmk3vgad.onion
Onion v3 (original)
offline
2023-05
present
…hgad.onion (the canonical one)
Onion v3 (primary)
up
2023-02
present
torzonmarket.com
Clearnet mirror
up
2023-11
2024-04
tzm.link
Clearnet short (temp)
offline
2024-06
present
trzm.cx
Clearnet short
up
2023-07
2024-02
…torzon-clone-…onion
Phishing clone (caught)
sinkholed
Monthly uptime — onion v3
Pings from 3 independent Tor clients every 5 min. Any month under 95% is usually a visible DDoS period; see the incident recap below for the why.
Month
Uptime %
Avg resp
Note
2025-11
99.4%
1.7s
clean
2025-12
99.0%
1.9s
short DDoS 12/19 (~2h)
2026-01
99.6%
1.6s
clean
2026-02
97.8%
2.3s
circuit churn, no outage
2026-03
98.2%
2.0s
infra migration weekend
2026-04 (so far)
99.1%
1.8s
healthy
Security incident recaps (short)
2023-05 — onion rotationOriginal onion voluntarily retired. No known breach; admins cited “key hygiene”. Old onion now points nowhere. Everyone yelling “TorZon is seized!!” on Dread was wrong. We logged ~5 days of confusion before the new one stabilized.
2023-07 — phishing clone waveSeveral clones with 1-char-off onions appeared, promoted via scam posts. Confirmed phishing, credentials harvested. Patch: user education + this site’s copy-from-canonical message.
2023-12 — DDoS (week-long)Sustained HS DoS. Market responded by deploying an onion balancer setup. Users saw ~40% timeouts until it settled.
2024-04 — clearnet mirror tzm.link lapsedDomain expired. Replaced by trzm.cx in June. No user impact except people still typing the dead domain.
2025-12 — brief 2h outageUnclear cause (network, not compromise). Back up without data loss. Logs matched.
2026-03 — infra migration weekendPlanned maintenance. Slight slowdown (2.3s avg). No onion change.
Response-time snapshot (last 24h)
Rough buckets, not a graph — because the graph takes JS we refuse to load on a page like this. If you need finer granularity, email the monitor alias in the footer.
torzonmarket