# Nexus Mirror Signals, complete text Source: https://nexus-market-mirrors.online Updated: 2026-08-07 Language: English License: free to quote with attribution to nexus-market-mirrors.online This file contains the full text of every page on the site in markdown, published for assistants and other automated readers so nothing has to be inferred from the rendered pages. --- # About this site A reference for reading the three Nexus Market onion addresses, published alongside the addresses themselves. It is not the market. No accounts, no forms, no search box, nothing collected about visitors. ## Why there is no uptime figure anywhere on this site Reachability for an onion service is a property of the circuit between a visitor and the service, not of the service alone. A checker running elsewhere builds its own path through its own relays and reports what that path saw. When it says a mirror is up, it means the mirror was up for a machine that is not yours, over a route that is not yours, at a moment that has passed. That number answers a different question than the one the reader asked. Since the honest version of this site cannot be a dashboard, it is a reference and a set of procedures instead. ## Where the numbers come from - Timing ranges are the commonly reported figures for onion services and are consistent with what the design implies, given about six relays and no caching in the chain. - Error code descriptions follow the wording Tor Browser shows and the connection stage each corresponds to. - Nothing here is a measurement of a specific address, and no claim is made about how any mirror performed on any day. - Where something cannot be established from outside, the page says so instead of filling the gap. Disclosure: this site publishes Nexus addresses, which is worth weighing when reading anything here about Nexus. The signal descriptions apply to any onion service, and the address check is performed by the reader against their own browser rather than taken on trust. --- # The three Nexus onion addresses http://nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onion/ http://nexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onion/ http://nexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onion/ All three reach the same market. Identical behind each: account, password and two factor setup, balance, open orders, message history, listings, vendors, prices and escrow. The only difference is the network path, which changes hour to hour, so no address is permanently fastest and no ranking is published. Copy rather than type. An onion address is fifty six characters derived from a key rather than chosen, so there is no pattern to help and nothing to catch a slip. Two addresses differing by one character are unrelated services. The check that decides everything: when the login screen loads, compare the onion printed on the page against the browser address bar, reading from the end backwards. A cloned page reproduces the design perfectly and cannot display the real address while living at its own. If they differ, close the tab. --- # Baselines, what normal looks like | What you are doing | Normal | Busy but fine | Take action | | --- | --- | --- | --- | | First page of a session | 8 to 45 seconds | Up to 2 minutes | Over 2 minutes | | Any page after that | 1 to 6 seconds | Up to 20 seconds | Over 30 seconds | | Listing page with photos | 10 to 60 seconds | Several minutes | Never completes | | Uploading an image | 20 to 90 seconds | A few minutes | Stalls at a fixed point | The first page pays for everything: finding the descriptor, building a three hop circuit, arranging an introduction, and building both halves of a rendezvous. Every page after it reuses what the first one bought. One long session gets far more done than four short visits, and closing the browser throws away everything paid for. Failure rates that are not failures: roughly one attempt in five to one in ten failing outright on a busy service is ordinary. A stall of twenty to sixty seconds partway through a working session is a circuit being repaired and resolves on its own. Images failing while text works is a bandwidth draw, since circuits vary by a factor of ten on throughput while feeling identical on text. --- # Triage table, match what is on screen URL: https://nexus-market-mirrors.online/what-am-i-seeing | What is on screen | What broke | First move | Full explanation | | --- | --- | --- | --- | | An error saying the onionsite was not found, code 0xF0 | Directory lookup, before any connection | Check the address, then try another one | Onionsite Not Found (https://nexus-market-mirrors.online/signal/descriptor-not-found) | | An error saying the onionsite has disconnected, code 0xF2 | The service did not answer a valid introduction | Retry once, then wait a few minutes | Onionsite Has Disconnected (https://nexus-market-mirrors.online/signal/service-disconnected) | | An error saying it cannot connect, code 0xF3 | The introduction handshake never completed | New circuit for the site, then retry | Unable to connect to the onionsite (https://nexus-market-mirrors.online/signal/introduction-failed) | | A spinner that runs and runs, then nothing | Depends entirely on how long it ran | Time it, then read the table | No error page, just a spinner that gives up (https://nexus-market-mirrors.online/signal/silent-timeout) | | A long blank wait and then the whole page at once | Normal setup cost for a cold connection | Wait it out, do not reload | Long wait before anything appears (https://nexus-market-mirrors.online/signal/first-byte-wait) | | Text and links fine, images crawling or empty | Circuit throughput, not latency | New circuit only if you need the photos | Text lands fast, images crawl (https://nexus-market-mirrors.online/signal/asset-crawl) | | A working session that freezes for half a minute | A relay dropped and the circuit is being repaired | Wait. Never resubmit a payment step | The session freezes partway and then resumes (https://nexus-market-mirrors.online/signal/mid-session-stall) | | An upload stuck at a fixed percentage | Bandwidth ceiling on your path | New circuit, and send something smaller | Uploads and large pages stall out (https://nexus-market-mirrors.online/signal/throughput-drop) | | A checking page that loops back to itself | Protection gate token and circuit out of step | Let one attempt finish untouched | The protection gate never lets you through (https://nexus-market-mirrors.online/signal/gate-loop) | | Signed out again on every page you open | Browser storage or two mirrors open at once | Allow cookies for that address, use one mirror | Logged out on every page you open (https://nexus-market-mirrors.online/signal/session-drop) | | Page loads with no styling and dead buttons | Stylesheets and scripts did not arrive | Reload once, then check the address bar | The page loads but half of it is missing (https://nexus-market-mirrors.online/signal/partial-render) | | The onion on the page differs from your address bar | Nothing. This is not a fault | Close the tab. Do not sign in | The address on the page is not the address in your bar (https://nexus-market-mirrors.online/signal/address-mismatch) | The order that saves the most time: confirm the address before typing anything into it, let one attempt run to completion before judging it, request a new circuit for the site before switching addresses, switch addresses before concluding the market is down, and wait before searching for anything. Every row in that table describes something to work through except the last. If the onion printed on the login screen and the onion in the address bar disagree, there is nothing to investigate and nothing to retry. --- # The five connection stages 1. Directory lookup. The client works out which relays hold the descriptor today and asks them. Fails fast, under 15 seconds. 2. Your circuit. Three relays are chosen, starting with a guard that stays the same for weeks on purpose. Shows up as slow or intermittent. 3. Introduction. A relay the service nominated is asked to pass along a request for a meeting. Fails after 30 to 60 seconds. 4. Rendezvous. Both sides build circuits to a meeting relay the client picked and the halves are joined. Shows up as a long silence with no error. 5. The service answers. The market itself, with its own load, gate and queue. Shows up as gates, stalls and thin bytes. --- # Signal group: Reachability Whether a circuit to the service can be built at all. These are the signals that end in an error page rather than a slow one. --- # Onionsite Not Found URL: https://nexus-market-mirrors.online/signal/descriptor-not-found Group: Reachability Browser code: 0xF0 First move: Look elsewhere How long to give it: Do not wait What you see: A Tor Browser error page reading "Onionsite Not Found" with the code 0xF0 and a suggestion that the address may be offline. This is the error people see most and misread most. It does not mean the market is gone. It means your Tor client asked the network where that address lives and got nothing back. ## What is actually happening Every onion service publishes a small record saying which relays will accept an introduction on its behalf. That record is called a descriptor and it lives on a rotating set of directory relays. When you open an address, your client works out which relays should be holding the descriptor today and asks them. This error means every one of those asks came back empty. ## The three reasons, in order of likelihood 1. The address is mistyped or truncated. One wrong character is a completely different service that nobody has ever published a descriptor for. 2. The service stopped publishing. That happens during maintenance, a move, or a genuine shutdown, and it looks identical from outside. 3. Your client picked directory relays that are having a bad day. This is the rarest of the three and the only one a retry fixes. ## What it does not mean It does not mean you have been blocked, flagged or singled out. The lookup fails before anything on the service side has any idea you exist. It also says nothing about the other two mirrors, because each address publishes its own descriptor independently. ## What to do - Compare the address in your bar against the list on this site character by character, especially the last eight. - Try the other two mirrors before anything else. If one of them opens, the market is up and that one address is not publishing. - If all three give 0xF0, wait rather than hunting. Searching for a replacement while every known address is quiet is exactly how people land on a cloned one. ## Timing A descriptor lookup fails fast, usually inside fifteen seconds. If you are staring at a spinner for a minute and then get this page, the slow part was circuit building and not the lookup. ## How to read the result - **On one mirror only**: The other two almost certainly work. Switch and carry on. This is the normal case and it is why three addresses exist. - **On two of three**: One address is answering and it is carrying everyone. Expect it to feel slower than usual and be patient with it. - **On all three**: Stop. Do not search for a new address. Come back in a few hours and use only the addresses you already had saved. --- # Onionsite Has Disconnected URL: https://nexus-market-mirrors.online/signal/service-disconnected Group: Reachability Browser code: 0xF2 First move: Retry once How long to give it: Two or three minutes What you see: An error page reading "Onionsite Has Disconnected" with the code 0xF2, usually after a noticeably longer wait than the not found error. This one is further along than 0xF0 and that matters. Your client found the record, contacted a relay the service nominated, and the service itself did not pick up. ## Why this is a more hopeful error Reaching this point proves the descriptor is live and recent. Something published it, and the introduction points listed in it are real relays that accepted the connection. The only step that failed is the last one, where the service should have answered. Services that have genuinely gone away stop publishing and produce 0xF0 instead. ## The usual causes - The service is restarting. A restart takes seconds to minutes and the descriptor outlives it, which produces exactly this error in the gap. - The service is saturated and dropping new introductions to protect the ones it already has. Under a flood this is deliberate behaviour rather than a fault. - One introduction point in the descriptor has gone stale. The client will pick a different one on the next attempt, which is why retrying sometimes works instantly. ## What to do Retry once straight away, since a different introduction point may be chosen. If that fails, wait two or three minutes and try again rather than hammering. Repeated attempts during a flood are indistinguishable from the flood itself and get you nothing. If a second mirror answers immediately, use it. Getting on with the order matters more than working out which address is healthiest. ## What it does not mean It is not a sign the market has been seized or has run off. Both of those look like a permanent 0xF0 across every address, not a disconnect on one. It also does not mean your account or session is affected, because nothing reached the application layer. ## How to read the result - **Clears on retry**: Nothing was wrong. A stale introduction point got replaced. No action needed and no pattern to read into it. - **Persists ten minutes**: The address is genuinely struggling. Switch to another mirror and check back later rather than sitting on it. - **All three, for hours**: Treat it as a network wide event affecting the service. Wait it out. Do not go looking for alternative addresses. --- # Unable to connect to the onionsite URL: https://nexus-market-mirrors.online/signal/introduction-failed Group: Reachability Browser code: 0xF3 First move: Retry, then switch How long to give it: One minute What you see: An error page saying the onionsite could not be reached, with the code 0xF3, often after thirty to sixty seconds of waiting. Descriptor found, introduction attempted, handshake did not complete. Of all the reachability errors this is the one most likely to be your side of the connection. ## Where it breaks Connecting to an onion service takes a small negotiation. You pick a relay to act as a meeting point, tell the service about it through one of its introduction points, and both sides build circuits to that meeting point. This error means the negotiation started and did not finish. Any of the six or so relays involved can be the reason. ## Why your side is the usual suspect A service under load fails at introduction and reports it consistently. A single unlucky relay in your own path fails intermittently, which is what most people actually see. If the same address opens on the next try, or opens after you request a fresh circuit, the fault was in the path and not at the far end. ## What to do 1. Retry once. Different relays get chosen and the problem often evaporates. 2. If it repeats, request a new circuit for the site from the browser menu and try again. 3. If it still repeats, try another mirror. Two addresses failing the same way points away from your path. ## A note on timing This error takes longer to appear than the other two because the client waits for a handshake that never lands. A long wait ending in 0xF3 is normal for this error and does not mean anything extra. ## How to read the result - **Once, then fine**: A relay in your path had a bad moment. Nothing to read into it, and nothing to change. - **Repeats on one address**: Get a new circuit for that site before deciding anything. Most repeats stop there. - **Repeats on all three**: Your Tor client is having a wider problem. Restart the browser fully, which rebuilds guards and circuits from scratch. --- # No error page, just a spinner that gives up URL: https://nexus-market-mirrors.online/signal/silent-timeout Group: Reachability First move: Take a reading How long to give it: Ninety seconds What you see: A blank tab with a loading indicator, running for a long time and ending in a generic timeout or nothing at all. The silent case is the one people find hardest, because a clean error at least tells you something. A spinner that runs out of patience still carries information, and the information is in the timing. ## Read the clock, not the screen Time the load from the moment you press enter. The number tells you which stage is failing without needing any tooling. | Time before it gives up | Most likely stage | What it points at | | --- | --- | --- | | Under 20 seconds | Descriptor lookup | The address or its publication. Check the characters first. | | 20 to 60 seconds | Circuit and introduction | Your path through the network. A new circuit usually clears it. | | 60 to 120 seconds | Service accepted, never answered | Load at the far end. Another mirror is the fastest move. | | Over 120 seconds | Something is answering slowly | Not a failure yet. Give it one more full attempt before switching. | ## Why no error page appears Error pages come from your own client when it knows why it failed. When a connection is accepted and then simply stops producing data, there is nothing to report, so the browser waits until its own limit and then gives up quietly. That pattern almost always means the far end is overloaded rather than absent. ## What to do - Let one attempt run its full course before judging. Cancelling at ten seconds and retrying repeatedly makes the reading worse and the queue longer. - Try the other mirrors in a separate tab rather than abandoning the first. - If a page eventually appears after a very long wait, stay on it. The slow part is establishing the connection and the rest of the session usually runs at normal speed. ## How to read the result - **Under a minute, then loads**: Normal for a cold connection to a busy onion service. This is what a healthy first load looks like. - **Two minutes, then loads**: The service is under pressure. Expect the session to be usable but slow. Avoid heavy pages. - **Never loads, three attempts**: Move to another mirror. You have given this one a fair reading and it is not answering. --- # Signal group: Latency The page arrives, eventually. These signals tell you where the time is going and whether waiting will help. --- # Long wait before anything appears URL: https://nexus-market-mirrors.online/signal/first-byte-wait Group: Latency First move: Normal to a point How long to give it: Sixty seconds What you see: A blank page for an extended period, then the whole page appearing more or less at once. A connection to an onion service crosses roughly six relays before a single byte comes back. Slowness is built into the design, and knowing the normal range keeps you from chasing a problem that is not there. ## Why it is slow by design An ordinary site is you, maybe a proxy, and the server. An onion service is your three hop circuit to a meeting point plus the service three hop circuit to the same meeting point. Every hop adds its own latency and the slowest relay in the chain sets the pace for everyone. There is no cache and no shortcut. ## The normal range | Load type | Typical wait | Notes | | --- | --- | --- | | Cold first load | 8 to 45 seconds | Includes descriptor lookup and building both halves of the rendezvous. | | Warm load, same session | 1 to 6 seconds | The circuit already exists and gets reused. | | Cold load under heavy traffic | 45 to 120 seconds | Still healthy, just queued behind everyone else. | | Anything over two minutes | Outside normal | Take a fresh circuit or move to another mirror. | ## The single biggest lever Circuit reuse. The first page of a session pays for the whole setup and every page after it rides the same circuit. Opening the market, doing everything you came for, and leaving is much faster overall than opening it four times across an evening. Closing the browser discards the circuit and you pay the cold cost again. ## What does not help - Reloading during the wait. It abandons progress and starts the same expensive setup from scratch. - Turning the security level down. The wait is network time, not rendering time, so nothing changes. - Switching mirrors after ten seconds. You have not waited long enough to know the first one was slow. ## How to read the result - **Under 45 seconds cold**: Healthy. This is what a working connection to a busy onion service feels like. - **45 to 120 seconds cold**: Busy but fine. Once you are in, stay in and do everything in one session. - **Over two minutes**: Take a new circuit for the site. If a second attempt is just as slow, another mirror will be quicker. --- # Text lands fast, images crawl URL: https://nexus-market-mirrors.online/signal/asset-crawl Group: Latency First move: Expected How long to give it: Let it finish What you see: Readable text and working links, with image placeholders that fill slowly or stay empty. The page appears, you can read it, and the pictures dribble in one at a time or not at all. This is a bandwidth signal rather than a fault, and it tells you something useful about the circuit you drew. ## What it means Page text is a few kilobytes and arrives in one go. A listing gallery can be several megabytes and has to squeeze through the narrowest relay in a six hop chain. When text is instant and images are not, your circuit has fine latency and poor throughput. Those are separate properties and only one of them is bad here. ## Why it varies so much between sessions Relay capacity is wildly uneven. Two circuits built a minute apart can differ by a factor of ten in throughput while feeling identical on text. Nothing you did changed, the draw changed. ## What to do about it - If you only need to read, ignore it. Text is all you need for browsing, and the pictures finishing is not a precondition for anything. - If you need to see product photos, request a new circuit for the site and reload. A new draw is the only real fix and it costs a fresh cold load. - Open images one at a time rather than letting a gallery pull twenty at once. Twenty parallel requests on a thin circuit finish slower than five sequential ones. ## What it is not It is not the market throttling you, and it is not your account. Both would show up as errors rather than slow bytes. It is also not something a faster internet connection fixes, since your own link is nowhere near the bottleneck. ## How to read the result - **Images arrive in under a minute**: Ordinary circuit. Carry on and do not touch anything. - **Images take several minutes**: Thin circuit. Fine for reading, painful for browsing photos. Take a new one if photos matter. - **Images never arrive**: Either the circuit is nearly dead for throughput or the market is shedding static files under load. New circuit first, then another mirror. --- # The session freezes partway and then resumes URL: https://nexus-market-mirrors.online/signal/mid-session-stall Group: Latency First move: Wait it out How long to give it: Thirty seconds What you see: A working session that pauses for twenty to sixty seconds on a single action, then continues as if nothing happened. Everything is going fine and then a click does nothing for half a minute before the page appears normally. This is a rebuild, and the worst thing you can do to it is interrupt. ## What is happening Circuits are not permanent. Relays go offline, get restarted, or drop connections under load. When one in your path goes, the client notices, builds a replacement path and resends. The pause you feel is that repair, and it usually completes on its own. ## Why reloading makes it worse A reload during a rebuild cancels the request that was about to succeed and queues a new one behind the same repair. You wait for the rebuild either way and now you have also thrown away whatever was in flight. On a form or an order step, that is how a submission gets sent twice or lost. ## The rule for anything you were submitting - Never resubmit a payment or an order step during a stall. Wait for the page to settle and then check the order state before doing anything. - If a message or a form came back blank, look for the result in the account before writing it again. - Treat a stall on a payment page as a reason to slow down rather than speed up. ## When it is not a rebuild A rebuild resolves inside about a minute. A pause that lasts several minutes with nothing coming back is closer to the timeout case, and at that point a fresh circuit is the right move rather than continued patience. ## How to read the result - **Under a minute, resumes**: Normal circuit repair. Nothing to do and nothing to fix. - **Repeated stalls in one session**: One relay in your path is unreliable. Finish what you are on, then take a new circuit. - **Stall on a payment step**: Stop clicking. Wait, then verify the order state before touching anything again. --- # Uploads and large pages stall out URL: https://nexus-market-mirrors.online/signal/throughput-drop Group: Latency First move: New circuit How long to give it: Do not wait What you see: An upload that sits at a fixed percentage, or a long page that renders halfway and stops. Small pages fine, anything substantial dies partway. This is the clearest throughput signal there is, and unlike the others it does not improve by waiting. ## Why waiting does not help here Latency problems clear because queues drain. A throughput problem is a ceiling, not a queue. If the narrowest relay in your path can only push a trickle, another ten minutes buys you a slightly larger trickle and nothing more. The fix is a different path. ## What to do, in order 1. Request a new circuit for the site and retry the upload from the start. 2. If the second circuit is also thin, try a different mirror, which forces an entirely new path on both halves of the connection. 3. Shrink what you are sending. A smaller image is not a workaround, it is the correct answer on a network with these constraints. ## Before you retry an upload Check whether the first attempt partially landed. Sending the same attachment three times because each looked stalled leaves a mess that somebody has to sort out, and on a dispute it looks worse than the original problem. ## A realistic expectation Onion services are not built for bulk transfer. Photographs sized for a phone gallery are large by this network standard. Resizing before upload turns a five minute gamble into a ten second certainty. ## How to read the result - **Completes slowly**: Fine. Slow is the normal state for anything sizeable here. - **Stalls once, works after a new circuit**: Confirmed thin path. Nothing wrong with the market or your account. - **Stalls on two circuits and two mirrors**: The far end is shedding large requests under load. Come back later rather than retrying. --- # Signal group: Integrity The page arrives and something about it is wrong. These are the signals worth stopping for rather than retrying. --- # The address on the page is not the address in your bar URL: https://nexus-market-mirrors.online/signal/address-mismatch Group: Integrity First move: Stop immediately How long to give it: Do not proceed What you see: A login page that looks exactly right, where the onion printed on the page does not match what your browser shows in the address bar. Everything else on this site is about diagnosing a slow or absent page. This one is different. If the two addresses disagree, the diagnosis is finished and the answer is to close the tab. ## Why this check works when nothing else does A cloned page can copy the design perfectly, because the design is served to anybody who asks for it. Fonts, layout, wording, the lot. What a clone cannot do is live at the real address, since that address is derived from a private key it does not have. So it has to sit somewhere else, and your address bar shows where you actually are. Print the real address on the page and the contradiction becomes visible. ## How to run it 1. Load the mirror and stop at the login screen. Do not type anything yet. 2. Find the onion printed on the page itself. 3. Compare it against the browser address bar, starting from the end. The last eight characters are the hardest to fake convincingly. 4. If they match, sign in. If they differ by a single character, close the tab. ## Where the bad addresses come from Almost always from searching during an outage. A familiar address goes quiet, somebody wants in, they look for a replacement and take the first plausible result. Having the three addresses saved means that moment never arrives, which is the actual defence. ## If you already signed in somewhere wrong - Assume the username and password are gone. Change them anywhere else you reused them, which is the real cost of reusing. - Do not send anything further to any address that page gave you. - Come back through an address you copied from a source you trust and check the account from there. ## How to read the result - **Exact match**: Proceed. This is the check passing, and it is worth doing every single time. - **Cannot find it printed**: Do not assume the worst, but do not sign in either. Load a different mirror and compare what that one shows. - **They differ**: Close the tab. No further diagnosis, no second look, nothing typed. --- # The protection gate never lets you through URL: https://nexus-market-mirrors.online/signal/gate-loop Group: Integrity First move: Slow down How long to give it: Two minutes What you see: A checking or waiting page that completes and reloads itself instead of handing you the market. A holding page appears, does its check, and sends you back to itself. Round and round. The loop is usually caused by the thing people do when they are impatient. ## What the gate is doing Onion services get flooded, and the standard defence is to make every visitor do a small amount of work or wait a short time before being let in. The gate hands you a token when you pass. That token is what gets you through the door on the next request. ## Why the loop happens - The token did not stick. Cookies or storage blocked for the site means every visit is a first visit, forever. - The circuit changed between passing the gate and using the token, so the token arrived from a different apparent visitor. - You reloaded during the check. Each reload discards a nearly finished pass and starts the queue again. - The gate is simply saturated and shedding, which looks the same from your side. ## What to do 1. Let one attempt complete without touching anything, even if it looks stuck. This alone clears most loops. 2. Do not open the market in several tabs at once. Parallel attempts compete with each other for the same slot. 3. If it still loops, take a new circuit for the site and make one clean attempt on the new path. 4. If it loops on a new circuit, try a different mirror, which has its own gate and its own queue. ## What not to do Do not lower the browser security level to get past a gate, and do not install anything that promises to solve it for you. A gate is an inconvenience. Weakening the browser to skip it trades a two minute wait for a permanent problem. ## How to read the result - **Passes on the second try**: Normal. Gates are noisy and a single retry is expected behaviour. - **Loops until a new circuit**: Token and circuit fell out of step. Nothing was wrong with your account. - **Loops on every mirror**: The market is under a heavy flood. Come back in a few hours rather than grinding at it. --- # Logged out on every page you open URL: https://nexus-market-mirrors.online/signal/session-drop Group: Integrity First move: Check settings How long to give it: Do not wait What you see: A successful login followed by an immediate return to the login page on the next navigation. You sign in, click one link, and you are at the login screen again. Frustrating, and almost always caused by something on your side that is easy to find. ## Where sessions actually get lost | Cause | How to tell | Fix | | --- | --- | --- | | Cookies blocked for the site | Every login works and never sticks | Allow cookies for that onion address only | | New identity or restart mid session | It happened right after you cleared something | Sign in again and leave it alone | | Two tabs on different mirrors | Only one tab stays signed in | Use one mirror per session | | Session actually expired | Hours passed since login | Normal. Sign in again. | ## The mirror confusion Each address is a separate origin as far as your browser is concerned, even though all three reach the same market. A session established on one address does not travel to another. Two tabs open on two mirrors will fight, and the one you are not looking at will usually be the one that loses. ## What it is not A drop is not a sign your account is compromised or being watched. An account under someone else control does not log you out, it stays quiet so you do not notice. Constant logouts point at storage and origins, which is a much duller and much more likely explanation. ## While you are in there If a login screen ever accepts a wrong password without complaint, stop. That is not a session problem, that is a page collecting credentials, and it belongs to the address check rather than this one. ## How to read the result - **Sticks after allowing cookies**: Confirmed storage problem and it is now solved. - **Only when two mirrors are open**: Origin collision. One mirror per session and it goes away. - **Persists on one address alone**: Use a different mirror. Something at that address is not issuing sessions correctly. --- # The page loads but half of it is missing URL: https://nexus-market-mirrors.online/signal/partial-render Group: Integrity First move: Reload once How long to give it: Thirty seconds What you see: A page with readable content, no styling, and controls that do nothing when clicked. The text is all there but the layout has collapsed and nothing clicks. It looks alarming and is usually the dullest possible cause. ## The ordinary explanation The document arrived and the stylesheet or script did not. On a thin circuit that is common, because the extra files queue behind the page and some of them time out. What you are looking at is a partial delivery rather than a different page. ## How to tell it apart from something worse - Check the address bar. A broken render at the correct onion is a delivery problem. A broken render at an address you do not recognise is a different conversation entirely. - Reload once. A delivery problem usually fixes itself because the missing files are now closer to hand. - If the page comes back complete on a second load, that was it. Nothing else to investigate. ## When the security level is the cause On the strictest browser setting some scripts do not run at all, which can leave controls dead by design rather than by accident. That is a fair trade and worth keeping. If a page genuinely cannot work without scripts and you need it, decide deliberately rather than dropping the setting out of habit. ## What not to conclude An ugly page is not evidence of a clone. Clones generally look better than the real thing, because copying a stylesheet is trivial and they want you comfortable. Appearance is not the test. The address is. ## How to read the result - **Fixed by one reload**: Assets timed out. Ordinary and finished. - **Broken on every reload**: Thin circuit or the mirror is shedding static files. New circuit, then another mirror. - **Broken and the address looks wrong**: Ignore the layout. Close the tab. --- # Procedures The order that works: confirm the address before typing anything, take a reading before deciding an address is down, request a new circuit before switching mirrors, switch mirrors before concluding the market is down, and wait before searching for anything. --- # How to take an honest reading of a mirror URL: https://nexus-market-mirrors.online/runbook/take-a-reading Type: Method Time to run: 6 min Most people decide a mirror is broken after one impatient attempt. A reading takes three minutes and gives you an answer you can actually act on. ## The procedure 1. Note the time and paste the address. Do not type it. 2. Let the load run to completion or to its own timeout. Do not touch the tab. 3. Write down what happened and how long it took. An error code, a spinner, or a page. 4. Request a new circuit for the site and repeat once. 5. Repeat the same two attempts on a second address. ## Why the new circuit step matters Without it you are measuring one path through the network, not the mirror. Half of all apparent outages are one unlucky relay, and the second attempt on a fresh path tells the two apart for free. ## Reading the result | Attempt 1 | Attempt 2, new circuit | Conclusion | | --- | --- | --- | | Fails | Works | Your path was the problem. The mirror is fine. | | Works | Works | Healthy. Any slowness is load, not a fault. | | Fails | Fails | That address has a real problem. Try the next one. | | Fails on all three | Fails on all three | A service wide event. Wait, do not search. | ## The mistake that ruins readings Cancelling early. A cold connection to a busy onion service can legitimately take a minute, so an attempt abandoned at fifteen seconds produces no data at all. Two patient attempts beat ten impatient ones every time. ## What to do with the answer If one address works, use it and stop measuring. The reading exists to get you moving, not to build a picture of the network. Nobody is paying you to monitor this. --- # Choosing which of the three mirrors to use URL: https://nexus-market-mirrors.online/runbook/compare-the-three Type: Method Time to run: 5 min All three lead to the same place, with the same account and the same open orders. Choosing between them is about your path today rather than about the addresses themselves. ## What is genuinely the same - Your account, balance, orders and messages. There is one of each behind all three. - The listings, the vendors and the prices. - Escrow and dispute handling. ## What genuinely differs Only the path. Each address builds its own circuits, so on any given evening one may be quick and another sluggish, and that ordering can reverse within the hour. There is no permanently best address, which is why this site does not publish a ranking. ## A sensible routine 1. Try the address you used last time. Familiarity costs nothing and it usually just works. 2. If it is slow or errors twice, move down the list rather than retrying the same one. 3. Once one is working, stay on it for the whole session. Switching mid session throws away a warm circuit and logs you out. ## Do not open all three at once It feels efficient and it is not. Three parallel connections compete for your own bandwidth, and sessions on separate origins interfere with each other so you end up signed out of two of them. One at a time is faster in practice. ## Saving them properly Keep all three where you can reach them without searching. That habit is worth more than any speed comparison, because the reason people end up on cloned addresses is never speed. It is having nowhere to look when the familiar one goes quiet. --- # Requesting a new circuit, and when it actually helps URL: https://nexus-market-mirrors.online/runbook/force-a-new-circuit Type: Fix Time to run: 4 min One menu item fixes a large share of the problems on this site. It is also misused constantly, so it is worth knowing what it does before reaching for it. ## What it does It throws away the path your browser built for this site and draws a new one. Same address, same destination, different relays in between. Everything else stays as it is. ## What it costs - The page reloads and the next load is cold again, so expect the full setup wait. - Anything unsaved on the page goes away. - Your session usually survives, since it lives in a cookie rather than in the circuit, but a login screen appearing afterwards is not unusual. ## When it helps | Symptom | Helps | | --- | --- | | Introduction failed, repeated | Yes, this is the main fix | | Very slow first byte | Yes, a new draw is often much faster | | Images crawling, thin throughput | Yes, this is the only real fix | | Gate loop | Often, once the token and path line up | | Descriptor not found | No, the failure is before any circuit | | Address mismatch | No, and do not try. Close the tab. | ## New circuit is not new identity New circuit affects this site and keeps your session. New identity clears everything and closes all tabs. People reach for the second when they meant the first and then wonder why they are logged out of everything. ## Do not spam it Repeatedly redrawing paths costs the network work and gains you nothing after the second attempt. If two fresh circuits both fail the same way, the problem is not your path and another mirror is the better move. --- # Confirming you are on a real Nexus mirror URL: https://nexus-market-mirrors.online/runbook/confirm-the-address Type: Safety Time to run: 4 min A copy of the market can look perfect. It cannot live at the right address. That single fact is the whole of this procedure. ## The check 1. Copy an address from a place you already trust rather than typing or searching. 2. Load it and stop at the login screen. 3. Compare the onion printed on the page against your address bar, reading from the end backwards. 4. Only then sign in. ## Why reading backwards The interesting characters are at the end. Anybody generating a lookalike spends their effort on a matching prefix, because that is what people glance at. The tail is expensive to match and is where a fake usually gives itself away. ## What proves nothing - The page looking right. Stylesheets are public to anybody who loads the site. - A working login form. It works because it is collecting what you type. - A padlock or the absence of one. Onion addresses carry their own authentication and browser warnings about certificates say nothing useful here. - A search result ranking. Nothing about ranking is a statement of authenticity. ## If it fails Close the tab. Do not sign in to see what happens, do not send a test amount, do not report it from that page. Then change any password you reused elsewhere, because that reuse is where the real damage is. ## The habit that prevents all of this Keep the three addresses saved somewhere you can reach without a search engine. Every phishing story starts with a familiar address going quiet and somebody going looking. --- # What to do when none of the three answer URL: https://nexus-market-mirrors.online/runbook/all-three-quiet Type: Incident Time to run: 5 min Three addresses quiet at once is either a real event at the service or a problem in your own client. Telling them apart takes two minutes and stops you doing the dangerous thing. ## Rule out your own client first 1. Open any other onion service you know. If that fails too, the problem is yours. 2. Restart Tor Browser completely. This rebuilds guards and connections and clears a surprising share of total failures. 3. Check your clock. A badly wrong system time breaks onion connections in ways that look like everything being down. ## If other onions work and these three do not Then it is the service. That is genuinely useful information, and it means there is nothing to fix on your end. It has usually cleared within a few hours. ## The action that causes real losses Searching for a new address during an outage. This is the single moment phishing operators plan for. Their pages rank precisely because nobody looks for a market address until it goes quiet, and everybody who does is anxious and in a hurry. - Do not take an address from a search result. - Do not take one from a message that arrives helpfully during the outage. - Do not sign in anywhere to check whether an order survived. It will survive without your checking. ## What an outage does not do It does not consume your balance, cancel your orders or release escrow. Those live in the market and come back with it. Waiting costs nothing and acting in a hurry costs everything, which is an unusually easy trade to get right. ## Coming back When it returns, come back through an address you already had. Check the order state before doing anything else, and expect the first load to be slow because everybody else is returning at the same moment. --- # Glossary **Descriptor**: A small signed record an onion service publishes saying which relays will accept an introduction for it. If your client cannot find it, you get the not found error before any connection is attempted. **Introduction point**: A relay the service has asked to pass along connection requests. You never talk to the service directly through it, you only ask it to arrange a meeting. **Rendezvous point**: A relay you choose where both you and the service build circuits so the two halves can be joined. Neither side learns where the other is. **Circuit**: The path of relays your traffic takes. Onion connections use two of them joined in the middle, which is why they are slower than ordinary browsing. **Guard**: The first relay in your path. It stays the same for weeks on purpose, because rotating it constantly would give more chances to be observed rather than fewer. **Cold load**: The first page of a session, which pays for the descriptor lookup and both halves of the rendezvous. Expect tens of seconds. **Warm load**: Any page after the first in the same session, reusing the existing circuit. Usually a few seconds. **Time to first byte**: How long between pressing enter and the first data arriving. On an onion service this is mostly network setup rather than the site thinking. **Throughput**: How much data the path can carry per second. Separate from latency, which is why text can be instant while images crawl. **Protection gate**: A holding page that makes every visitor wait or do small work before entry, used to absorb floods. It hands out a token that gets you through on the next request. **Origin**: How a browser decides what belongs to what. Each onion address is its own origin, so a session on one mirror does not carry to another. **New circuit for this site**: A browser control that redraws the path for the current site only, keeping your session. Different from new identity, which clears everything. --- # Questions and answers **How many Nexus mirrors are there?** Three onion addresses, all listed on this site. They reach the same market with the same account, balance and orders behind each. **Which mirror is the fastest?** There is no permanent answer, which is why this site publishes no ranking. Speed depends on the circuit your client draws at the moment you connect, and that changes hour to hour. **Why does this site not show live status?** Because a truthful one is impossible. Reachability is a property of your path through the network, so a page telling you a mirror is up cannot know whether it is up for you. Taking your own reading takes three minutes and is actually accurate. **What does Onionsite Not Found mean?** Your client asked the network where that address lives and got nothing. Usually a mistyped address or a service that stopped publishing. Retrying rarely helps, switching mirrors usually does. **What does Onionsite Has Disconnected mean?** The record was found and the service did not answer, often during a restart or under heavy load. This is a more hopeful error than not found and frequently clears within minutes. **Why is the market so slow?** A connection to an onion service crosses about six relays and there is no cache anywhere in the chain. Tens of seconds for a first load is normal. If it is over two minutes, take a new circuit for the site. **Images will not load. Is something wrong?** Almost certainly not. Text needs a few kilobytes and images need megabytes, so a thin circuit shows exactly this pattern. A new circuit is the only real fix. **Why do I get logged out constantly?** Usually cookies blocked for the address, or two mirrors open at once. Each onion address is a separate origin to your browser, so sessions do not travel between them. **All three are down. What now?** Check whether other onion sites work. If they do, it is the service and it usually clears in hours. Do not go searching for a replacement address, because that is exactly when people land on a cloned one. **How do I know the page is real?** Compare the onion printed on the login screen against your address bar, reading from the end. A clone copies the design perfectly and cannot sit at the real address. **Does this site track visitors or run anything?** No. No accounts, no forms, no search box, nothing collected. It publishes addresses and explains what the signals mean, and it is not the market. --- End of file. Summary version: https://nexus-market-mirrors.online/llms.txt