We're starting to suspect that in our AWS environment, that doesn't support ipv6 AAAA record DNS requests type 28 (not supported since our DNS proxy doesn't rather than anything AWS-y itself), that we might be hitting some of the issues reported in https://github.com/encode/httpx/discussions/2167
So this is a bit speculative, although from initial tests, it does seem to improve things
We're starting to suspect that in our AWS environment, that doesn't support ipv6 AAAA record DNS requests type 28 (not supported since our DNS proxy doesn't rather than anything AWS-y itself), that we might be hitting some of the issues reported in https://github.com/encode/httpx/discussions/2167
So this is a bit speculative, although from initial tests, it does seem to improve things