You expect an error to mean the market is gone
WeTheNorth addresses
hn2paw7zadwkcra3qzv5e4q547i7e5lvxm62cfxqftuqdu7moiu2ceyd.onionhn2paw7zfvndw3dovycegeqmvvnf4pl67b3g2p7pohjlzavloosh73id.onionhn2paw7zrgujyhnt6mgxlt2q6uhgbke4itpqitxhyfbumq3wtnckbuyd.onionPrinted as supplied, in no order. Nothing here is checked or timed, so an address that opens is not proof of anything. more about the set
I got an error page. It is down, or it has been seized, or it exited.
Most failures happen on the route, not at the destination. The error text usually names which layer gave up, and the layer is rarely the market.
The gap: one failed attempt is being read as a fact about the world.
Why the jump to the worst case
Because the worst case is the story everyone has heard. Markets do disappear, and the memory of that is vivid enough to fill any gap in information. An error page contains almost no information, so the vivid story fills it. This happens fastest to people with money sitting in an account, which is also the group least able to think clearly about it.
What the layers are
| Where it broke | What it usually means |
|---|---|
| Cannot find the descriptor | The lookup for that address failed. Often the directory system, sometimes the address is wrong or retired. |
| Cannot connect to the service | The descriptor was found. Something answered. The rendezvous did not complete. |
| Timeout with no message | A slow or dead relay in your circuit. This is the most common failure of all. |
| A page from the site saying it is busy | You reached the market. It is shedding load. This is the door working. |
| A browser error about the connection | Your own client, proxy or network. Nothing to do with the destination. |
Only one row on that table is about the market at all, and it is the one where you actually got a page. The rest are about the road between you and it.
A cheap sequence before concluding anything
- New circuit for this site, then reload. This alone clears most of it.
- Try the second address from your stored set, then the third. Different keys, different infrastructure.
- Restart the browser so the whole client state is rebuilt.
- Leave it an hour. Load and attacks both pass.
- Only after all of that, go back to a source you can name and see whether the set has changed.
Notice that the last step is the one people do first. Searching for a new wtn market address at the moment of failure is how a bad address gets into circulation, because the search happens in exactly the frame of mind that skips checks.
What this board will not tell you
Whether an address is up. Not on this page, not on the addresses page, not anywhere. No checks are run here, nothing is probed and no status is stored. Any site telling you a specific onion is up right now is telling you about a request it made from somewhere else, at some earlier moment, over a circuit that was not yours. Your own attempt is better evidence than that, and it is the evidence you already have.
Related: a slow page means a fake and the address will keep working.
Questions people send about this
Everything failed for an hour. Is it gone?
An hour is a normal outage on this network. Sustained failure across an entire set over days is worth taking seriously, and even then the first check is your own connection.
Can I tell a seizure from an outage?
Not from an error page. A seizure typically replaces the site with a notice, which is a page rather than a failure.