Nexus
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.

← Full live status dashboard

90-day uptime
99.94%
Active mirrors
3 / 3
Median latency
141 ms
Open incidents
1 minor

Working Nexus Market URL · verified mirrors

Mirror A
http://nexusncagw2vnag3ycv62occuouhfgkp6htx7alhnzl5xwgtzi2mfbid.onion
p50 108 ms · p95 214 ms · signed 0x7F2A·0A9D
Operational
Mirror B
http://nexuspokkxp4ayqqec3c3lkekwhnjdqur5bqiocemx4t6sy3werqihad.onion
p50 141 ms · p95 267 ms · signed 0x7F2A·0A9D
Operational
Mirror C
http://nexusr4ivg23525pvw53h3av7b7xcamxqguprosazaoray33qgrar2qd.onion
p50 287 ms · p95 612 ms · signed 0x7F2A·0A9D
Degraded
90 days ago fewer outages → now

Internal services

Login service
p50 92 ms · p95 186 ms
Operational
Multisig escrow engine
p50 48 ms · p95 112 ms
Operational
Vendor dashboard
p50 76 ms · p95 178 ms
Operational
Dispute queue
p50 63 ms · p95 147 ms
Operational
In-market messaging
p50 88 ms · p95 196 ms
Operational

Recent incidents

May 5, 2026 · 02:27
Mirror C — degraded latency on Tor guard rotation
Investigating Median latency on Mirror C climbed past 250 ms after a guard rotation on the Tor side. Mirrors A and B are unaffected. Migrating users with active sessions are being routed to Mirror A by the load balancer's onion-pinning logic.
May 3, 2026 · 03:27
Vendor dashboard — PGP verification queue backed up
Resolved · 4h 12m A surge of vendor PGP key updates pushed the verification queue past its scheduled drain. Worker pool expanded; queue cleared at 07:39 UTC. No data loss, no missed signatures.
Apr 26, 2026 · 03:27
Mirror rotation — scheduled v3 onion swap
Completed · 0m downtime Routine rotation of all three production mirrors. Fingerprint 0x7F2A0A9D unchanged. No interruption to active sessions; legacy addresses 410 Gone after 96 hours per policy.
Apr 14, 2026 · 03:27
Layer-7 flood — Mirror A
Resolved · 26m Sustained POST flood targeting /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.
Mar 22, 2026 · 03:27
Multisig escrow — cold-storage signer rotation
Maintenance · 12m Scheduled rotation of cold-storage co-signing keys. Withdrawals queued during the window were drained within 12 minutes of completion. No funds affected.

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-05-05 03:13 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.