What we saw this week
Group A of the 2026-W39 snapshot holds 31 wrapped ACBuy addresses pulled off public sheet pages. Requested one at a time, every single one failed at the network level. Not one answered. Group B, the 62 source addresses read off a maintained directory, came back the other way round.
Then we rebuilt the Group A addresses from the source marker inside each one. Thirty-one out of thirty-one returned a normal response. The wrapper had died; the listing behind it had not moved. That gap is the whole answer to this question.
One more number: 113 directory addresses were dropped from that collection window because the host stopped accepting connections, and they are left out rather than written down as failures. Excluding them keeps the table honest about what was actually seen.
How the call gets made
Each check ran with an 8-second timeout, no cookies and no login, and two things were recorded: whether the address answered, and where it landed. Nothing about your account, your region or your browser changes that outcome, so a result you reproduce yourself should look like ours.
Read a failure carefully before you act on it. A connection that fails means the wrapper did not answer in that moment. It does not mean the listing is gone, and it is not a stock notice. The item ID and the source marker sit inside the address you already have.
Our 2026-W39 status counts read RESOLVES 93, with zero MOVED, zero GONE and zero SHIELDED. A clean sweep like that describes one collection window rather than a forecast, and it is worth remembering that the wrapper layer failed in the very same window that produced it.
Three ways to read it
Reading one: the wrapper is dead, the listing is alive. Your link failed, the source address answers, and a rebuild gets you back to the item. This is what all 31 samples looked like this period, and it is the common case.
Reading two: both are dead. The wrapper fails and the rebuilt source address returns 404 or 410, or the listing has been taken down by the seller. That is a GONE reading, and no amount of rebuilding brings the item back. Nothing in the 31 samples landed here this period.
Reading three: neither result is trustworthy. A timeout, a refused connection or a verification wall leaves you with an UNRECORDED or SHIELDED reading, which is a statement about the check rather than about the item. The honest move is to run it again later instead of assuming the worst or the best.
What to do for each
For reading one, rebuild. Run the rest of the sheet through the link resolver in small batches, three rows at a time, and note which ones answer. Then paste the rebuilt marketplace address into an accepting platform instead of the wrapped one. The platform ledger shows which platforms are still taking orders.
For reading two, drop the row and stop spending time on it. You can keep the original address in your notes so the trail stays readable, but there is nothing left to retrieve. Sheet space is better spent on the rows that still answer.
For reading three, retry before you conclude anything. Wait an hour, run the same address again, and treat only a repeated result as a verdict worth writing down. A single messy response is not evidence about a listing, and it is not a reason to strike a row off your sheet.