Nexus Panel BoardPanels of numbers this site works out for itself
Route

Why the path keeps changing

The path between you and a service is not a fixed thing, and several confusing symptoms come straight from that.

Addresses in the set
3
addresses published
Positions where all three agree
6
positions where all three agree
Agreement across positions
6
all
two
none
positions where exactly two agree
Positions where all three differ
44
positions where all three differ

Nexus market addresses in this board

copy, do not retype
nexusb2l73qzjn4slhyfxa3jvpolw7fomiz5sgyyefnsdhikaqgborqd.onion
nexusma2iekjhhyenua3u4zlyfsj2ubwxr2nt6gdte5rvwukzze63fyd.onion
nexusabcdbnjw6or46y3hh6uicsl4xvu5cncfp27hkggznvtxhxlngad.onion

Printed as supplied, in no order, with nothing marked best or main. This board never opens an address, so nothing on this page says one of them is reachable for you now.

What stays fixed and what does not

The address is fixed. It is the same 56 characters every time and it identifies the same service regardless of anything else. That is the stable half.

The path taken to reach that service is not fixed. It is assembled, used, and later replaced, and the replacement happens on its own schedule rather than when you ask. Two loads of the same address minutes apart may travel entirely differently.

The symptoms this explains

  • A page that was slow and is now fine with nothing having changed at your end.
  • A page that was fine and is now slow, likewise.
  • One address behaving differently from another for a while, then not.
  • A load that fails once and succeeds immediately afterwards, which people usually attribute to their retry rather than to the change underneath it.

Why this makes personal experience unreliable

If you form an impression of an address over several visits, you are averaging over paths you did not choose and cannot see. Two people using the same address at the same moment can have genuinely different experiences, and both impressions are accurate about their own path and useless as a general statement.

This is why the board refuses to publish anything about how the addresses perform, even though it would be the easiest content in the world to write. Any such statement would be one observer generalising from a sample of paths, and there is no honest way to present that as information.

What the tiles are doing here

They compare the three published strings position by position: how many positions all three share, how many split two against one, and how many differ entirely.

The relevance is indirect but real. Because the three are almost entirely different from each other, they are genuinely separate destinations reached by separate paths. Switching between them is a meaningful action rather than a cosmetic one, which is the single most useful response to a path problem.

What not to conclude

Changing paths is not something going wrong. It is ordinary behaviour and the system is designed around it. The reason to know about it is not to worry, it is to stop over-interpreting your own experience.

Specifically, it means a single bad session is not evidence about an address, a single good session is not evidence either, and a run of either one is a small sample of paths rather than a fact about a destination.

A note on control

There are ways to influence path selection, and this board is not going to walk through them. They are the kind of adjustment that helps in specific circumstances and makes things worse when applied as a general habit, and a reference site is the wrong place to be nudging people into changing defaults.

What is worth saying is that the defaults are chosen so that everybody looks alike, and that being unremarkable is most of the value on offer. Any change that makes your setup distinctive costs something that is hard to see and hard to get back.

What to write down when something odd happens

Because the path underneath you moves, a symptom you noticed ten minutes ago may be impossible to reproduce. That is frustrating, and it has one practical consequence worth acting on: if something unusual happens, note it at the time rather than intending to look into it later.

What is worth noting is small. Which address you were on, what you saw, and whether ordinary browsing was affected at the same moment. Those three facts are enough to distinguish most of the categories on this board later, and none of them survive an hour in memory.

What is not worth noting is a timing. A duration measured once, on one path, is a fact about that path and nothing else, and writing it down tends to turn it into a baseline you compare everything against. That is how people end up with a firm belief that one address is slow, which the distance measurements on this board exist partly to argue against.

Reading this panel wrong

3 ways it happens
  1. Reading the agreement bars as anything about paths.They compare three strings to each other. No path is measured anywhere on this site.
  2. Treating a run of good sessions as a fact about an address.It is a sample of paths you did not choose. The next path may behave completely differently.
  3. Assuming a changing path means something is wrong.It is ordinary. Knowing it happens is what stops the symptoms being mysterious.

What this panel is not: a network explainer. It says which everyday symptoms come from path changes and stops there.

Nearby panels

Every panel on the board

68 pages
Strings
How long each address is The symbols an address can contain The opening all three share Where the three part company Digits, and where they fall What repeats inside an address How far apart the three are The character they all end on
Reading
Symbols the eye trades What a front and back check proves The part nobody reads Reading an address in blocks Copying rather than typing The stretches you cannot say Reading an address out loud What a check cannot reach
Route
What the browser is doing The first load of the session When a page loads slowly Why the path keeps changing What each step can see The screens that mean failure Where the address lives between visits Where the address came from
Session
The name you choose The login screen How long a session lasts What stays behind Two tabs, one account Ending a session on purpose Losing access Encrypted text in a session
Money
The deposit address Waiting for confirmations What escrow holds Where the cost sits Rounding and leftovers Taking a balance back out The waiting, laid out The steps you cannot take back
Orders
Before the order exists Placing the order The delivery details Between placing and dispatch What tracking does not say Finalising When it goes to dispute The feedback you leave
Corpus
How much is on this board How the panels are distributed How long a panel is The tiles, counted Which phrases the board uses What is deliberately left out How the panels connect The tiles that come back empty
Reference
All panelsHow the numbers are madeThe addressesWhat this board covers