Nexus Market Status
Live mirror, login, escrow & vendor dashboards

A practical diagnostic ladder for users who can't reach the platform but the public probe says it's up.

Step one: verify your Tor Browser is on a current release. Old releases have known guard-rotation bugs that surface as “not working” against new mirrors specifically. Step two: New Tor Circuit for this Site, retry. Step three: try the sibling mirror — if the headline fails, switch to backup A; if backup A fails, backup B. Step four: if all three fail, wait five minutes and retry once before treating it as a platform-side issue.

If steps one through four all fail and the public probe says the platform is up, the bottleneck is local to your Tor circuit topology. The probe runs from a different vantage and may be successfully reaching mirrors that your circuit cannot. Refreshing the entire Tor Browser session typically resolves these cases within a single restart.

Read the error, not the symptom

Not found means the lookup failed before any connection existed and reloading changes nothing. Disconnected means the record was found and the service did not answer, which often clears in minutes. A connection failure usually points at a relay in your own path. Three different failures at three different stages, and people treat all of them as the site being down.

The order that saves time

Wait out one full attempt before judging. Request a new circuit for the site. Try another mirror. Only then conclude anything. Reloading the same address repeatedly is the one approach that never resolves anything and it is what most people do.

A spinner with no error

Time it. Under twenty seconds points at the lookup, twenty to sixty at your circuit and the introduction step, over a minute at load on the far end. The clock tells you which stage failed without any tooling at all.

Text loads and images do not

That is a bandwidth problem rather than an outage. Your circuit has acceptable latency and poor throughput, and a new circuit is the only real fix. Waiting does nothing, because it is a ceiling rather than a queue.

← Full live status dashboard

90-day uptime
99.92%
Active mirrors
3 / 3
Median latency
117 ms
Open incidents
none

Working Nexus Market URL · verified mirrors

90 days ago fewer outages → now

Component states, the 90 day uptime history and the incident log live on the status dashboard. This page covers one question in depth rather than repeating the board.