Per-service status
Nexus Onion Status 2026: Is Nexus Market Reachable Right Now?
Oniongate follows whether the nexus darknet market answers on Tor and how fast it does so. Every word on it is produced by a probe, never set by hand. For clarity, this is the onion marketplace named nexus, not the trusted-traveller programme, the game-mod host, or any other clearnet service that happens to share the word. Oniongate tracks this nexus onion market the same way it tracks every other listed service, on one shared, honest probe loop.
How to read nexus's status numbers
Why Oniongate tracks Nexus instead of just linking to it
Oniongate exists because a link alone tells a visitor nothing about whether Nexus actually answers right now. Every Nexus mirror on oniongate is probed on the same recurring loop as the other six markets Oniongate follows, scored independently, and shown with an honest Unknown state rather than a guess. Oniongate does not operate Nexus and cannot vouch for anything past the network layer — only whether the listed Nexus addresses responded to the last probe.
What the 24h, 7d and 30d uptime windows mean
Each uptime card is a rolling percentage of successful probes over that window, recalculated every cycle rather than fixed to a calendar day. The 24h figure reacts fastest and swings the most on a single bad stretch; the 30d figure smooths past a short outage and reflects the longer pattern. Read the 24h card for "is anything wrong right now" and the 30d card for "how reliable has nexus actually been."
Reading nexus's per-mirror breakdown
nexus has 3 endpoints on file in the signed directory below, each probed and scored independently rather than rolled into one shared number. A single mirror reading Down while the others read Online usually points at that specific mirror, not at nexus as a whole — check whether the pattern is isolated to one address or shared across all of them before drawing a conclusion.
What to do if nexus reads unknown
Unknown means the probe loop has no fresh result to report for nexus, not that anything is wrong. It shows up right after this status page is first added to oniongate, and it shows up if the probe feed itself goes offline — in both cases every service on oniongate reads unknown together, not just this one. Wait for the next cycle and refresh rather than treating an unknown reading as a sign the market itself is in trouble.
Probe timeline
last 30 checksEach cell is one probe, newest on the right. The strip fills as the loop runs; with no feed attached yet, every check reads unknown rather than a colour oniongate cannot stand behind.
Nexus onion market: mirror & incident log
This section is oniongate's place for anything about nexus's mirror set worth recording separately from the live banner, rather than a paragraph identical to what every other tracked market's page carries.
Incident log
No incidents are logged for nexus in the current window. With three endpoints on file, oniongate's bar for an entry here is a pattern spanning at least two of nexus's three addresses across several cycles, not a single mirror having one rough stretch — a three-mirror spread means an isolated miss is far more often routing noise on oniongate's own vantage point than a real nexus-side problem.
Mirror history
Nexus currently sits in the middle tier of oniongate's roster with three monitored onion endpoints, more resilient to a single dead address than a one-mirror market but narrower than torzon or mars's five-endpoint spread. Verifying which of the three is actually reachable before connecting, rather than trusting whichever address you saved earliest, is worth the extra step — general operational-security habits beyond what this reachability log covers are collected by EFF's Surveillance Self-Defense guide. oniongate will log a nexus mirror-count change here the same way it does for every other tracked market, whenever the signed directory itself adds or drops a nexus address, so this section is worth a second look after any nexus mirror rotation.
Mirrors — monitored endpoints
3 endpoints on filenexusakrv5pwd5jtzkycsmp3sllliq6nxilutfug2o3rlmdxmqlzz2ad.onionnexusbomklgyvipzr5p4nfluezdsjntzksni4wsqf63kpv2ge4bqnhyd.onionnexusc26ms5xcsd4h7lhvqnbsclc6uxkk5nywh4lh7e56ylokqdg6eid.onionThese addresses come from the signed 2-of-3 directory. oniongate measures the nexus mirrors, it does not create them. Any nexus address outside that signed list is not one oniongate monitor.
Honest answers
Is nexus reachable right now?
The banner has the answer. Down means the latest probe could not complete a request to any listed nexus endpoint; unknown means no fresh check exists to summarise. The reading reflects oniongate's probe over Tor, not an opinion about the marketplace, and it ages into unknown rather than freezing if the feed goes quiet.
Which nexus mirror should I use?
Any of the signed ones above, verified by you. nexus publishes more than one onion, and the safest habit is to copy the full address, read every character, and confirm it against a second independent source. Oniongate never abbreviate the string, so you always have the whole thing to check.
Do all three mirrors go down together?
Not necessarily. Each nexus endpoint is probed separately and shows its own dot, so one can be unreachable while another answers. That is by design: it stops a single failed mirror from painting the whole service red, and stops one lucky mirror from hiding a broader problem.
How often is nexus checked?
On a short loop, roughly every few seconds per endpoint, over Tor. When the feed is live, each row records how long ago it last completed a check, so you can weigh a reading by its freshness. A row that says unknown has simply not reported yet.
Does Oniongate probe Nexus more than once a day?
Yes, on a recurring loop rather than a single daily check. Nexus's mirrors are probed repeatedly through the day so a row here reflects a recent measurement, not a stale one from hours earlier. The exact interval varies with probing load across all seven tracked markets.
If Nexus shows Unknown across every mirror, does that mean it is seized?
No — treat an all-Unknown reading as a monitoring gap, not a seizure claim. It usually means the probing loop for Nexus has not reported recently, whether from a restart, a Tor circuit issue on oniongate's end, or a temporary gap in the feed. A seizure is a specific claim oniongate does not make without a signed statement to back it.
What this oniongate nexus status page cannot tell you
A reachability reading is a narrow, specific claim. Here is what it does and does not cover, so a green dot next to nexus is not mistaken for more than it actually says.
Reachability is not the same as legitimacy
A probe reaching nexus's onion address confirms the service answered a network request within the timeout window. It says nothing about escrow practices, vendor vetting, or whether a specific listing inside nexus is genuine — those questions belong on nexus's own reference and verification pages, not on a reachability board. Treat oniongate as one input among several, not a verdict on whether nexus itself is trustworthy.
Why one mirror's reading is not the whole picture
nexus may publish more than one onion endpoint, and each one is probed independently. A single dead mirror does not mean nexus itself is down if other mirrors on file are still answering — check the full mirror table below rather than reading one row as the complete state of the service. Conversely, one live mirror during a wider outage is not proof everything is fine; it only means that one specific address is currently reachable.
How to use oniongate alongside nexus's own verification steps
Before trusting any nexus address copied from oniongate or anywhere else, verify it against nexus's own signed record — a PGP fingerprint match, not a status dot, is what actually establishes that an address is genuine. This status page exists to answer "is it reachable right now," a question nexus's own reference site is not built to answer continuously; the two pages do different jobs and neither replaces the other.
Reading nexus's mirror count on oniongate
nexus is tracked here with three separate onion endpoints, a mid-sized footprint compared to the seven markets OnionGate monitors — more redundancy than a single-mirror service, less than the largest mirror sets on oniongate.
What three mirrors typically buys a visitor
A three-endpoint spread gives nexus room to lose one mirror to maintenance or a routing problem without the whole service reading Down, while still keeping the number of addresses a visitor has to verify manageable. Check the mirror table below for nexus's current per-endpoint readings rather than relying on a single row.
What this reading does not cover
Nothing here evaluates nexus's vendor base, dispute process, or trustworthiness — only whether its tracked addresses answered a recent probe. Verify any nexus address against its own signed record before treating a reachable reading as more than that.
A worked example: reading nexus’s three-mirror spread
What three monitored onion addresses buys you over one
nexus is tracked across three separate onion endpoints, which sits between the single-address markets and the five-mirror ones on oniongate. Three is enough that one address going Down does not automatically read as a nexus-wide outage, but few enough that a visitor can reasonably check all three readings in a single glance rather than scanning a longer mirror table.
Why oniongate do not pick a “primary” among nexus’s three addresses
Oniongate deliberately does not label any one of nexus's three onion addresses as the main one and the other two as backups — that framing belongs to nexus's own operators, not to a measurement board. What oniongate shows is which of the three currently answers, in the order they were added to the signed directory, and it is up to the visitor which verified address to actually use.
How often to recheck a nexus reading before connecting
A status reading ages the moment it is produced, and for a market like nexus that is tracked across three onion addresses, the safest habit is reloading oniongate immediately before you connect rather than relying on a tab left open from earlier in a session. The last-checked timestamp on oniongate exists specifically so that habit is verifiable — a stale-looking timestamp is a reason to wait for the next cycle, not to trust an old reading.
Nexus as a darknet market: what oniongate's status actually verifies
Nexus is one of seven darknet markets oniongate probes on the same Tor loop, and the status word on this page describes exactly one thing: whether Nexus's onion address answered a Tor request within the timeout window on the most recent probe cycle. Nothing about Nexus's inventory, its vendor base, or any uptime claim Nexus makes on its own front page factors into this reading — oniongate did not consult Nexus's marketing, it consulted a stopwatch and a Tor circuit.
Why "darknet market status" means something narrow here
A lot of pages use the phrase "darknet market status" to mean a vague blend of reputation, activity level, and uptime folded into one score. oniongate's Nexus status page does not do that. Reachability over Tor is the only signal this page reports, and every other question about Nexus — whether it is a good market to use, whether its escrow is sound, whether its vendor base is currently active — belongs to Nexus's own reference material, not to this status reading.
How often Nexus's Tor status actually changes
Most probe cycles produce no change at all: Nexus's onion address answers the way it answered last cycle, and the status word simply repeats. A change only gets logged on this darknet market's page when Nexus's status genuinely flips between Online, Checking, Down and Unknown — oniongate does not manufacture drama by treating an unchanged Tor reading as new information about the market.