Awazon Market Status: Mirrors and Access Queue
This page shows the current state of the three Awazon Market mirrors and explains what the access queue means when one of them is slow. The status here is a snapshot, refreshed on a schedule, and the most current word on any mirror is the one you get by opening it in the Tor Browser.
| Mirror | Status | Last checked |
|---|---|---|
awazonozc4jwyrveu4473igv5ldt2hnccl2s7lerm2z27cvrc22e4uyd.onion |
Online | October 8, 2026 |
awazonth6ocz5cyos63czmhtsglqr7ydkdcc4lopux7nxbauoo2qmvyd.onion |
Online | October 8, 2026 |
awazonvaqbgkhirejon6qnlxcjibrhkqhzh2xb2lclc6t67vxhlvjkyd.onion |
Online | October 8, 2026 |
Reading the status
All three mirrors point at the same backend, so the status of one says a lot about the others. If all three show online, the market is reachable and any of them will open your account. If one shows slow or queued while the others are fine, that is a congested path, not a down market, and the correct response is to open the next one rather than troubleshoot the slow one. If all three are unreachable at the same time, check the Tor Browser's own connection status first, because a stuck client side connection produces the same symptom as a real outage and is more common than one.
The access queue is not downtime
When a mirror is under heavy load it shows a loader telling you not to refresh. That is a queue, not a failure. It exists to flatten traffic spikes and to make scraping expensive. The correct response is to leave the tab open and wait. Refreshing resets your place in line, which is the one action that makes a slow open slower. Most queues clear within ten minutes under normal peak conditions. If a queue drags well past that, switch to the next mirror rather than reloading, and check the operator thread on Dread for a signed note if you suspect a rotation is in progress.