FAQ
Why do onion addresses change instead of staying fixed?
Onion services can change address when operators rotate keys, move infrastructure, or respond to disruptions—there is no permanent guarantee tied to a single address. Users should treat any particular onion URL as a temporary access point that may eventually stop working.
1Why does a working onion address stop resolving?
The fastest answer: onion addresses are not static URLs. Operators rotate them under operational pressure, and old ones die while the service itself stays alive — which is exactly why the danger of relying on outdated bookmarked URLs is higher than most users assume. A saved link that worked last month can stop resolving not because the market vanished, but because its entrance moved.
Think of an onion address like a temporary door number in a building where the landlord deliberately changes the numbering. The building is still there, the rooms are the same, but anyone holding an old slip of paper with yesterday’s number walks up to a wall, not a door.
What forces an address to die
- Network congestion and DDoS pressure — when one entrance is hammered, operators open another and abandon the first
- Infrastructure seizure or takedown of a mirror — a domain can be burned while the core service moves elsewhere
- Operational rotation — links are treated as disposable access points, not long-term identities
- Defensive compartmentalization — different user groups may receive different entrances, and a leaked one gets retired
- Address goes live Users share it, phishers copy the URL, and traffic concentrates on a single point
- Pressure on that address increases Attackers target it, or infrastructure behind it becomes unreliable
- Operator rotatesA new onion address is generated and distributed through controlled channels
- Old address diesIt stops resolving, returns errors, or loads a warning page
- Service continues The market is still operational, but only through the new entrance
An onion address is closer to a session ticket than to a permanent street address. Treating it as a fixed destination creates a false sense of continuity.
If a saved Abacus link stops loading, the most likely explanation is rotation, not a full market outage — but the only safe reaction is to re-verify a current address through channels you already trust, never through a search result.
2What actually rots: link rot vs. market downtime
Link rot is a dead bookmark, not a dead market. An onion address that no longer resolves is simply an endpoint the service has retired, rotated, or abandoned — while the market behind it may be operating normally on a different address the same day. Downtime is the opposite: the address still exists, but the service behind it is temporarily unreachable because of infrastructure failure, maintenance, or an attack on availability. Users routinely misread the first as the second because both look identical in Tor Browser: a blank error page and a spinning connection indicator.
| Signal | Dead bookmark (link rot) | Dead market (downtime) |
|---|---|---|
| The address itself | no longer published or rotated away | still published and structurally valid ;; What fails | your stored endpoint | the service behind the endpoint ;; Balances and escrow | unaffected, still on the backend | may be inaccessible during the outage ;; What you can fix | yes — find a current published address | no — only waiting or a mirror helps ;; What you should conclude | update your source of truth | check operational status before assuming exit scam |
Why the two feel identical in Tor
Tor Browser deliberately does not give you a meaningful error code for an unreachable onion service. You typically get a generic “address couldn’t be found” or “connection timed out” page regardless of cause. That is by design: the network wants to hide which services existed, which were known to the directory, and which failed at a specific moment. The result is that a typed or bookmarked address tells you almost nothing about the state of the market — only that your client could not reach a service at that address through that circuit.
The practical rule
Treat an address that stops resolving as a signal about the address, not about the business. Retry is fine; the first failure may be a relay issue, a slow hidden service descriptor fetch, or an overloaded introduction point. But after two or three failures across different circuits, stop troubleshooting the address and question your source for getting it. A live market that cares about continuity publishes working access points; a bookmark you saved weeks ago has no such guarantee.
Never treat repeated failed loads of an old Abacus link as proof of an exit scam or market seizure. You are seeing endpoint failure. The market status is a separate question, answered only by current operational information, not by your browser tab.
3How should you think about finding current Abacus access points?
The practical answer is that no single saved link, forum list, or directory page should be treated as the permanent way to reach Abacus. Instead, you want a small set of independent sources, each checked against the others, so one outdated post cannot send you to a stale or hostile address.
Onion addresses move because their operators face operational and abuse pressure: relays get blocked, hosts disappear, mirrors are rotated ahead of expected takedowns, and phishing clones try to occupy the space a dead link leaves behind. That means access is not a static bookmark but a current lookup problem. The safest mental model is to treat every link as a candidate, not a credential.
Source
How to use it
Private saved records
Keep only as a fallback; never as proof that a link is still live
Trusted contact
Use for confirmation, not as a single source of truth
Live reachability check
Verifies a candidate opens, but not that it is the real Abacus
Independent mirrors
Compare addresses across sources; reject lone outliers
A good approach is to gather two or three unrelated starting points — for example a previously working private note, a contact you already trust, and one active mirror directory. When they agree on an address, the signal is stronger; when they disagree, delay action until the conflict is resolved.
The same logic applies over time. A link that worked yesterday is not evidence it works today, and a link that loads today is not evidence it is the genuine market. What matters is whether the source and the address line up together, because both can be imitated independently.
A forum post or link list is a snapshot, not a guarantee. If it was captured weeks ago, its Abacus onion address may already be abandoned, rotated, or replaced by a phishing copy that loads normally.
So the goal is not to find one “official” page to believe forever. It is to keep checking the current candidate against sources you have already established, and to treat any sudden change — a different address, a weird SSL-style warning, an unexpected welcome screen — as a reason to stop and re-verify rather than click through.
4What to do when an old Abacus link loads, warns, or redirects?
An odd session means the page resolved, but your browser is no longer inside the expected trust boundary. Treat warnings, layout changes, or redirects as the session telling you it has already failed, not as a challenge to fix it on the fly.
When a saved Abacus onion address loads but Tor shows a certificate mismatch, a missing padlock, or an unverified address bar, the connection path changed in some way. That does not automatically mean you are on a fake copy. Sometimes the service reconfigured its front layer, moved to a new v3 key, or is balancing visitors through a different introduction point. But from your side, none of those details make the page trustworthy again. A warning is a cheap way to stop and restart, while logging in anyway or entering a passphrase can be the most expensive mistake of the session.
A changed layout is different from a failed handshake. Markets do alter their interface. If the design looks different but the URL is the exact address you intentionally wanted, take it as a signal to slow down, not as proof of phishing. A cloned page can reuse every visual detail of the real one. A real page can push an update that moves the login box by ten pixels. Appearance alone tells you very little.
- Page loads but shows a security warningDo not continue. Close the tab and open a fresh Tor Browser session.
- You see a redirect or a second address appears Stop. A market does not need you to chase moving URLs after you arrived at the correct one.
- Layout looks different but the address is the one you expected Pause and compare against a known current access point from your own saved source, not from memory.
- You already entered anything or started a session Treat that session as exposed. Rotate what you used, and do not reuse the same input on a “working” link.
Think of a half-working onion session like a door that opened, then the hallway lights flickered. You are not safer because the door opened; you are further inside an unknown space.
The worst move is to rationalise a warning because a busy schedule says “just this once.” A cloned login page does not need to look broken to capture what you type.