Taking the detailed answer (thanks for that!) from
@tor.bjornebole2 into account, it's very possible that this is a carrier-based behavior that we really can't control from our end.
With that said however, I'll pass your question on and see if I can get a better explanation from our network team.