What do you do when the table you were using goes dark?

First hour after the table stops loading

In the first hour the only thing that is still cheap is copying. Screenshot the rows you actually used rather than the whole table, note the date and time on the capture, and save the order numbers that came from those rows. Once a page stops rendering, no amount of later effort recovers a row you never copied.

Then check whether the failure is yours. A browser extension, a stale session or a blocked script produces a blank page that looks exactly like a dead service. Open the same address in a private window, try a second network, and note what each attempt returned before you conclude anything about the site.

1. Capture within the first hour, while anything still renders.
2. Retry in a private window and on a second network.
3. Note the exact time of each failed attempt.
4. Separate the failures: table page, account login, order page.

Copies of your own rows worth keeping

Not every row is worth saving. Keep the rows behind purchases you have already paid for, the rows behind orders that have not shipped, and the rows behind items you intend to buy again. Everything else is browsing, and browsing data has no later use.

For each kept row, record the item description, the seller name, the option you selected, and the order number it generated. That set of four details is enough to reconstruct what you asked for even if every listing behind it disappears, and it is also what a seller needs to identify the item in their own system.

Substitute sources and their footing

When one table stops being maintained, another appears, and the temptation is to treat any replacement as equivalent. It is not. The questions that decide whether a replacement is usable are whether it states what it measured, when it last checked, and how many rows it is carrying.

A source that cannot show what it measured is not a record. The desk dropped a packing recommendation after testing it on five soft-goods parcels and finding it changed the chargeable figure on none of them, which is the standard a claim has to meet before it is worth acting on. Apply the same test to a replacement table: if it cannot tell you where its numbers came from, treat its numbers as decoration.

Order-side checks that bypass the table

Your order does not depend on the table. It depends on the account you paid through, and that account has its own order list, its own receipt records and its own message thread. Log in directly, or through the platform address you know, rather than through a link from the table that stopped working.

If the account itself does not open, that is a different problem from a table that stopped being updated, and it is the one that deserves urgency. Community reports in August 2026 described the platform as no longer taking new orders, with Reddit threads in a replica community and a monitoring page on rep.tools cited as the source; this desk does not repeat that conclusion — the check you can run yourself is the one worth your time.

1. Open the account directly and confirm the order list still renders rows.
2. Check whether any parcel is sitting in a warehouse with a clock running.
3. Check whether a balance is held and what the withdrawal conditions say.
4. Keep every message in the platform thread rather than moving to email.

Migration decision rules for a live order

Move only the part of an order that can still be moved. An unshipped item in a warehouse can usually be transferred or shipped out, while a parcel already handed to a line cannot be redirected by anybody. Sorting your order into those two groups tells you whether migration is a real option this week or a plan for the next purchase.

Move when the account is unreachable, when the warehouse stops posting receipts, or when a balance cannot be withdrawn. Do not move simply because a table stopped being updated, because the table was never the thing holding your goods, and a rushed transfer reintroduces every risk you are trying to leave behind.

1. Can move: anything still sitting in a warehouse rack.
2. Can move: items not yet purchased from a seller.
3. Cannot move: a parcel already handed to a carrier, whatever the status says.
4. Deciding signal: whether receipts and withdrawals still work.

What a maintenance record has to show

A maintained table shows its work. There is a last-checked date, a statement of what was checked, and a visible change log when rows are added or removed. Those three things turn a list into a record, and they are the only way to tell an updated table from one that was built once and abandoned.

When you cannot find a last-checked date, treat every figure in the table as undated and re-check the parts you intend to act on. That is slower for one purchase and much faster than discovering a problem after the parcel has left.

When a table comes back and rows have moved

Tables often return. When one does, do not assume the row you saved is the row that is now published. Compare the item description, the option and the seller against your capture, and treat any difference as a change to be resolved before you rely on it again.

If a row changed and an order was placed from the old version, the capture is what proves what you ordered. That is the whole reason for copying in the first hour, and it is worth doing even when the outage turns out to be a browser extension and nothing more.

Deadlines that decide the outcome

Where the numbers in this entry come from

Origin: KB-2026-04 packing request test — the vacuum-bag request was dropped after it changed the chargeable figure on none of five soft-goods parcels. A source that cannot show what it measured, and what the measurement changed, is not a record this desk will act on.

◇KB-2026-11· 2026-09-30 See the batch ledger · Challenge a figure

Entries filed next to this one

• How do you recover a purchase made from a link that has since died?

  The purchase is anchored to the order record, not to the link, so recovery starts with the warehouse receipt and the payment record. Ask the warehouse which seller the item came from, ask the seller directly with the description and the option, and keep the answer dated.

• How do you move to another agent with an order already in flight?

  Split the order into three groups: items still in a warehouse rack, items not yet purchased, and parcels already handed to a carrier. The first two can usually be moved, the third cannot be redirected by anyone. Move for account-level failures, not for a slow week, and keep the old account open until the last parcel lands.

• What happens when QC rejects an item?

  A rejection means the warehouse will not store or ship the item as received, so the order pauses inside the handling window. You can ask for a re-check, a return to the seller, an exchange, or a refund through the platform, and the window — not the rejection itself — decides what stays available.

Gauges this entry points at

• Applicability protocol

  Work out which entries apply to your order right now.