3 ms·
As your answer suggests, it's likely an MTU problem. From a quick tcpdump, news.yahoo.com doesn't do any MTU problem compensation in the tcp handshake. If your
by toast0 5y ago
As your answer suggests, it's likely an MTU problem. From a quick tcpdump, news.yahoo.com doesn't do any MTU problem compensation in the tcp handshake. If your network is sending out a bad MSS on TCP, and there's nothing in the return path that sends back icmp needs-frag, you're not likely to get back any large packets from them (I don't know if they have path mtu probing enabled, or if it is, if it runs fast enough to be meaningful... probably not given your experience).
If your network is sufficiently messed up, the incoming SYN+ACK from Yahoo may encourage your client to send too large of a packet on the local network, which could be dropped without a needs frag as well, if you've got enough cookies, that can cause connection stalls early on.
From my time at Yahoo Travel, and the hostnames I get back from DNS, it doesn't look like news.yahoo.com is using a CDN; I'm getting geodns'ed to a load balancer in a nearby colo. The images (s.yimg.com) are served by Yahoo's in-house CDN though and get an edge box in a nearby internet exchange (I think; can't exactly tell).