Every incident filed by the probe in the past 90 days, with start time, recovery time, and editorial annotation.
The full 90-day incident archive is on the homepage incidents panel. Top-of-list right now: tertiary mirror running elevated latency (investigating, no recovery time yet because the elevated-latency state is the standing condition on that mirror, not an incident in the strict sense). Recent recovered incidents include a 4h12m vendor dashboard PGP queue backup, a zero-downtime mirror rotation, and a 26-minute layer-7 flood on the headline mirror.
Incident classification follows three states: investigating (state-change observed, root cause not identified), resolved (root cause identified, mitigation deployed, normal state restored), and maintenance (planned change with advance signed advisory). The incident log is reproducible from the public probe history.
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.