Infrastructure Health
Frontend Nodes
StableTor Hidden Services (V3) routing & load balancing.
Monero Daemon
SyncedDeposit detection & sub-address generation.
Bitcoin Node
CongestedMempool heavy load. Expect confirmation delays.
Private Mirrors
ActiveRotational links for vendors and Verified buyers.
Ticket System
Low LoadSupport queues and dispute resolution staff.
Anti-DDoS
StandardEndGame filter and queue management system.
🌐 Network Architecture & Latency
Many users ask: "Is Torzon down or is my connection slow?" Understanding the distinction is crucial for navigating the darknet efficiently. Torzon operates on the Tor (The Onion Router) network, which prioritizes anonymity over speed. When you connect to a Torzon mirror, your traffic is encrypted three times and routed through random volunteer nodes (Entry Guard, Middle Relay, Exit/Rendezvous Point).
If the Torzon status indicators above are green, but you cannot load the page, the issue likely lies within your specific Tor circuit. A "slow" middle relay can increase latency from 2 seconds to 30 seconds, causing a timeout.
The Solution: Do not panic. Simply request a "New Identity" in your Tor Browser (Ctrl+Shift+U) to force the creation of a new circuit. Alternatively, verify the onion link you are using against our Verified Mirrors List. Using an outdated or phishing link will often result in a connection refusal.
🪙 Monero Daemon Synchronization
We utilize a custom high-performance Monero (XMR) daemon to scan the blockchain for incoming deposits. Occasionally, under heavy load or during network-wide spam attacks on the Monero network, our node may fall behind the block height.
When the status shows "Syncing" or "Lagging", your deposits are safe. They exist on the blockchain but have not yet been indexed by the market's wallet. Once the node catches up (usually within 20-60 minutes), your balance will update automatically. Creating multiple support tickets during a sync event only slows down our support staff. Please check this Status page first.
🛡️ DDoS Mitigation "EndGame"
Torzon employs the "EndGame" anti-DDoS filter, a robust solution designed to repel botnet attacks common in the darknet market ecosystem. During a Layer 7 HTTP flood, the filter automatically escalates security protocols.
What you might see:
- • Queue Screen: You are placed in a waiting line. Do not refresh; you will be redirected automatically.
- • Hard Captchas: The difficulty of the clock/image captchas will increase to exclude bots.
- • Login Loops: If your session expires rapidly, ensure your browser allows cookies for the duration of the session.
If the attack volume exceeds 500k requests per second, we may temporarily restrict access to "Private Mirrors" only. Vendors should always keep a private mirror bookmark saved.
🔧 Maintenance Windows
Regular server maintenance is performed every Sunday at 04:00 UTC. This window is used for database optimization (PostgreSQL vacuuming), PGP key rotation, and server security patches.
Downtime during maintenance rarely exceeds 45 minutes. If Torzon is inaccessible for longer than 2 hours without a notice on this Status page or our official Dread forum thread, please assume a network-wide issue is occurring and check back later.
Connection Troubleshooting
Torzon is "Online" but I can't connect
This is a client-side routing issue. Try the following:
- New Circuit: Click the "Broom" icon (New Identity) in Tor Browser.
- Check Bridges: If you are in a censored region, use "obfs4" bridges in Tor connection settings.
- Disable JavaScript: While Torzon works best with JS enabled for captchas, try setting security to "Safest" momentarily to see if the static HTML loads.
I passed the Captcha but get redirected back
This is known as a "Login Loop". It happens when your browser isn't saving the session cookie.
1. Ensure your browser is not in "Always Private Browsing Mode" (Standard Tor Browser is fine).
2. Verify your system clock is correct. Timestamps that drift more than 60 seconds cause session invalidation.
The page looks broken (CSS not loading)
Sometimes the market loads, but without styles (white background, text only). This means the resource server (CDN) is blocked by your specific exit node. Refresh your identity (Ctrl+Shift+L) to get a new exit node.
Incident Post-Mortems
Transparency is key. Below is a log of recent infrastructure events and their resolutions.
Resolved: Bitcoin Mempool Congestion
Impact: Deposits taking 2+ hours; Withdrawals stuck.
Analysis: A surge in BRC-20 token minting clogged the Bitcoin network, driving fees to 400 sats/vB. Our dynamic fee estimator initially set fees too low.
Resolution: We manually bumped the fee rate for all pending withdrawals (RBF - Replace By Fee). The dynamic estimator has been recalibrated.
Mitigated: Layer 7 DDoS Attack
Impact: Intermittent 502 Bad Gateway errors on main onion links.
Analysis: A botnet targeted the search endpoint with malformed queries attempting to overload the PostgreSQL database. Peak traffic reached 1.2M req/sec.
Resolution: "EndGame" filters were deployed. Captcha difficulty was raised to Level 3 (Image Rotation). Attack subsided after 4 hours. No user data was compromised.
Scheduled Maintenance Completed
Summary: Routine optimization. Monero wallet daemon upgraded to v0.18.3.3 to support latest Bulletproofs+. Database vacuuming reduced query time by 12%.
Warrant Canary
VALIDThe presence of this message confirms that Torzon Market has NOT been compromised, served with a warrant, or forced to log user data by any third party.