Terrible latency/peering from Level3
I want to preface this by saying that this isn't a new issue and it has been happening for maybe 2 years now. My main issue is with online games, but it impacts other aspects of my internet experience as well.
I usually play online PC games on US servers. Both US East (Virginia) and US West (Seattle/California). For these games, as some of you may know, latency or ping is very important in determining the quality of your game. While these issues are prevalent in-game, I think this tracert will also prove a point. And before anyone says "but most networks don't prioritize ICMP packets!" I know that already, so don't bother.
Tracing route to eat.valve.net [188.8.131.52] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms homeportal [192.168.1.254] 2 * * * Request timed out. 3 24 ms 23 ms 23 ms 184.108.40.206 4 26 ms 23 ms 27 ms 220.127.116.11 5 28 ms 26 ms 26 ms 18.104.22.168 6 36 ms 35 ms 35 ms 22.214.171.124 7 107 ms 106 ms 107 ms ae-2-52.edge2.Seattle3.Level3.net [126.96.36.199] 8 122 ms 130 ms 119 ms ae-2-52.edge2.Seattle3.Level3.net [188.8.131.52] 9 112 ms 111 ms 111 ms eat.valve.net [184.108.40.206] Trace complete.
This is a tracert from my house in Miami, Florida to Seattle, Washington. It looks alright at first, from ATT in Miami all the way to 220.127.116.11, which is an ATT somewhere in Kansas. This is already about half the distance to Seattle and it only took 35ms for this ICMP packet to get there, throttling or not.
The issue here is when we go from ATT to Level3. I don't think there is any reasonable world where that jump should take well over 100ms. I really don't know what I'm paying for.
In fact, here is an in-game screen-shot (from Dota 2) with some more, presumably non-IMCP requests.
As we can see, the ping from Miami to US East (Virginia) is already over 100ms. Lol. Further, I almost have a better connect to somewhere in Peru than Seattle. Mind you, we live in a developed country with a good internet backbone.
All I want is to talk to someone from ATT or Level3 that actually knows what ping means. I would at least like to know why this is happening and I bet there is an easy fix for this, too, if anyone actually cares enough to look into it.