Nexus expanded its .onion mirror network from four to seven nodes in early January 2026, following a successful stress test of the expanded infrastructure during the holiday period — traditionally one of the highest-traffic periods for online marketplaces of all types.
Mirror nodes operate independently with separate hardware, hosting providers, and geographic locations. Each mirrors the full marketplace functionality and is cryptographically authenticated by the platform's master PGP key — users can verify a mirror's legitimacy by confirming its address appears on the PGP-signed official mirror list.
Why Mirror Networks Matter
Single .onion addresses are vulnerable to targeted DDoS attacks, hosting provider takedowns, and infrastructure failures. A distributed mirror network addresses all three attack vectors: DDoS against one node doesn't take down others; a takedown of one hosting provider doesn't affect independently hosted mirrors; and hardware failure at one node is absorbed by the remainder.
The three new mirrors are located in different jurisdictions to diversify legal risk: one in Switzerland (strong privacy law framework), one in Iceland (strong digital rights protections), and one in a jurisdiction that declines to disclose its location publicly. All three are operated by trusted independent parties who have undergone the platform's vetting process.
The expanded mirror network also improves load distribution, benefiting all users with faster page loads and more consistent availability during peak traffic periods. Internal monitoring shows average Tor circuit load time has decreased by approximately 18% since the expansion went live.