The reserve node is the deep fallback. Its job is to answer when the primary and secondary are both under pressure at the same time, which is uncommon but is the exact scenario a single-address market cannot survive. If the first two are stalling across fresh circuits, this is the node to reach for.
Availability is the lowest of the three at around ninety-eight percent, which still means it is reachable the large majority of the time. The figure is lower mainly because this node is exercised less, so a brief dip weighs more heavily in the percentage. It is not a warning sign.
Latency reads around three hundred twenty milliseconds and can climb right after a rotation while descriptors propagate through the Tor network. A minute of patience is normal here. If nothing renders after that across a couple of circuits, check the status log for a wider event.
Same verification, every time. Copy from the explorer, compare against the captcha, never type from memory.
| Date | Event | State |
|---|---|---|
| 2026-03-11 | Descriptor propagation lag on the reserve node | info |
| 2026-02-04 | Lookalike address circulating outside the signed pool | advisory |
| 2024-09-01 | Explorer began indexing the Osiris pool | info |
