DarkMatter Status
This page tracks the observable operational state of the DarkMatter market: reachability of the primary DarkMatter onion URL, health of its backup mirrors, 90-day uptime, recent incidents, and the current phishing-clone watch. All checks are conducted from independent Tor-network probes; nothing on this page is an endorsement of the marketplace.
Snapshot
Endpoint reachability
Each endpoint below is the canonical PGP-signed DarkMatter URL for its role. Any onion address outside this table should be treated as a phishing clone until its signature is verified independently — addresses shown here match the signed block on the verified-access section of the homepage.
| Role | Address | State | Last check | Median RT |
|---|---|---|---|---|
| Primary | darkmatj7cjqruicuemre5svpnyfwjwgv5brvvv25hhwifagd4pkafyd.onion | Up | 14:22 UTC | 1.9s |
| Mirror 1 | darkmatgvwajlcq75r6dpighmbac77gd5nqgujxq3mrdavyl46pcf3id.onion | Up | 14:22 UTC | 2.3s |
| Mirror 2 | darkmatnx6wlttzvdkae5gdou4zy7nrcqbkh2ovhfezwz7ljj6gujgid.onion | Up | 14:22 UTC | 2.1s |
Response times are measured over Tor and vary considerably with circuit quality. Treat ±2s swings as normal. A sustained RT above 15s or consecutive timeouts trigger an incident entry below.
90-day uptime
One cell per day for the last 90 days on the primary DarkMatter onion URL. Green is a clean day; amber is a degraded day with elevated latency or partial outages; red is a day with extended unavailability. Grey cells predate our current monitoring window.
- Clean days
- 87 / 90
- Degraded days
- 2
- Outage days
- 1
- Mean latency
- 2.1s
Recent incidents
Entries below cover the last 90 days on the primary DarkMatter onion URL and its published mirrors. Incidents are logged when reachability or latency diverges meaningfully from baseline; cosmetic UI changes are not logged.
-
Intermittent timeouts on primary
Primary onion returned elevated timeouts between roughly 11:00–14:00 UTC. Mirrors remained fully reachable throughout. Consistent with introductory-point churn on the Tor side rather than a platform-level issue. Resolved without operator comment.
-
Extended unavailability on primary address
Primary onion unreachable for approximately nine hours spanning the UTC evening. Both mirrors remained up, and a signed mirror announcement was posted on two external reference lists within the first hour. Platform behaviour on recovery was consistent with a descriptor-publication issue; no loss of session state reported.
-
Elevated latency across all endpoints
Median response times climbed to roughly 8s on the primary and both mirrors simultaneously. Behaviour is more consistent with a Tor-network event than a platform fault. Latency returned to baseline without intervention.
-
Status page monitoring window opens
Independent reachability probes for the canonical DarkMatter URL and its two published mirrors began on this date. Earlier data shown on this page is reconstructed from public signed mirror announcements and is not probe-derived.
Phishing-clone watch
A non-exhaustive list of addresses that impersonate the DarkMatter market and have been observed in circulation recently. These are not the real market. They are posted here so readers who encounter them elsewhere can compare them against the canonical DarkMatter link and discard them.
| Clone address (do not use) | First seen | Channel |
|---|---|---|
| darkmatej7cjqruicuemre5svpnyfwjwgv5brvvv25hhwifagd4pkafyd.onion | 2026-03-28 | Paste-site post |
| darkmatj78qruicuemre5svpnyfwjwgv5brvvv25hhwifagd4pkafyd.onion | 2026-04-06 | Search-result bid |
| darkmatj7cjqruicuemre5svpnyfwjwgv5brvvv25hhwifagd4pkafyq.onion | 2026-04-14 | Forum DM |
Substitutions are highlighted in red. The canonical DarkMatter onion URL is the one signed by the operator's key in the verified-access section. If an address you are about to use is not that exact string, it is a clone.
How this page is produced
Reachability probes are HTTP HEAD requests issued over Tor to each published onion address at a fixed cadence, from multiple circuits. A response within a defined latency envelope counts as reachable; a timeout or connection failure counts as a miss. Three consecutive misses within a scheduled interval elevate an endpoint to the degraded state; sustained unreachability elevates it to the outage state.
Nothing on this page is an interaction with the marketplace beyond the HEAD probe itself — we do not log in, place orders, or transit the platform's checkout flow. The data shown is limited to what a passive observer on the Tor network can see.
For the subject-matter overview, see the homepage overview. For the editorial approach behind this site, see the about page.