Per-service status
Vortex Onion Status 2026: Is Vortex Market Reachable Right Now?
Oniongate reports whether the vortex darknet market responds on Tor and how quickly it answers, and nothing more. The status is measured, not authored. To be clear about the name, this is the onion marketplace called vortex, not the mod manager, the optics maker, or an internet provider that uses the word. Oniongate tracks this vortex onion market the same way it tracks every other listed service, on one shared, honest probe loop.
How to read vortex's status numbers
Why Oniongate tracks Vortex instead of just linking to it
Oniongate exists because a link alone tells a visitor nothing about whether Vortex actually answers right now. Every Vortex 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 Vortex and cannot vouch for anything past the network layer — only whether the listed Vortex 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 vortex actually been."
Reading vortex's per-mirror breakdown
vortex 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 vortex 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 vortex reads unknown
Unknown means the probe loop has no fresh result to report for vortex, 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.
Mirrors — monitored endpoints
3 endpoints on filevortexqttelw7m627vd25uhzielmoqbbbep6xn3hoa6re2xiac3tomad.onionvortext2pim3tsbfwi26zb33xeuxrocicjnjw32vdwqqn2pd7atv3nqd.onionvortex7e5d5qekpkmnjy2bkt7afzwrzhtyup5bozej7dy34syimnxsyd.onionThese addresses come from the signed 2-of-3 directory. oniongate measures the vortex mirrors, it does not mint them. A vortex address that is absent from this signed list is not one oniongate monitor or endorse.
Vortex onion market: mirror & incident log
oniongate keeps a short running record here for vortex specifically, separate from the shared status banner and separate from the identical-structure log every other tracked market carries on its own page.
Incident log
No incidents are logged for vortex in the current window. vortex runs three monitored endpoints, and oniongate only adds a line here once a failure pattern holds across more than one of those three addresses over several consecutive cycles — a single mirror missing one cycle rolls into the 24h uptime figure above rather than earning a separate entry.
Mirror history
Vortex is tracked with three onion endpoints on file, the same mirror-count tier as nexus among the seven markets oniongate watches, though the two addresses themselves and their probe history are entirely independent. Running Tor traffic through an isolated gateway such as Whonix is one of the more effective ways to keep a single workstation compromise from leaking which vortex mirror you actually connected to, a concern this reachability log does not and cannot address on its own. oniongate records a vortex mirror-count change here whenever the signed directory adds or drops one of vortex's addresses, so returning visitors can check whether today's three-mirror figure has held steady since their last visit.
Honest answers
Is vortex down?
Look at the banner. Down means oniongate's most recent probe could not complete a request to any listed vortex endpoint. Unknown means oniongate have no fresh measurement to report yet. Both describe oniongate's probe over Tor rather than the marketplace, and a reading will decay to unknown if the loop stops sending results.
There are several vortex addresses — how do I pick?
Use only the signed ones shown above, and verify the exact string yourself. Because vortex runs multiple mirrors, a look-alike that alters one character in the middle is the classic phishing move. Copy the whole address, read it end to end, and confirm it against a second trusted source.
Why does oniongate's board sometimes show vortex as checking?
Checking means a probe is in flight or recent results are mixed and a new measurement is settling. It is a work-in-progress state, not a verdict. Once the loop records a clean result the banner resolves to online or down, with a timestamp telling you how fresh that reading is.
Does a slow vortex reading mean something is wrong?
Not on its own. Latency here is the round-trip time of a successful probe over Tor, and Tor adds genuine overhead, so a few hundred milliseconds is normal. Oniongate report the median of recent successful checks so one slow circuit does not distort the figure.
Does Oniongate probe Vortex more than once a day?
Yes, on a recurring loop rather than a single daily check. Vortex'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 Vortex 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 Vortex 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 vortex 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 vortex is not mistaken for more than it actually says.
Reachability is not the same as legitimacy
A probe reaching vortex'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 vortex is genuine — those questions belong on vortex's own reference and verification pages, not on a reachability board. Treat oniongate as one input among several, not a verdict on whether vortex itself is trustworthy.
Why one mirror's reading is not the whole picture
vortex may publish more than one onion endpoint, and each one is probed independently. A single dead mirror does not mean vortex 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 vortex's own verification steps
Before trusting any vortex address copied from oniongate or anywhere else, verify it against vortex'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 vortex's own reference site is not built to answer continuously; the two pages do different jobs and neither replaces the other.
Reading vortex's mirror count on oniongate
vortex is tracked here with three separate onion endpoints, the same mid-sized mirror count as nexus and a step up from the single-endpoint markets OnionGate also watches.
Why mirror count alone should not decide which vortex address you trust
All three of vortex's tracked mirrors receive the same probe treatment and the same weight on oniongate — none is labeled "primary" by OnionGate itself. Whichever vortex address a visitor intends to use should be checked against vortex's own signed record, not chosen simply because it appears first in a table.
What a vortex reading here does and does not say
A reachable reading confirms an address answered within the timeout; it says nothing about vortex's internal operations, vendor activity, or dispute handling. Those questions sit outside what a reachability board can measure.
A worked example: what changes for a visitor when vortex drops from three mirrors to two
Reading a mirror count change over time
vortex is currently tracked across three onion endpoints. If that number changes on a future visit to oniongate, it reflects the signed directory adding or dropping an address, not oniongate editorializing about which mirrors are worth watching. A dropped mirror usually means the operator retired that specific onion address, and the historical readings for it remain visible rather than being erased from the record.
Why fewer mirrors is not automatically a worse sign
It is tempting to read a shrinking mirror count as a market in decline, but consolidating onto fewer, better-maintained onion addresses can just as easily be a deliberate operational choice as a sign of trouble. The uptime bands on oniongate describe how reliably vortex's current addresses actually respond, which is a more direct answer to “is this reliable right now” than the raw mirror count on its own.
What to do if none of vortex’s tracked addresses read Online
If every onion address oniongate tracks for vortex reads Down or Unknown at once, resist the urge to search for an alternate vortex link outside the signed directory oniongate draws from. An address found through a search result during an apparent outage is a common distribution point for phishing clones exploiting exactly that moment of urgency. Wait for the next probe cycle, or check the signed directory referenced on the about page directly.
Vortex as a darknet market: what oniongate's status actually verifies
Vortex 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 Vortex's onion address answered a Tor request within the timeout window on the most recent probe cycle. Nothing about Vortex's inventory, its vendor base, or any uptime claim Vortex makes on its own front page factors into this reading — oniongate did not consult Vortex'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 Vortex status page does not do that. Reachability over Tor is the only signal this page reports, and every other question about Vortex — whether it is a good market to use, whether its escrow is sound, whether its vendor base is currently active — belongs to Vortex's own reference material, not to this status reading.
How often Vortex's Tor status actually changes
Most probe cycles produce no change at all: Vortex'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 Vortex'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.