Awazon Market Status. Mirror Uptime and the Access Queue
At the time of last update, all three official mirrors are operational. Each runs on Tor v3, begins with the string awazon, and requires no JavaScript. If you read this page, the catalog is accessible, which is a good sign.
Current mirror status
| Mirror | Status | Last checked |
|---|---|---|
| awazonvewzuve3emyxtz2z7ko6bjv6m6qieioi2tuvbgwiomn6vyryyd.onion | Online | 30 September 2026 |
| awazonvjpi6bdysnad23ydgscomsku53wnfewrbbpxobvzow5xe6nyyd.onion | Online | 30 September 2026 |
| awazonwilo4vky6obkwrkv62vx24tnf5323pts6d7gohdoj4pjt646qd.onion | Online | 30 September 2026 |
How the status is checked
The team pings each mirror on a schedule. Failures get marked and removed from active rotations. New addresses appear only after a PGP-signed announcement on Dread. Treat unsigned addresses as suspicious regardless of how legitimate they look.
What to do if a mirror does not load
Try the second and third mirrors immediately. Verify that your security slider is set to Safer. Copy the full address again, ensuring all 56 characters match exactly. Wait ten to fifteen minutes. Short outages usually resolve on their own within that window.
Access Queue is not a failure
If a loader page appears with a do not refresh notice, it is a queue, not downtime. DDoS protection limits simultaneous connections during peaks. The correct reaction is leaving the tab open and waiting. Refreshing resets your position in line. The full behavior of the queue is documented in Awazon Market Access Queue Explained.