Aliased landing for the status query population, identical content scope to the homepage but streamlined to a single answer.
Live status: operational. The full per-component panel — mirrors, login service, multisig escrow engine, vendor dashboard, dispute queue, in-market messaging — is on the homepage. The 90-day uptime view sits underneath it. The incident log is below that.
This page exists because “nexus market status” arrives as a search query distinct from “is nexus market down,” and the editorial preference is to serve each query population on its own URL with the answer tailored to the phrasing. Bookmark whichever URL you ended up on; both rotate through the same probe data.
Reachability and response time per mirror, plus the internal services that sit behind them: login, escrow, the vendor dashboard, the dispute queue and messaging. A mirror can be reachable while a service behind it is slow, which is why they are listed separately rather than rolled into one number.
The median figure describes a typical request and the higher percentile describes the slow tail. A mirror with a good median and a bad tail feels fine until it suddenly does not, which is the pattern most people notice as the site randomly hanging.
Tor relays go offline, get restarted and drop connections under load constantly. A state flipping for a few minutes and returning is the network behaving normally, not an event. Only sustained changes across mirrors are worth calling an incident.
Whether the operator is trustworthy, whether escrow is being honoured, or whether the service will exist next month. Uptime is a statement about reachability and nothing else, and reading it as a trust signal is the most common mistake made with a page like this.
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.