Awazon Market status: mirror uptime and the access queue
As of the last update on 18 September 2026, all three official mirrors are operational. Each runs on Tor v3, every address begins with "awazon", and none require JavaScript. If you are reading this, the catalog that feeds these pages is reachable, which is a good sign the underlying mirrors are up.
Current mirror status
| Mirror | Status | Last checked |
|---|---|---|
awazonvewzuve3emyxtz2z7ko6bjv6m6qieioi2tuvbgwiomn6vyryyd.onion | Online | 18 September 2026 |
awazonvjpi6bdysnad23ydgscomsku53wnfewrbbpxobvzow5xe6nyyd.onion | Online | 18 September 2026 |
awazonwilo4vky6obkwrkv62vx24tnf5323pts6d7gohdoj4pjt646qd.onion | Online | 18 September 2026 |
How the status is checked
The Awazon team pings each mirror on a schedule. When one fails, it is flagged and removed from the active rotation. A replacement address only appears after the team posts a PGP-signed announcement on the Dread forum, so a new onion you saw floating around elsewhere is not confirmed until that signature exists. Treat unsigned addresses as suspect.
What to do if a mirror does not load
- Try the second and third mirrors before assuming anything is broken.
- Confirm your Tor Browser security slider sits at Safer, the level the market expects.
- Re-copy the full address and make sure all 56 characters transferred, no truncation at the edges.
- Wait 10 to 15 minutes and retry, since short blips often clear on their own.
Access Queue is not a failure
If the page opens on a loader that says "Do not refresh the page", you are in the access queue, not looking at a downtime screen. The DDoS protection throttles simultaneous connections during peaks, so the right move is to leave the tab alone and let your place in line advance. Refreshing drops you to the back and resets the wait.