Three production mirrors on the current rotation, prober-checked every ten minutes. Copy from the home page table; the entries below are reference for what to expect.
Anubis publishes three mirrors and runs them in parallel. The Primary takes the bulk of buyer traffic and lives behind the platform's primary anti-DDoS challenge layer. Backup A absorbs spillover during peak windows. Backup B is the explicit failover, on lower-throughput guard relays with intentional latency budget.
The reason for the triad is simple: a flood targeting one address does not affect sessions on the other two, and the platform can stage and verify a new mirror before retiring an old one, which means zero-gap rotation. The full live table with copy buttons is on the Anubis Market profile page. Bookmark the directory rather than any single mirror; the rotation refreshes on every prober cycle.
Which mirror should I use?
Primary first. If the challenge layer times out on your circuit, switch to Backup A. If both fail, use Backup B. If all three fail, the platform is dealing with an active flood. Hit "New Tor Circuit for this Site" in Tor Browser, give it a few minutes, retry.
