Right now, nodes which have pruning enabled will drop peers who ask for blocks older than the minimum limit:
However, nodes will also happily ask pruned (limited) peers for blocks beyond this range, despite knowing about it. This results in nodes asking pruned peers for blocks, and promptly being disconnected.
While this is fine and all, it does result in some weird unexpected behavior when a node knows mostly pruned nodes as it will end up inexplicably dropped from a bunch of its peers for no apparent reason.
I have proposed a fix for this in #14507 which tracks the peer's known best block and avoids asking pruned peers for blocks that would potentially result in violating the limit above, but I figured I should post an issue as well, so we have this tracked.