50M : Bad pings on some game servers (usually 20-30 ping, in the 100's)

[Simcut]

Hi there

I'm an active gamer and for some reason a number of servers are pinging at around the 100-110 ping mark, where normally they'd be like 20-30.

Here's an example of one of the trace routes I've done.

tracert 188.165.225.144

Tracing route to ks312869.kimsufi.com [188.165.225.144]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 6 ms 7 ms cpc2-ware5-2-0-gw.9-1.cable.virginmedia.com [82.
1.196.1]
3 66 ms 7 ms 7 ms lutn-core-2a-ae5-1226.network.virginmedia.net [8
0.4.221.1]
4 7 ms 7 ms 8 ms popl-bb-1c-ae2-0.network.virginmedia.net [62.253
.174.1]
5 8 ms 7 ms 7 ms popl-bb-1b-ae13-0.network.virginmedia.net [213.1
05.159.189]
6 7 ms 7 ms 7 ms tele-ic-5-ae0-0.network.virginmedia.net [213.105
.159.117]
7 * * * Request timed out.
8 91 ms * 91 ms nwk-2-6k.nj.us [178.32.135.232]
9 462 ms 222 ms * ldn-5-6.uk.eu [178.32.135.231]
10 95 ms 94 ms 95 ms rbx-g2-a9.fr.eu [91.121.131.177]
11 96 ms 93 ms 95 ms vss-3-6k.fr.eu [213.251.130.77]
12 95 ms 95 ms 95 ms ks312869.kimsufi.com [188.165.225.144]

that IP belongs to a match server I normally use, everyone else's ping is fine, and the traceroute seems to show that it bounces from the UK to America?! (nj.us must mean new jersey?) and then back to uk, then france :| very odd

To show that it's not an issue for all servers I use, here's a traceroute to a UK server that I use.

tracert 193.33.187.131

Tracing route to 193.33.187.131 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms cpc2-ware5-2-0-gw.9-1.cable.virginmedia.com [82.
1.196.1]
3 11 ms 10 ms 11 ms lutn-core-2b-ae5-1226.network.virginmedia.net [8
0.4.221.129]
4 31 ms 8 ms 7 ms nrth-bb-1b-ae9-0.network.virginmedia.net [62.253
.174.5]
5 8 ms 7 ms 7 ms popl-bb-1a-as3-0.network.virginmedia.net [213.10
5.172.14]
6 8 ms 7 ms 7 ms popl-bb-1b-ae0-0.network.virginmedia.net [213.10
5.174.230]
7 9 ms 7 ms 7 ms tele-ic-5-ae0-0.network.virginmedia.net [213.105
.159.117]
8 10 ms 7 ms 11 ms 62.253.174.70
9 15 ms 12 ms 14 ms racksrv-162.gw.goscomb.net [46.17.60.162]
10 10 ms 11 ms 11 ms 193.33.187.131

Trace complete.

If you need more details from me please ask.

Regards

[qasdfdsaq]

Yes, it looks like Virgin Media's routing to OVH (in France) is very broken right now, it should be transiting via London, not the US.

You are correct though in that right now, it appears to be going London => New Jersey => France. Based on reverse traces there seems to be something wrong in VM's Poplar datacentre.

[iain_herts]

this part of ur tracert is the OVH london to USA network

8 91 ms * 91 ms nwk-2-6k.nj.us [178.32.135.232]
9 462 ms 222 ms * ldn-5-6.uk.eu [178.32.135.231]

as seen here

http://weathermap.ovh.net/backbone

i would say there is a OVH routing isse not 100% sure you could try and post over on there uk site

http://forum.ovh.co.uk/

[qasdfdsaq]

No, the routing issue is on VM's end. The forward path (VM to OVH) is incorrectly going to the US. The reverse path (OVH to VM) is correctly going directly to London.

That would suggest OVH is correctly sending data to VM directly, but VM is sending data to OVH via the US.

[Simcut]

What's the next course of action? I dont wanna ring up Virgin about this, would rather email them/post it somewhere to make them aware..

[qasdfdsaq]

Things like this often fix themselves after a little while as most routing protocols are largely automatic. If you do want to report it to them, best place to do so is via the VM community forums.

[Simcut]

Thanks for the replies btw guys. I'm pleased to say this problem has now gone (at least for me it has)