Anubis Market Down

You are here because the market will not load. Most of the time the market is not down. The order below separates your client from the server, and it takes about five minutes. Start at the top and stop as soon as something fixes itself.

Test every address before calling it dead.

anubisq6kqiq5ttmrrnj3pyxssmnaxurl76flaegbtzbcwtes3vomiid.onion
anubisqdpukalgiyxlb7rtcya3u6grun2mcozonmb57c54qrt7sqh7qd.onion
anubisqe2yramasw5yvlnipaknraza5rzb5uxb7zqhxuxroobvvm6aid.onion

First, check the mirrors

Three addresses exist for one marketplace. Do not assume failure until you test every single link listed above. Give each mirror two minutes of connection time before judging it dead. The Tor network routes packets through multiple relays, which adds latency. A slow load does not equal a broken server. Your login credentials and cryptocurrency balance reside on the central database, not the specific onion domain. Switching from one mirror to another changes nothing regarding your inventory or wallet history. If one address times out while others respond, that specific node likely suffered a temporary routing issue. Check all three options systematically.

What usually causes it

Your local Tor circuit might be congested or stuck on a bad relay. Force a new circuit in the browser settings if pages hang indefinitely. Local network interference or aggressive VPN configurations often block the connections needed for stable routing. Sometimes, distributed denial of service attacks target one specific address while leaving the others untouched. In those moments, one link looks dead, but the remaining mirrors stay fully operational and responsive. Scheduled rotations also interrupt service briefly. New addresses get prepared in advance to minimize downtime during these shifts. Announcements go out on this page first whenever a planned rotation happens. Most perceived outages result from client-side issues rather than server crashes. Verify your own setup before assuming the entire platform has failed completely. Circuit specifics are in slow circuits and how to fix them.

What we monitor

Servers run availability checks every ten minutes across all active mirrors. Automated scripts ping endpoints and log response times continuously. When two or more mirrors drop simultaneously, the incident triggers an immediate public notice on this page. Historical data shows most incidents resolve within hours, not days. Short blips rarely exceed an hour. Complex failures involving hardware replacements take longer but happen infrequently. The monitoring system distinguishes between total outage and partial degradation. If only one mirror fails, the site remains accessible via the others without urgent alerts. This consistency helps maintain trust and reduces unnecessary panic among regular users during minor technical hiccups.

When to worry

If all three addresses fail to connect for more than twenty-four hours, contact us directly. Send a message to our published PGP key with details of your attempt. Before writing, verify your internet connection independently using other services. Confirm your Tor version matches the latest release recommended by developers. Note down the exact time when the issue started, relative to UTC. Provide screenshots of error messages if available. We prioritize verified reports over vague complaints. Patience helps, but silence beyond one day warrants direct communication through the encrypted channels provided for support inquiries. If you suspect a clone instead of an outage, read the phishing guide.