Osiris mirror pool: the live node list
Three production nodes on the current rotation. Pull the host from the table on the home page; the notes below describe what each node is provisioned for.
Osiris runs three onion endpoints in parallel. The Primary carries the bulk of session traffic and sits behind the platform's front-line anti-DDoS challenge layer. Backup A is provisioned to absorb spillover during peak-load windows. Backup B is the explicit failover, parked on lower-throughput guard relays with a deliberately higher latency budget.
The triad exists so a flood aimed at one host does not touch sessions on the other two, and so the operator can stage and health-check a replacement node before draining the one it retires. That is the zero-gap rotation model. The full node list with copy controls is on the Osiris profile page. Pin the directory, never a single host.
Which node do I hit first?
Primary by default. If the challenge layer stalls on your circuit, fail over to Backup A, then Backup B. If all three time out, the platform is absorbing an active flood: trigger New Tor Circuit for this Site in Tor Browser, hold a few minutes, then retry.