The primary node is the first address the explorer recommends trying. It has the longest history in the pool, which on Tor translates directly into faster resolution: an established hidden service has stable descriptor consensus and routes through known-good guards.
Availability over the observation window sits above ninety-nine percent, the highest in the pool. That number is measured from periodic reachability checks across several Tor circuits, so read it as a recent trend rather than a live probe. Every dip is recorded in the status log with a timestamp and a duration.
Latency reads around two hundred milliseconds on a healthy circuit, meaning the anti-DDoS queue and login usually render within a few seconds. If the primary stalls for longer than a minute on your side, the cause is almost always your circuit. Rebuild it and retry, or switch to another node while you do.
Whatever node you use, verify it before entering anything. Copy the address from this explorer, hold it against the address the login captcha prints, and never type a fifty-six character string from memory. See verifying a mirror.
| Date | Event | State |
|---|---|---|
| 2026-05-22 | Flood window raised queue times on the primary node | minor |
| 2026-02-04 | Lookalike address circulating outside the signed pool | advisory |
| 2024-09-01 | Explorer began indexing the Osiris pool | info |
