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.
0x7F2A0A9D unchanged. No interruption to active sessions; legacy addresses 410 Gone after 96 hours per policy.
/login. Anti-DDoS challenge ("Checking your browser") elevated for 26 minutes. Browsers passing the challenge experienced a single-page extra hop, no credential or session issues.
Three independent v3 hidden services, each on its own guard pool. The probe rotates Tor circuits per request to measure user-realistic latency.
Authentication endpoint backed by per-session ephemeral keys. Health = the same probe completing a full handshake against a synthetic account.
2-of-3 escrow contract orchestration: order lock, dispute branch, payout. Health = signer round-trip well under 200 ms.
Shop management, listings, order queue. Status reflects success rate of synthetic vendor read/write cycles, not raw latency.
Three-way dispute panel rota. Health = mean ticket pickup time below the published 6-hour SLA.
End-to-end encrypted vendor ↔ buyer thread. Health = synthetic message round-trip under 1 s.
Status changes are mirrored to public RSS at /status.rss, Atom at /status.atom, and a JSON snapshot at /status.json. PGP-signed advisories accompany every state change. The feed endpoints are anonymous — no clearnet email or identifier is collected.
No. As of 2026-05-05 04:55 UTC all main services are operational. Mirror C is reporting degraded latency, which is normal during Tor guard rotation. Use Mirror A or Mirror B.
The probe runs every 60 seconds against fresh Tor circuits. Numbers above represent the most recent completed cycle.
Mirror C lives on slower guard nodes intended as fallback. Latency above 250 ms reflects circuit congestion, not a problem with the market itself.
From this page. The mirror addresses above are the live, signed v3 onions in 2026. Each is verified against PGP fingerprint 0x7F2A0A9D on every probe cycle.