I currently have both BT and VM connections, so I can compare the hardware directly. I was hoping to switch to VM, but at this rate I might just cancel within my cooling off period because the latencies are unreasonably high on Virgin Media.
Tested with the same machine:
Average ping to Steam (BT): 69ms
Average ping to Steam (VM): 134ms
Average ping to Google (BT): 73ms
Average ping to Google (VM): 137ms
These measurements are at off peak times. I was hoping for an improvement given higher bandwidth on VM, but for gaming this is going to be a massive downgrade over BT Infinity given that latencies are nearly 2x higher.
If you are on a superhub3 you will be getting increased latency anyway due to an issue with the puma chip it has. Ironically the gamer package makes your connection worse for gaming currently.
~~~~~~~~~~~~~~~~~~~~~~~~~ All posts made are personal opinions as I do not work for VirginMedia. Kudo's a post if you find it useful and want to say thanks Mark a post as a helpful answer if it answers your question
I can understand that the chipset issue is affecting the LAN times dramatically (3.2ms instead of 0.2ms, 16x slower than it should be), but it is not at all clear that the same problem would be adding an extra 60ms to internet ping times.
Traceroute says: 1 gateway (192.168.0.1) 2.203 ms 3.869 ms 4.479 ms 2 * * * 3 glfd-core-2a-xe-021-0.network.virginmedia.net (22.214.171.124) 27.667 ms 28.019 ms 28.240 ms 4 * * * 5 * * * 6 * * * 7 eislou2-ic-1-ae3-0.network.virginmedia.net (126.96.36.199) 55.676 ms 56.055 ms 56.656 ms 8 188.8.131.52 (184.108.40.206) 40.747 ms m350-mp2.cvx3-a.ltn.dial.ntli.net (220.127.116.11) 28.113 ms 18.104.22.168 (22.214.171.124) 28.792 ms 9 126.96.36.199 (188.8.131.52) 41.980 ms 184.108.40.206 (220.127.116.11) 31.320 ms 18.104.22.168 (22.214.171.124) 30.612 ms 10 126.96.36.199 (188.8.131.52) 33.568 ms 184.108.40.206 (220.127.116.11) 34.894 ms 18.104.22.168 (22.214.171.124) 30.947 ms 11 google-public-dns-a.google.com (126.96.36.199) 34.388 ms 32.548 ms 37.437 ms
So at the very least 2/3 of the increase in ping times is happening _beyond_ the 3rd hop. This is nothing to do with the SH3. That may be adding 3ms to the ping times, but the network infrastructure behind it is adding another 60ms compared to BT Infinity.
Looks like there is congestion on part of the network where you are. I am currently getting an average ping of 15ms to google DNS:
Tracing route to google-public-dns-a.google.com [188.8.131.52] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms unknown [192.168.1.1] 2 7 ms 8 ms 7 ms 10.238.20.1 3 8 ms 18 ms 7 ms perr-core-2a-xe-303-0.network.virginmedia.net [184.108.40.206] 4 * * * Request timed out. 5 * * * Request timed out. 6 19 ms 16 ms 15 ms tcl5-ic-4-ae5-0.network.virginmedia.net [220.127.116.11] 7 17 ms 16 ms 22 ms 246-14-250-212.static.virginm.net [18.104.22.168] 8 18 ms 17 ms 19 ms 22.214.171.124 9 23 ms 17 ms 17 ms 126.96.36.199 10 16 ms 16 ms 17 ms google-public-dns-a.google.com [188.8.131.52]
Get on the blower to tech support (0333 000 3101) and ask to speak to 2nd line tech support so they can liaise with networks. You will likely go over your cooling off period waiting for a reply from a member of staff here.