Incidents reported on status page for nekoBT https://status.nekobt.to/ en https://status.nekobt.to/incident/1041501 Sun, 30 Aug 2026 16:14:00 -0000 https://status.nekobt.to/incident/1041501#4abeb2f77c535fa42e7423389a255d2bbd90b4a4996fb9ab9f302f422f2d23d7 **Summary** For most of 30 August, the site and tracker were intermittently slow or unavailable. Announces and page loads timed out for many users. The service is now stable. No data was lost, and no user data was accessed or exposed. Torrents, accounts and stats are unaffected. **What happened** Our servers began receiving substantially less processing capacity than they are allocated (high CPU steal). This happened below the level we operate at, and was not visible or controllable from inside our own systems. With roughly a third of our capacity gone, requests that normally complete in milliseconds started taking seconds. On its own that would have been just higher latency. What made it an outage was how our front-end responded: connections accumulated faster than they were released, and each one held far more memory than it needed. That became self-sustaining. The service would recover briefly, get overwhelmed by clients reconnecting at once, and fall over again. An automated recovery process made this worse. It could not distinguish "the service is broken" from "the machine has no capacity right now", so it restarted things during the second case, dropping every connection and triggering another reconnection wave. **What we changed** - Corrected timeout and memory settings so the front-end sheds load instead of accumulating it - Removed the automated restart process, replacing it with one that only responds to genuine failures, not load issues - Reduced cryptographic overhead across our infrastructure, recovering a meaningful share of compute capacity **What's next** We are working with our infrastructure provider on the underlying capacity shortfall, which remains the root cause and is not something we can resolve alone. **Apology** Sixteen hours is a long time to be unreliable, and several of the things that turned a slowdown into an outage were ours. The changes above address those directly. Sorry for the disruption. https://status.nekobt.to/incident/1041501 Sun, 30 Aug 2026 00:30:00 -0000 https://status.nekobt.to/incident/1041501#acd5a1158c6d7f9b121ebc80839e9324628660ef45e3862a443cef98084bef98 Performance begins to degrade https://status.nekobt.to/incident/967424 Sat, 18 Jul 2026 00:10:00 -0000 https://status.nekobt.to/incident/967424#276283d3e7ba1f946f9a9803d160ae3ee4ca6c4b77197bc6a4034ffd292eb956 Services should be recovering now. Thank you for your patience. https://status.nekobt.to/incident/967424 Fri, 17 Jul 2026 19:17:00 -0000 https://status.nekobt.to/incident/967424#aa4bd323452e5b90de67643c78039ac4dc7aa2c841e9e830888fd5967de62ecb API and Tracker are down unexpectedly due to an issue with a service provider. Expected to be back around 2026-07-18 00:00 UTC. https://status.nekobt.to/incident/850676 Mon, 16 Mar 2026 19:30:00 -0000 https://status.nekobt.to/incident/850676#6f3cc8e4739ff611c1538cf745e2ed941177d8a4ff0e21700423f19605039f47 We are working to migrate our servers. https://status.nekobt.to/incident/809125 Wed, 21 Jan 2026 18:58:58 -0000 https://status.nekobt.to/incident/809125#c519090d814fbf439d70ff12f5436a295be822e5ffcd88f9fada8340895b2f76 Maintenance completed https://status.nekobt.to/incident/809125 Wed, 21 Jan 2026 17:40:42 -0000 https://status.nekobt.to/incident/809125#254e556d952b46e6c88a22716d4f5370315ac5d488ce74c1accaafbc2e0bf20d Sonarr has corrupted and several backups are not valid. Please be patient whilst we restore the site. https://status.nekobt.to/incident/808295 Tue, 20 Jan 2026 18:30:00 -0000 https://status.nekobt.to/incident/808295#aea329198b372bfb7de118dc6e281a60fbd32eeea10fda1711a03980f63a217f Fixed. All endpoints have been restored. https://status.nekobt.to/incident/808295 Tue, 20 Jan 2026 13:30:00 -0000 https://status.nekobt.to/incident/808295#4a43cb3c9cc51230b1e73adce1ce3174b9e8c3f4218a9ffada247ad499e7ebe8 Endpoints that use Sonarr are failing due to Sonarr falling into a partly corrupted state.