Torzon Updates

Published · Updated

Torzon Updates is the TorzonWatchers changelog of hostname changes, operator notices, and Tor Browser reminders relevant to verified rows in the hub table. This Torzon Updates feed is research-oriented and exists for educational purposes only — every Torzon Updates entry is dated, scoped to one rotation event, and cross-linked back to the verified hub when readers need a current hostname.

2026-05-18 — Secondary mirror rotation

TorzonWatchers replaced the secondary row in the hub table after a signed operator notice published a new v3 hostname. The primary row was unchanged. If your bookmark used the old secondary, it will time out until you copy the new line from the hub. This Torzon Updates entry is the only confirmation we publish about the rotation; ignore unsigned chat forwards claiming alternate hostnames.

In-service news panel observed inside a verified Torzon mirror — headline 'DDoS Update' with a reminder to save private mirrors, surrounded by Top Vendors and Welcome, Admin context
Corroborating evidence · 2026-05-18 review · In-service news panel posted by the remote operators inside the primary mirror, referencing public-mirror DDoS conditions and the use of rotating mirrors. TorzonWatchers cross-checks this in-service notice against the cleartext PGP-signed message before changing any row in the verified hub table — the screenshot itself is never sufficient on its own.

2026-05-10 — Archive row marked slow

The archive hostname was kept for reference but noted as high-latency during the TorzonWatchers review. Use the primary or secondary rows for normal reading. See the status notes for timeout observations recorded during that check. This Torzon Updates note exists to head off "archive is dead" reports — slow is not dead.

2026-05-03 — Tor Browser 14.x reminder

Several "the site is broken" reports traced back to outdated Tor Browser clients, not a remote problem. Update from the Tor Project download page before swapping mirrors. Setup steps: How to Open Onion Links in Tor Browser. Torzon Updates flags Tor Browser version warnings because outdated clients are the single most common cause of false outage reports.

2026-04-21 — Primary unchanged, elevated timeouts

The TorzonWatchers review logged longer load times on the primary hostname with no edit that day. No table change occurred. If you only saw slowness, wait and retry; if you saw hard failures on every mirror, read tor browser not connecting. Torzon Updates records elevated-latency days even when no rotation happens so the operational history is auditable.

2026-03-29 — PGP key rotation reminder

A signed operator notice referenced a forthcoming PGP key rotation. TorzonWatchers re-imported the new public key alongside the old fingerprint for verification continuity. Future Torzon Updates entries will reference the rotated fingerprint where applicable. Readers who store the operator fingerprint locally should compare it against the fingerprint summary on About TorzonWatchers.

How often Torzon Updates publishes

Torzon Updates entries land when the hub table changes, when a review notes a pattern worth a short warning, or when a Tor Browser release affects how the onion network behaves. There is no fixed Torzon Updates schedule — a missing week here does not mean nothing happened, only that nothing required a logbook entry. Check the verified hub table directly for the current canonical row.

What Torzon Updates does not cover

  • Vendor announcements unrelated to hostname or PGP verification
  • Forum drama or seizure speculation (background reading lives on history)
  • Real-time "is it up" pulses — see the status notes logbook instead
  • Promotional copy of any kind — Torzon Updates is editorial verification only

What to do next