The three-mirror layout on Anubis Market is intentional and the architecture matters. Each mirror sits behind a different guard pool on the Tor network, which means a flood targeting one address does not affect sessions on the other two. The platform stages new mirrors before retiring old ones, which means rotations happen with zero gap in service.
Primary takes the bulk of buyer traffic and sits behind the platform anti-DDoS challenge layer. Most users land here and stay here.
Backup A absorbs spillover when Primary is under load. Tuned for vendors during high-volume settlement windows. Lower hit rate but consistent latency.
Backup B is the explicit failover. Lower-throughput guard relays on purpose, intentional latency budget, present so the rotation never has fewer than three live mirrors.
Live table with copy buttons on the profile page.
| Role | Address | Lat | |
|---|---|---|---|
| Primary | anubisqr57mqcf3vfqv3hknwbpux5ioqs6atmpwrqive6x6wrkdtrwyd.onion |
142 ms | |
| Backup A | anubisgrlku6ohajojoq52kr6nzixtkfp3jc3pdncgdoykgyfxfutgyd.onion |
178 ms | |
| Backup B | anubisrjpfcc43t4r4zl5ovayivjxqkn63ykkzfngjqvk26lnbgcyryd.onion |
214 ms |