So for the last week or so I've been constantly getting anywhere between 117-135ms ping solid on any Valve EU servers (CS:GO/Dota 2) and following the tracerts I did they seem to confirm that this is infact the case. I play with another Virgin Media customer who geographically speaking is less than 35 miles from where I am yet his ping is what my one to the EU servers normally would be. I've seen quite a few threads on reddit about this particular issue with Virgin so I was hoping to be provided or be able to assist you to provide some sort of resolution to this rather irritating problem.
5 22 ms 11 ms 8 ms manc-bb-1c-ae2-0.network.virginmedia.net [18.104.22.168] 6 10 ms 11 ms 9 ms ae0.man11.ip4.gtt.net [22.214.171.124] 7 27 ms 39 ms 56 ms xe-3-0-1.fra61.ip4.gtt.net [126.96.36.199] 8 27 ms 25 ms 29 ms valve-gw.ip4.gtt.net [188.8.131.52] 9 * * * Request timed out. 10 143 ms 158 ms 141 ms 184.108.40.206
Friend on VM get almost identical routing from the MANC hop onwards yet his pings are normal so perhaps the hidden hop 9 is the issue at Valve's GTT end
Tracing route to lux.valve.net [220.127.116.11] over a maximum of 30 hops:
1 7 ms 7 ms 7 ms Alexander-PC [0.0.0.0] 2 7 ms 7 ms 7 ms uddi-core-2a-xe-031-0.network.virginmedia.net [18.104.22.168] 3 * * * Request timed out. 4 * * * Request timed out. 5 13 ms 17 ms 12 ms manc-bb-1c-ae1-0.network.virginmedia.net [22.214.171.124] 6 13 ms 13 ms 15 ms ae0.man11.ip4.gtt.net [126.96.36.199] 7 34 ms 33 ms 31 ms xe-2-2-0.fra61.ip4.gtt.net [188.8.131.52] 8 29 ms 33 ms 28 ms valve-gw.ip4.gtt.net [184.108.40.206] 9 * * * Request timed out. 10 * * * Request timed out. 11 136 ms 136 ms 135 ms 220.127.116.11
Looking at your traces I'm getting some deja vu! Thank you CTBlench for bringing this to our attention and Aggellos for all the IPs we can test to.
The last time I saw this it was an issue with GTT which they eventually sorted out but as CT mentions another of our users is getting totally normal results then there may be an issue with our routing we need to look into.
CTBLench, could you get your friend to post a traceroute on this thread for us to take a look at and compare?
I got this 2-3 days ago, new IP address only got this high ping on EU west servers. EU east is fine.
140-150 ping in game all day every day from 2 days ago?
looks like a routing issue again
I was on an 18.104.22.168 IP before now a 22.214.171.124
EU west :
Pinging 126.96.36.199 with 32 bytes of data: Reply from 188.8.131.52: bytes=32 time=170ms TTL=48 Reply from 184.108.40.206: bytes=32 time=216ms TTL=48 Reply from 220.127.116.11: bytes=32 time=179ms TTL=48 Reply from 18.104.22.168: bytes=32 time=184ms TTL=48
Ping statistics for 22.214.171.124: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 170ms, Maximum = 216ms, Average = 187ms
Tracing route to 126.96.36.199 over a maximum of 30 hops
1 5 ms <1 ms 1 ms routerlogin.net [192.168.0.1] 2 * * * Request timed out. 3 12 ms 8 ms 10 ms brad-core-2a-xe-002-0.network.virginmedia.net [188.8.131.52] 4 * * * Request timed out. 5 9 ms 8 ms 17 ms manc-bb-1c-ae2-0.network.virginmedia.net [184.108.40.206] 6 12 ms 8 ms 9 ms ae0.man11.ip4.gtt.net [220.127.116.11] 7 29 ms 26 ms 28 ms xe-8-0-0.fra61.ip4.gtt.net [18.104.22.168] 8 30 ms 38 ms 26 ms valve-gw.ip4.gtt.net [22.214.171.124] 9 * * * Request timed out. 10 205 ms 145 ms 192 ms 126.96.36.199
All on a wired connection
Eu East :
Pinging 188.8.131.52 with 32 bytes of data: Reply from 184.108.40.206: bytes=32 time=37ms TTL=52 Reply from 220.127.116.11: bytes=32 time=36ms TTL=52 Reply from 18.104.22.168: bytes=32 time=38ms TTL=52 Reply from 22.214.171.124: bytes=32 time=47ms TTL=52
Ping statistics for 126.96.36.199: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 36ms, Maximum = 47ms, Average = 39ms
Thanks for sending your stats and trace. So far, looking at the traces the poor link isn't gtt but either the end destination which is Valves server in luxembourg or hop 9 on yours and thestoos traces which doesn't respond to ping requests but might be where the high ping begins. Have any of you contacted Steam support in case there is an issue with their server that might be causing this?