Your onion site went offline and the page just won't load. Before you assume the worst, .onion uptime behaves differently from the ordinary web. A single failed connection rarely means a site is gone for good.
Why onion sites go down more often
A regular website usually sits behind commercial hosting with monitoring, load balancers, and paid uptime guarantees. Onion services often don't work that way.
Many are run by small teams, volunteers, or newsrooms experimenting with privacy infrastructure. The Guardian's team has written about building a Tor onion service and noted that standard uptime monitoring tools don't support onion services at all. They had to build their own simple monitor using crontab and curl.
If a major news organization must build custom tooling just to know whether its onion service is reachable, it reveals something fundamental: checking uptime on Tor is not straightforward.
What the error actually means
Tor Browser gives specific error codes when an onion site fails to load. Learning them beats guessing.
- Onionsite Not Found or Onionsite Has Disconnected: the site is most likely offline. Contact the site administrator.
- Onionsite Cannot Be Reached: there's an internal error on the service's side.
- Unable to Connect to Onionsite: the site may be busy, or the Tor network itself is under load. Try again later.
- Onionsite Requires Authentication: the address is working, but you need a key you don't have yet.
Reading the code before panicking tells you whether the problem is the site, the network, or your own access.
Why a saved bookmark isn't a safety net
Bookmarking an onion address feels responsible. It's useful, but it won't confirm the site still exists or remains legitimate.
Onion addresses can change when an organization rotates keys, migrates infrastructure, or shuts a service down entirely. A bookmark doesn't update itself and won't warn you if the address has been abandoned or repurposed.
Directory pages cause real harm here. Pages claiming to be "the" hidden wiki of working onion links are not safe shortcuts. What exists today is a sea of clones and copycats, often filled with outdated, fake, or dangerous addresses. Treat any such listing as a warning sign.
The safer way to get an onion address
The most reliable method is also the most straightforward: go to the organization's regular website first, the one you already trust, and look for their official onion address there.
Several organizations build this in directly. Onion Browser on iOS ships with preinstalled .onion bookmarks for sites like DuckDuckGo, the New York Times, the BBC, ProPublica, and Deutsche Welle. This gives new users a verified entry point instead of guessing.
If you can't find an onion link on an organization's official page, that absence is useful information. A familiar name is never a safety guarantee on its own. Cross-checking against the clearnet source is what matters.
A temporary outage versus a broken trust signal
When an onion site won't load, two very different situations can be at work.
The first is ordinary technical trouble: Tor network congestion, the service's server restarting, or a volunteer-run project with limited uptime monitoring. This is common and not a red flag by itself.
The second is a changed or dead address being replaced by something else entirely, sometimes quietly repurposed by someone unrelated to the original operator. This is why re-verifying against the organization's official clearnet page matters every time you use a bookmarked address, not just the first time.
Tor gets you there, it doesn't vouch for what's there
Tor Browser routes your traffic through the Tor network, but it does not automatically make your actions anonymous, and it does not verify that a site is trustworthy or safe.
Logging into a personal account, downloading a file, or reusing a username on an onion service can undermine your privacy regardless of Tor. Uptime and trust are separate questions.
What to do right now
If an onion address won't load, work through this checklist instead of giving up or assuming compromise.
- Check the Tor Browser error code first. It often tells you exactly what's wrong.
- Try again later if the message suggests network congestion rather than a dead site.
- Go back to the organization's clearnet website and re-copy the onion address from there.
- Never trust an onion address found only in an unverified list or forum post, especially one claiming to be a directory of "working" sites.
Onion sites can be fragile by design, run by small teams without commercial monitoring. That fragility is normal. The part worth unlearning is treating every bookmark as permanent and every directory as authoritative.