Status & Reachability FAQ

As of the sweep timestamped at the top of the mirror status table, all three Torzon onion mirrors answered our probes. If you cannot reach any of them, first rule out your own network — a single blocked transport is far more common than a genuine three-mirror outage. The downtime guide shows how to tell the two apart.

Every value carries the timestamp of the sweep that produced it. We publish documented readings on a roughly 15-minute cadence. This is not a live streaming board, and we never display a green status we did not actually measure. If a timestamp looks old, treat the figure as stale and re-check.

That means the endpoint is up and the block is local to your network or transport. Compare your result with the unfiltered control row on the matrix, then switch transport (obfs4 → snowflake → meek-azure) and, if needed, switch to another mirror. The full sequence is in the downtime guide.

Slow means the mirror answered but above its latency band. Intermittent means some attempts in the sweep succeeded and others timed out. Blocked means every attempt for that region and transport timed out. If the control row also failed it is a real endpoint incident; otherwise it is regional filtering. Definitions live on the monitoring page.

Use whichever the status table shows reachable with the lowest latency from your transport. As a rule of thumb, Mirror A pairs with obfs4, Mirror B with snowflake, and Mirror C with meek-azure. The region matrix shows the current best pairing for each area.

No. Reachability and authenticity are separate checks, and an imposter endpoint can be perfectly reachable. Always verify the 56-character v3 address against the signed manifest using the published fingerprint on the Verify page before you rely on it.

For each mirror we count the sweeps in the trailing 30 days where it answered from at least one probe region within the timeout, divided by the total number of sweeps. "Slow" counts as up; "intermittent" counts as up if any attempt succeeded. It is a connectivity figure, not a marketplace service-level guarantee. The maths is documented on the monitoring page.

Censorship is transport-specific. A firewall may enumerate obfs4 bridge IPs while leaving snowflake's WebRTC churn alone, or permit only HTTPS to known CDNs, which favours meek-azure. That is exactly why each transport is measured separately rather than reporting a single "Tor works / does not" verdict.

No. Torzon Status is an independent connectivity monitor. We do not operate the marketplace, hold escrow, vet vendors or process any order — and we have no visibility into anything behind the login by design. We only document whether the onion mirrors are reachable. More on the about page.

No. The site is static, with no accounts, cookies, analytics or visitor logs tied to you. Our probes test the mirrors, not the people reading the results. The full privacy notice spells this out.