Nexus Best Open Library
An open collection of assessments, comparisons and measurement notes on Nexus Market and the Tor marketplaces it is usually ranked against. Every entry states its criteria and its limits.
Full catalogue · Criteria · Questions · Glossary · Verified addresses · Method
Library / Catalogue / Uptime and address rotation
Keywords: uptime, resilience, mirrors, flood, Tor circuits
Two causes account for nearly everything a user experiences. The first is local: a Tor circuit that has degraded, which affects only you and is fixed by requesting a new one. The second is a flood aimed at the service itself, which affects everybody trying that address and passes on its own timescale, usually minutes.
Neither is a market disappearing, which is the conclusion users reach fastest and correctly least often.
Running one address means one target. A flood against it removes the market for everybody until it subsides. Running several means the flood has to find and hold every address simultaneously to achieve the same effect, which is a materially harder problem and is why redundancy is a structural property rather than a convenience.
For a user the practical consequence is small and specific: when one address is slow, another is usually not, and switching costs nothing because the account, balance and orders live behind all of them.
| Observation | Likely meaning | Reasonable response |
|---|---|---|
| One address slow, others fine | Flood or load on that address | Switch address |
| All addresses slow, other onion sites fine | Heavier wave against the service | Wait, retry later |
| All onion sites slow for you | Your own circuit or connection | New circuit, restart browser |
| All addresses gone for days, no signed word | Genuinely unusual, warrants caution | Do not go searching for replacements |
Downtime itself costs a user nothing but patience. What costs money is the reaction to it, because an outage is precisely when people search for an alternative address and accept whatever a search result offers. Almost every phishing loss follows that sequence, which makes waiting a technique rather than an absence of one.
nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onionnexusma2iegzo7atzwbrwxhcdopyri3vare2twibldnlc3txqjdeb5yd.onionnexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onionOpen in Tor Browser only, and compare the onion on the login screen against your address bar before entering a password.