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.
You cannot tell a problem from normal operation without knowing what normal is. These are the ranges to compare your own readings against. They describe onion services in general rather than any promise about a particular address.
Load times
| What you are doing | Normal | Busy but fine | Take action |
|---|---|---|---|
| First page of a session | 8 to 45 seconds | Up to 2 minutes | Over 2 minutes |
| Any page after that | 1 to 6 seconds | Up to 20 seconds | Over 30 seconds |
| Listing page with photos | 10 to 60 seconds | Several minutes | Never completes |
| Uploading an image | 20 to 90 seconds | A few minutes | Stalls at a fixed point |
Why the first page costs so much more
It pays for everything. Finding the descriptor, building your three hop circuit, arranging an introduction, and building both halves of a rendezvous. Every page after it reuses what that first one bought. This is the single most useful thing to know about using an onion service, because it changes how you use it. One long session gets far more done than four short visits across an evening, and closing the browser throws away everything you paid for.
Failure rates that are not failures
- Roughly one connection attempt in five to one in ten failing outright on a busy service is ordinary. Relays go offline mid connection and nothing is wrong.
- A stall of twenty to sixty seconds partway through a working session is a circuit being repaired. It resolves on its own and reloading interrupts the repair.
- Images failing while text works is a bandwidth draw, not a fault. Circuits vary by a factor of ten on throughput while feeling identical on text.
What varies and what does not
| Property | Varies with | Can you change it |
|---|---|---|
| Time to first byte | Circuit draw and service load | Yes, new circuit |
| Throughput | The narrowest relay in the path | Yes, new circuit |
| Descriptor availability | The service publishing | No |
| Gate queue length | How many people arrive at once | No, only waiting |
How these numbers were arrived at
They are the ranges commonly reported for onion services and they match what the design predicts, given six relays and no caching anywhere in the chain. They are not measurements of any specific address and this site publishes no uptime figure, because one measured from somewhere that is not your machine would be a statement about somebody else evening rather than about yours.