Nexus Market Status
Live mirror, login, escrow & vendor dashboards
90-day uptime
99.92%
Active mirrors
3 / 3
Median latency
149 ms
Open incidents
none

Working Nexus Market URL · verified mirrors

90 days ago fewer outages → now

Internal services

Login service
p50 94 ms · p95 161 ms
Operational
Multisig escrow engine
p50 44 ms · p95 90 ms
Operational
Vendor dashboard
p50 63 ms · p95 132 ms
Operational
Dispute queue
p50 60 ms · p95 112 ms
Operational
In-market messaging
p50 81 ms · p95 174 ms
Operational

Recent incidents

Sep 16, 2026 · 02:09 UTC
In-market messaging — degraded latency
Resolved · 6m A backlog built up behind a slow dependency and cleared on its own.
Sep 15, 2026 · 05:09 UTC
Mirror C — degraded latency
Resolved · 5m Elevated latency under sustained arrival volume. The access queue held longer than usual, which is the intended behaviour rather than a fault.
Sep 12, 2026 · 20:23 UTC
Mirror A — degraded latency
Resolved · 26m One relay in the published path degraded and dragged the tail latency with it. Reachability was unaffected.
Sep 12, 2026 · 17:46 UTC
Mirror C — degraded latency
Resolved · 28m One relay in the published path degraded and dragged the tail latency with it. Reachability was unaffected.
Sep 12, 2026 · 16:16 UTC
Multisig escrow engine — unreachable
Resolved · 42m The worker pool for this component exited and was restarted. Requests during the window failed rather than hanging.
Sep 10, 2026 · 16:25 UTC
Mirror A — unreachable
Resolved · 32m Guard pool for this address lost two relays at once and circuits could not complete until replacements were selected.

What the components mean

Mirror A / B / C

Three independent v3 hidden services, each on its own guard pool. The probe rotates Tor circuits per request to measure user-realistic latency.

Login service

Authentication endpoint backed by per-session ephemeral keys. Health = the same probe completing a full handshake against a synthetic account.

Multisig engine

2-of-3 escrow contract orchestration: order lock, dispute branch, payout. Health = signer round-trip well under 200 ms.

Vendor dashboard

Shop management, listings, order queue. Status reflects success rate of synthetic vendor read/write cycles, not raw latency.

Dispute queue

Three-way dispute panel rota. Health = mean ticket pickup time below the published 6-hour SLA.

In-market messaging

End-to-end encrypted vendor ↔ buyer thread. Health = synthetic message round-trip under 1 s.

Public feeds for status updates

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.

Frequently asked

Is Nexus Market down right now?

No. As of 2026-09-24 04:00 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.

How fresh is the data on this page?

The probe runs every 60 seconds against fresh Tor circuits. Numbers above represent the most recent completed cycle.

Why is Mirror C in degraded mode?

Mirror C lives on slower guard nodes intended as fallback. Latency above 250 ms reflects circuit congestion, not a problem with the market itself.

Where do I get the working Nexus Market URL?

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.

Search topics covered on this status page

Down / outage queries

If you searched is nexus market down, nexus market down today, or nexus market not working, the live answer is the banner above. The probe runs every 60 seconds against fresh Tor circuits.

Online / live queries

For is nexus market online, nexus market live, or nexus market uptime, see the 90-day uptime bars and the per-mirror state table on the homepage.

Component & mirror state

For mirror status, mirror down, response time, or component health, the homepage panel breaks state down per-mirror and per-internal-service.

Anti-DDoS & layer-7 challenge

For checking your browser or ddos status, see the explainer landing covering the L7 challenge that fronts the backup mirrors during traffic peaks.

Working URL / current rotation

For working nexus market mirror, the verified rotation roster is the mirror table on the homepage; refresh on every visit since the platform rotates on a 24-hour cadence.

Sector & protocol queries

For darknet market status or tor onion status, the probe is platform-specific (Nexus only); Tor-network-side health is published at the Tor Project metrics portal.