Real-time confirmation page for the query population using “live” as their phrasing of choice.
Yes, the platform is live and serving. The probe ran most recently at ; all three production mirrors completed the probe cycle. The 90-day rolling uptime sits at 99.94 percent; the median latency across mirrors is 141 ms; the open-incidents count is one (the standing degraded-latency advisory on the tertiary mirror).
This page is functionally a thin alias of the homepage status panel; it exists to serve the “nexus market live” search phrasing without forcing users to read past the more-typed “status” landing. Bookmark whichever URL you arrived at — the probe data is shared.
That the state shown was produced by a probe rather than typed by hand. It is a recent observation from one vantage point, not a continuous feed and not a guarantee about the next minute.
Reachability for a hidden service is a property of the circuit between a client and the service. A probe builds its own path through its own relays and reports what that path saw. When it says a mirror is up, it means up for a machine that is not yours, over a route that is not yours, at a moment that has passed.
As a first filter rather than an answer. If everything here is failing, waiting is sensible. If it is all green and you cannot connect, the problem is your path and there are two concrete things to try before giving up.
A mirror failing between probe passes, a route that works from the probe and not from most of the world, or the service degrading in a way that still answers a simple request. All three happen, which is why the page is worth reading and not worth trusting absolutely.
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.