It is not loading. Here is the order.

Failure one: the circuit is tired

Symptom: the mirror address sits at the spinner, but the problem is not the mirror. Test: open any other .onion page, a known one, and watch. If that page is also slow or also stuck, the circuit is the issue, not the address. Tor circuits age. A circuit that carried a heavy page, a video, a big download, degrades. The relays are still there, but the path is clogged, and every new request through it pays the toll.

The fixes, in order of least effort:

1. Shield menu in the toolbar, New circuit for this site. The browser builds a fresh three-relay path for that tab. Ten seconds, sometimes less.
2. Restart Tor Browser. Closes every circuit, clears the cached relay hints, builds everything from zero on the next start. Slower, but it resets the whole path, not just one tab's.
3. Switch networks. Mobile data instead of Wi-Fi, or the other way around. A provider that shapes Tor traffic on one network does not always shape it on another. If the market loads on mobile data and not on the home Wi-Fi, the provider is the variable, and the fix is the bridges section of the Tor Browser page.

If the other onion pages load fine and only this mirror hangs, skip to failure two.

Failure two: the mirror is down

Symptom: this address spins, the other two addresses in the block above load normally. The circuit is healthy, the queue works on the other mirrors, the captcha appears, the storefront renders. Only this one address does not come up.

That is rotation, not death. The market rotates its set of mirrors. A mirror leaves the set, a new one enters, and the published list catches up on its own schedule. A mirror that was live in the last signed list can be gone now, and the list that named it is a list from months ago. The address is not broken. It is simply not serving right now.

The move: go to the next address in the block above. Paste it, run the queue, click the circle. If the next one loads, the first one is out of rotation and the session is fine. No need to diagnose the dead address further. It will either reappear in a future list or it will not, and both outcomes are the market's business, not the reader's.

If all three addresses are up but one is noticeably slower than the others, that is also rotation in motion: load shifting between mirrors. The slow one is not broken, it is just carrying more.

Failure three: the market is queuing you

Symptom: the page loads. A spinner appears. The text reads "Do not refresh the page. Please wait... you are being forwarded to the market." The spinner runs for a while, maybe a couple of seconds, maybe a couple of minutes. Then the captcha: "Are you not a Robot? Click the broken circle (the one with a cut.)" with a 24 second bar.

This is not a failure. This is the front door. The queue is the market's way of spreading the load, and the captcha is its way of keeping scripted traffic out. Both are normal, both are expected, and both happen on every visit, not just on bad days. A reader who has been through it twice does not call it a problem. A reader who has been through it once and refreshed the page twice is in the queue again, behind the person who did not refresh.

The only mistake here is impatience. The spinner is not stuck. The bar is not broken. The market is doing the thing it does, and the session continues on the other side of the circle click. Full walk-through: opening the market, step by step.

Why a green dot next to an address is worthless

A number or a dot next to an onion address is a measurement of someone else's circuit, at someone else's moment. The person who ran the check had a path through three relays. The check passed on that path, at that time, from that machine, through that provider. When a reader clicks the address, none of that is reused. A new circuit is built, from scratch, through relays that may be different, at a time when the load on the mirror may be different, from a network that may shape traffic differently.

The green dot describes a past event on a path that no longer exists. It is a photograph of a door that was open, and the door in front of the reader is a different door, on a different path, at a different time. The photograph does not open the door.

The only honest test is the one that takes thirty seconds: open the address, run the queue, click the circle, look at the last six characters in the address bar. If the storefront loads and the six characters match, the mirror is up. If it does not, the mirror is not up, or the circuit is not there, or the provider is in the way. Three different causes, three different fixes, and all three are sorted out on the mirrors page. A dot on a list sorts out nothing.

When all three fail

All three addresses in the block above spin, or all three refuse the circuit, and the other onion pages load fine. The circuit is healthy, the browser is healthy, the network is healthy. The market is not answering. The search phrase for that moment is awazon market down, and the honest answer is in the next paragraph.

The queue is the front door. If the queue screen does not appear, if the address connects and then hangs with no spinner and no captcha text, the door is not just slow, the door is closed. Maintenance, a relay problem on the market's side, a mirror set in the middle of a rotation with no live entry point. The cause is on the market's end, and it is not visible from the reader's end.

There is nothing to do except wait and come back. No phone number to call, no support form to fill, no status feed to watch. The market has no clearnet presence, no contact channel, no channel at all outside the onion. The list of mirrors is published as a PGP-signed message, and the set rotates on its own schedule. The mirror that is down now may be the one that is up in a few hours, and the set that is live now may be a different set by the time the list updates.

Close the tab. Come back later. If the market was in maintenance, it will be back. If the set rotated, the new set will be the one in the market's next signed list. In the meantime, the circuit is not the problem, the browser is not the problem, and the reader did nothing wrong. The market is just not there, and that is the one failure with no fix on the reader's side.