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

Home › Signals › The session freezes partway and then resumes

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

Group
Latency
First move
Wait it out
How long to give it
Thirty seconds
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.

Everything is going fine and then a click does nothing for half a minute before the page appears normally. This is a rebuild, and the worst thing you can do to it is interrupt.

What you see. A working session that pauses for twenty to sixty seconds on a single action, then continues as if nothing happened.

What is happening

Circuits are not permanent. Relays go offline, get restarted, or drop connections under load. When one in your path goes, the client notices, builds a replacement path and resends. The pause you feel is that repair, and it usually completes on its own.

Why reloading makes it worse

A reload during a rebuild cancels the request that was about to succeed and queues a new one behind the same repair. You wait for the rebuild either way and now you have also thrown away whatever was in flight. On a form or an order step, that is how a submission gets sent twice or lost.

The rule for anything you were submitting

  • Never resubmit a payment or an order step during a stall. Wait for the page to settle and then check the order state before doing anything.
  • If a message or a form came back blank, look for the result in the account before writing it again.
  • Treat a stall on a payment page as a reason to slow down rather than speed up.

When it is not a rebuild

A rebuild resolves inside about a minute. A pause that lasts several minutes with nothing coming back is closer to the timeout case, and at that point a fresh circuit is the right move rather than continued patience.

How to read the result

Under a minute, resumes

Normal circuit repair. Nothing to do and nothing to fix.

Repeated stalls in one session

One relay in your path is unreliable. Finish what you are on, then take a new circuit.

Stall on a payment step

Stop clicking. Wait, then verify the order state before touching anything again.

Other latency signals

Latency

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.

Normal to a point Latency

Text lands fast, images crawl

Why listing photos on a Nexus mirror lag well behind the page text, what that says about your circuit, and when to stop waiting.

Expected Latency

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

New circuit

Procedures that apply here

Method

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

6 min Fix

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.

4 min Method

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

5 min