Onion Site Not Loading
Onion Site Not Loading is the TorzonWatchers status logbook for whether each documented hidden-service mirror returned a page during our last review. An onion site is "not loading" when Tor Browser shows connected but the hidden service never responds — timeout, blank tab, or TLS-style error on misconfigured clones. This onion site not loading log records what TorzonWatchers observed; verified hostname strings stay on Torzon Market Links. Coverage here is published for educational and research purposes only.
Last hidden service review (UTC)
| Check | Result | Timestamp |
|---|---|---|
| Primary mirror reachability | Loaded login/captcha gate after ~90s | 2026-05-18 14:22 |
| Secondary mirror reachability | Loaded after ~140s | 2026-05-18 14:25 |
| Archive mirror | Timeout at 180s | 2026-05-18 14:28 |
Slow loads during a hidden service review still count as reachable. A hard timeout means TorzonWatchers could not complete a handshake in the window used that day. The onion site not loading symptom can mean either a remote-side problem or a local Tor Browser fault — keep reading.
Is the hidden service down or is the onion site not loading on your end?
Remote slowness: Both mirrors respond but take minutes. Your Tor Browser is probably fine. Retry off-peak hours or use the secondary row on the hub table.
Remote timeout in our log: We could not load the hidden service in Tor Browser during that review. That does not prove permanent shutdown — mirrors rotate. Read the changelog before you trust a replacement from a chat app.
Local Tor failure (not a remote problem): Every onion site breaks for you, including known-good test hosts. Fix Tor with tor browser not connecting instead of refreshing mirrors.
Why a hidden service looks offline in 2026
- Operator-side DDoS mitigation throttling new Tor circuits to the onion.
- User pasting a burned hostname from an old forum post instead of the verified table.
- Outdated Tor Browser build with deprecated behavior against current hidden-service endpoints.
- System clock drift breaking circuit creation to any onion hostname.
- Pluggable-transport bridge failure on a censored network.
How TorzonWatchers measures onion site not loading
Onion site not loading is measured by direct observation, never by automated uptime scripts. A reviewer opens Tor Browser, pastes the hostname from the verified table, and records what happened in the timestamp table above. There are no green/red badges and no fake "live" indicators. If the onion site not loading symptom persists across reviews, the row eventually moves to "archive only" in our notes and a short message goes to the changelog.
Tor Browser status indicators that look like a hidden-service outage
Two patterns get reported as "the site is down" when the real cause is local Tor:
- Connecting wheel for 5+ minutes. This means Tor itself cannot build circuits. Every onion site not loading at once is a Tor problem, not a hidden-service problem. See tor browser not connecting.
- Captcha succeeds, then nothing. This means the onion responded once, then the circuit dropped. Try New Identity in Tor Browser; if it repeats across every hidden service, suspect Tor again.
What TorzonWatchers does not publish on status
- Live "up/down" badges tied to clickable onion links.
- Promised response times or uptime percentages for any mirror.
- Claims that a mirror is "guaranteed online" right now.
- Real-time "up/down" alerts — this is a logbook, not a monitor.
Verified hostname strings stay on the hub table. This status page is observational notes only.
Reference material for onion site not loading
Interpreting an onion site not loading symptom is easier with official Tor guidance. TorzonWatchers cites primary sources only: