Three addresses, one market. Same account, same orders, same balance behind each one. No accounts, no forms, nothing collected
Nexus Mirror Signals

The three Nexus Market addresses, and how to read them

All three onion addresses are below. They reach the same market with the same account and the same orders behind each. Copy one, run the check, and if it will not open the rest of this site tells you exactly what the screen is trying to say.

Nexus Market onion addresses3 live · same market behind each
nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onion
nexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onion
nexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onion

Run 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.

It will not open, what now Signal reference

Twelve signals, five procedures and the normal timing ranges to compare against. Free to read, nothing to sign up for. Most problems end at taking a proper reading.

Why this exists

A status page cannot tell you the truth about an onion service

Every uptime figure you have seen for a hidden service was measured from somewhere that is not your machine, over a circuit that is not yours. It is a statement about somebody else evening. These four ideas are what this site is built on instead.

01

Reachability is yours, not theirs

Your path crosses about six relays. Any of them can be the reason a page will not open, and none of them appear on a dashboard. Half of all apparent outages are one unlucky relay in your own circuit.

02

The error text is the diagnosis

Not found, disconnected and connection failed are three different failures at three different stages. People treat them as one thing called down, and then apply the wrong fix and repeat it.

03

Slow is not broken

Tens of seconds for a cold load is the design working. Knowing the normal range stops you switching addresses at fifteen seconds and paying the setup cost all over again.

04

One signal ends the session

Everything here is a diagnosis except the address check. If the onion on the page and the onion in your bar disagree, there is nothing left to investigate.

Signal reference

Twelve things a Tor Browser can tell you

Grouped by where they break. Reachability signals end in an error, latency signals end in a slow page, and integrity signals mean the page arrived and something about it is wrong.

0xF0 Onionsite Not Found 0xF2 Onionsite Has Disconnected 0xF3 Unable to connect to the onionsite REACH No error page, just a spinner that gives up LATEN Long wait before anything appears LATEN Text lands fast, images crawl LATEN The session freezes partway and then resumes LATEN Uploads and large pages stall out INTEG The address on the page is not the address in your bar INTEG The protection gate never lets you through INTEG Logged out on every page you open INTEG The page loads but half of it is missing

Open the full reference

Tell the three reachability errors apart

Not found means the network could not say where the address lives, and a retry almost never helps. Disconnected means the record was found and the service did not answer, which is a far better sign and often clears in minutes. Connection failed usually means a relay in your own path let go.

The fix is different in each case, and applying the wrong one is why people spend an hour reloading a page that was never going to load.

0xF0 points at the address itself
0xF2 points at load or a restart
0xF3 points at your circuit
No error at all points at the clock
Start with the not found error
Failure stage by error
0xF0descriptor lookupstop
0xF2service answerretry
0xF3introductionrecircuit
nonetimeout, silenttime it

Know the normal range before you judge a mirror

A cold first load has to find the descriptor and build both halves of a rendezvous before a single byte comes back. Eight to forty five seconds is healthy. Under real traffic, two minutes is still the network doing its job rather than failing at it.

Every page after the first rides the circuit you already paid for, which is why one long session beats four short visits by a wide margin.

Cold load, 8 to 45 seconds
Warm load, 1 to 6 seconds
Busy cold load, up to 2 minutes
Over 2 minutes, take a new circuit
See the full baselines
Latency trace, one session
coldfirst byte31s
warmmedian page3.4s
warmslowest page11s

Latency and throughput are different problems

When the text lands instantly and the pictures crawl, your circuit has decent latency and poor bandwidth. Waiting fixes queues and does nothing about a ceiling. That is why a new circuit is the only real answer to stalled images and stalled uploads, while it is the wrong answer to a slow first byte you have not waited out yet.

Text instant, images slow means thin
Everything slow means queued
Stalls midway means a rebuild
Uploads dying means a ceiling
Read the throughput signals
Same circuit, two measures
latencypage textgood
throughputgallerythin
actionnew circuitcosts a cold load

One check that no copy can pass

A cloned market copies the design perfectly, because the design is handed to anybody who loads the page. What it cannot do is live at the real address, since that address comes from a key it does not have. Print the real onion on the page and the contradiction shows up in your address bar.

Read the comparison from the end backwards. Anybody generating a lookalike spends their effort on the prefix, because that is the part people glance at.

Design proves nothing
A working login form proves nothing
Search ranking proves nothing
The address bar decides
Run the address check
The comparison
page...gyd.onionmatch
bar...gyd.onionsign in
page...gyd.oniondiffer
bar...q7d.onionclose it
Where the time goes

Five stages sit between you and a Nexus mirror

Each one can fail on its own and each one fails in a way you can recognise. This is the whole path, and the last line of every box is what you can actually observe from a browser.

STAGE 01

Directory lookup

Your client works out which relays should hold the descriptor for this address today and asks them for it.

fails fast, under 15s
STAGE 02

Your circuit

Three relays are chosen, starting with a guard that stays the same for weeks on purpose.

slow or intermittent
STAGE 03

Introduction

You ask a relay the service nominated to pass along a request for a meeting.

30 to 60s then fails
STAGE 04

Rendezvous

Both sides build circuits to a meeting relay you picked, and the two halves are joined.

long silence, no error
STAGE 05

The service answers

Now the market itself gets involved, with its own load, its own gate and its own queue.

gates, stalls, thin bytes
Three ways in

Pick the one that matches what you are doing

Something is wrong right now

The triage table. Match what is actually on your screen against twelve rows and it points at the one page that explains it and the one thing worth doing next.

Start here

Signal reference

Twelve entries covering every error message, every slow pattern and every integrity problem, each with what it means, what it does not mean and what to do.

Twelve signals

Baselines

The numbers to compare against. Cold and warm load times, throughput expectations and how often a healthy connection fails for reasons that are nobody fault.

What normal looks like

Runbooks

Five short procedures. Taking a reading, choosing between the three addresses, requesting a new circuit, confirming an address and handling a full outage.

Five procedures
Addresses

The three Nexus onion addresses

All three reach the same market. Keep them somewhere you can find without a search engine, because that habit is what stops a quiet evening turning into a cloned login page.

Nexus Market onion addresses3 live · same market behind each
nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onion
nexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onion
nexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onion

Run 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.

Take a reading before deciding a mirror is down

Two patient attempts on two paths take about three minutes and answer the question properly. Most people give up at fifteen seconds and then spend an hour on the wrong problem.

Read the procedure Common questions