We were experimenting some rate limiting settings and the load balancer IP in front of the hn cluster wasn't excluded, both features haven't been mixed before (doesn't make much sense to rate limit a search cluster behind a load balancer).

Sure thing, we’re experimenting with some Load-Balancing heuristics and instrumentations, and it looks it got rate-limited by the engine who got surprised all traffic was coming from a single IP /o\