v1.1.1
What's Changed
Bug Fix — Indexer Scoring: Response Time and Success Rate
All indexers were reporting identical response time and success rate values (e.g. 2157.7 ms / 98.1%). The numbers looked plausible but were the same for every indexer regardless of actual performance.
Root cause: The scorer was fetching Prowlarr history per-indexer using an indexerId query parameter on GET /api/v1/history. Prowlarr silently ignores that filter — every call returned the full global history, so every indexer was computing the same global average.
Fix: Replaced the per-indexer history fetching with a single call to GET /api/v1/indexerstats, which returns Prowlarr's own pre-computed per-indexer averageResponseTime and query/failure counts. This is the same endpoint the Prowlarr UI stats page uses.
Side effect: A scoring run now makes 3 API calls total instead of N+2 (one history fetch per indexer). Noticeably faster on instances with many indexers.
After rescoring with the fix, rankings reflect actual indexer performance — fast, reliable indexers rise to the top, slow or backoff'd indexers fall accordingly.
What didn't change
- Health score formula and weights are unchanged
- Reorder logic and ignore/pin behaviour are unchanged
get_indexer_history()is retained in the Prowlarr client for future malicious content linkage
Full changelog: https://github.com/o51r15/inspectarr/commits/v1.1.1