What happened on August 5: the outage, and what we changed

For part of the morning the site was slow or unreachable. This was not a hack: someone pointed a crawler at us to copy our entire torrent and NZB catalogue in one go, and the sheer volume took us down. Here's the full account of what broke and what we've changed.

If you tried to use TorrentClaw on the morning of August 5, you may have found the site slow, half-loaded, or showing an error page instead of loading at all. It was our fault to absorb, not yours to suffer, and we're sorry. Here is what actually happened, including the parts that are uncomfortable to write.

What happened

This was not a hack, and that is worth saying up front: it was a crawler. Someone wanted to copy our entire catalogue — every torrent and every NZB — and instead of asking for it slowly, asked for all of it at once from tens of thousands of different addresses, rotating constantly.

The problem was how. Almost every request asked for a page nobody had ever asked for before, so almost none of them could be served from the ready-made copies we keep for speed. Each one had to be built from scratch, and each one produced a new copy to store.

That is what did the damage. The stored copies grew far faster than anything we had planned for, and eventually filled the space available. Once there was no room left to write, the site could no longer do its job.

Distinct IP addresses24,811/hour
Requests56,677/hour
Distinct pages requested43,219/hour
Served from a ready-made copy2.5%

a normal visitor: 37%

A normal visitor hits those ready-made copies on more than a third of their requests. The crawler, on 1 in 40.

Per-hour figures, sustained for hours. 24,811 addresses for 56,677 requests: about 2 each, spread thin so it wouldn't look like one source. No person browses like that.

Why it turned into an outage

One exhausted resource became five failures feeding each other. The site couldn't write, so it slowed down. Because it was slow, our own systems marked it as unavailable and stopped sending it traffic — including traffic it could have served. And because visitors were seeing errors, the automated checks that watch our health started running far more often, which piled more work onto the very thing that was struggling.

That last part is the one worth naming plainly: for a while, the health check had become a significant share of the load. A system meant to measure the problem was making it worse.

The part that stings

We have a protective layer whose whole job is to stop exactly this kind of attack. It had silently stopped working — still reporting itself as running, while doing nothing. Nobody noticed, because the thing we were checking was whether it was alive, not whether it was actually working.

That is a monitoring failure as much as a technical one, and it is the change we care most about.

What we changed

There is now a hard ceiling on the storage that filled up, enforced from outside the site itself, so it holds even if the site is unhealthy or not running at all. We gave the site substantially more room to work in, so a traffic spike can no longer push it over a cliff. We made the failure detection less trigger-happy, so a brief hiccup no longer takes everything offline. And the health checks can no longer become the load — they answer from a short-lived cache, which still surfaces a genuine failure within seconds.

We have also tightened who can reach us and how, and changed how we verify that our protective layers are genuinely working rather than merely switched on.

About the torrentclaw.to mirror

The mirror is temporarily restricted: it currently answers app and API traffic only, so the unarr agents and integrations keep working normally, but browsing it in a browser returns a short message pointing you to herecomesaconsequence.com. That restriction is deliberate — it is what stopped the attack from reaching us — and we will lift it once the mirror can defend itself properly. Use herecomesaconsequence.com in the meantime.

Support

If something still looks wrong for you, tell us from the Contact page or at [email protected]. TorrentClaw also stays reachable from herecomesaconsequence.com (main) and torrentf3aifidcsaaanmnmuhv2s53r6hqsl3zkmfidiaxainkeqk5id.onion (Tor network).