nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onionnexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onionnexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onionRun the check before you sign in. Open these in Tor Browser only. When the login screen loads, compare the onion printed on the page against your address bar, reading from the end. If they differ, close the tab.
The page appears, you can read it, and the pictures dribble in one at a time or not at all. This is a bandwidth signal rather than a fault, and it tells you something useful about the circuit you drew.
What it means
Page text is a few kilobytes and arrives in one go. A listing gallery can be several megabytes and has to squeeze through the narrowest relay in a six hop chain. When text is instant and images are not, your circuit has fine latency and poor throughput. Those are separate properties and only one of them is bad here.
Why it varies so much between sessions
Relay capacity is wildly uneven. Two circuits built a minute apart can differ by a factor of ten in throughput while feeling identical on text. Nothing you did changed, the draw changed.
What to do about it
- If you only need to read, ignore it. Text is all you need for browsing, and the pictures finishing is not a precondition for anything.
- If you need to see product photos, request a new circuit for the site and reload. A new draw is the only real fix and it costs a fresh cold load.
- Open images one at a time rather than letting a gallery pull twenty at once. Twenty parallel requests on a thin circuit finish slower than five sequential ones.
What it is not
It is not the market throttling you, and it is not your account. Both would show up as errors rather than slow bytes. It is also not something a faster internet connection fixes, since your own link is nowhere near the bottleneck.
How to read the result
Ordinary circuit. Carry on and do not touch anything.
Thin circuit. Fine for reading, painful for browsing photos. Take a new one if photos matter.
Either the circuit is nearly dead for throughput or the market is shedding static files under load. New circuit first, then another mirror.
Other latency signals
Long wait before anything appears
Time to first byte on an onion service includes six relays and a rendezvous. What is normal for a Nexus mirror and when the number stops being normal.
LatencyThe session freezes partway and then resumes
Pauses in the middle of a working Nexus session usually mean a relay dropped and the circuit is being rebuilt. Why waiting beats reloading.
LatencyUploads and large pages stall out
When image uploads to a Nexus mirror stall at a percentage or big pages stop halfway, the circuit has run out of usable bandwidth.
Procedures that apply here
Requesting a new circuit, and when it actually helps
The single most useful control in Tor Browser for onion problems, what it does, what it costs and which symptoms it fixes.
MethodChoosing which of the three mirrors to use
The three Nexus addresses reach the same market. How to pick between them sensibly and why the fastest one today may not be tomorrow.
MethodHow to take an honest reading of a mirror
A repeatable way to measure whether a Nexus mirror is slow, broken or fine, without tooling and without fooling yourself.