What happened these past days: the May 21–22 loading error and how we fixed it
For a couple of days, some visitors saw an error when loading the site. No data, accounts or payments were affected. Here's what happened, why it took us time to catch, and what we changed so it won't happen again.
If you visited TorrentClaw on May 21 or 22, you may have hit a browser screen reading "This page couldn't load — A server error occurred. Reload to try again." Sometimes a reload fixed it, sometimes it came back. We're sorry for the disruption, and we want to explain exactly what happened, in full transparency.
What happened
TorrentClaw runs on two twin web servers behind a load balancer so we can ship updates without downtime. During a routine update, one of the two servers got stuck on an old version of the site while the other had the new one. The balancer splits traffic between them, so roughly half of all visits landed on the stale version — which requested site files that no longer existed, and that's where the error came from.
Why it took us time to notice
This failure is sneaky: it produced no server-side errors (both servers reported themselves healthy) and only surfaced inside your browser. Our usual alarms watch for server errors, and there weren't any, so nothing fired. That's the part that stings most, and the part we've now fixed at the root.
How we fixed it
We rebuilt the lagging server and confirmed both now serve the exact same version. We also added an automatic check to our deploy system: from now on, if the two servers don't end up on identical versions, the deploy aborts itself and alerts us instead of silently going half-broken. The specific gap that caused this can no longer ship undetected.
What matters for you
No data was affected — not accounts, passwords, subscriptions, payments, or your privacy. The catalog, your lists and your plan are exactly as they were. This was a delivery problem with the website, not with the data behind it.
If you still see the error
Your browser may have cached the old version. It usually clears on its own next visit; if it persists, go to herecomesaconsequence.com/sw-reset.html (it clears the local cache and redirects you) or force-reload with Ctrl/Cmd + Shift + R.
Support and backup access
Any questions, reach us from the Contact page or at [email protected]. And remember TorrentClaw is reachable from several mirror domains in case one ever fails: herecomesaconsequence.com (main), torrentclaw.to, and torrentf3aifidcsaaanmnmuhv2s53r6hqsl3zkmfidiaxainkeqk5id.onion (Tor network).
