Xilo lagging - anyone else?

I regularly game on a French UT2k4 mod server (178.32.80.189) but for a while now it's completely gone to pot at peak times. Nobody else on it has any problems, it's obviously my connection (tracert would confirm that too). Looks to be a peering issue.

Anyone else on Xilo Pro 24/Tiscali seeing increases in latency/packet loss? Especially over the channel? Might have to start looking for a new ISP if it continues, which is a pain as my options are severely limited.

Edited by deleted (Tue 07-Jun-11 21:54:13)

Not on Xilo, but similar issues being seen by people on BE

Can you post a tracert please?

Interesting. Pings seem to be all over the place, one second 30, the next 140, with loads of packet loss. The router showing the latency seems to change a lot too. Sometimes it's the first one after murphx.net but obviously not this time. Very strange.

Tracing route to 178.32.80.189 over a maximum of 30 hops

1 1 ms <1 ms <1 ms snip [###.###.#.###]
2 13 ms 12 ms 12 ms lns1.uan.thn.uk.murphx.net [89.145.254.69]
3 12 ms 12 ms 12 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 20 ms 13 ms 13 ms ge2-6-1.cr1.core.thn.uk.murphx.net [89.145.254.1
61]
5 48 ms 58 ms 57 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
6 58 ms 214 ms 18 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
7 21 ms * 21 ms ldn-1-6k.uk.eu [94.23.122.125]
8 21 ms 21 ms 21 ms rbx-g1-a9.fr.eu [94.23.122.66]
9 22 ms * 21 ms vss-2-6k.fr.eu [94.23.122.173]
10 111 ms 112 ms 113 ms 178.32.80.189

Edited by deleted (Tue 07-Jun-11 22:04:08)

This is a problem with OVH.

They often have saturated links and all issues start within their network - if you're their customer, you'll have to give them a nudge i'm afraid.

Common problem being seen by other ISPs too

Matt

Right, so it's a peering problem and the only way I can fix it is by moving?

Here's one showing Murphx lagging too. I realise ping isn't the most reliable metric but it shows how close to breaking point the network is running.

Tracing route to 178.32.80.189 over a maximum of 30 hops

1 1 ms <1 ms <1 ms snip [###.###.#.###]
2 12 ms 12 ms 12 ms lns1.uan.thn.uk.murphx.net [89.145.254.69]
3 13 ms 12 ms 12 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 93 ms 203 ms 199 ms ge2-6-1.cr1.core.thn.uk.murphx.net [89.145.254.1
61]
5 13 ms 12 ms 13 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
6 34 ms 12 ms 13 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
7 20 ms 20 ms * ldn-1-6k.uk.eu [94.23.122.125]
8 21 ms 21 ms 20 ms rbx-g1-a9.fr.eu [94.23.122.66]
9 27 ms * 20 ms vss-2-6k.fr.eu [94.23.122.173]
10 31 ms 30 ms 30 ms 178.32.80.189

Edited by deleted (Tue 07-Jun-11 22:10:16)

No, it is not a peering problem. It is a problem with their network (from what we have seen from various posts, over various ISPs, their Linx capacity may be the issue).

As I said, other ISPs are seeing the same problem too and are likely to peer over Linx, as such, the issue won't be any different.

Matt

Look at the packet loss, that is far more important that the odd high ping.

Matt

OK. That's too bad. Wouldn't explain my last tracert though, I'd have thought.

Let me give you another example...

Text

1 23 45 67 89 10

root@xx [~]# traceroute 178.32.80.189 traceroute to 178.32.80.189 (178.32.80.189), 30 hops max, 40 byte packets 1  91.199.78.252.ip.static.xcl.net.uk (91.199.78.252)  2.199 ms  3.238 ms  3.208 ms  2  vl667.hex-7600.as29550.net (92.48.95.9)  3.188 ms  3.156 ms  3.126 ms 3  xe-1-2-0.lon21.ip4.tinet.net (77.67.67.137)  3.073 ms  3.047 ms  3.009 ms  4  xe-1-0-0.lon14.ip4.tinet.net (89.149.183.166)  2.978 ms xe-0-0-0.lon14.ip4.tinet.net (89.149.183.162)  34.097 ms xe-1-0-0.lon14.ip4.tinet.net (89.149.183.166)  2.901 ms 5  213.200.77.234 (213.200.77.234)  4.707 ms  5.689 ms  5.656 ms  6  ldn-1-6k.uk.eu (94.23.122.125)  19.085 ms * ldn-1-6k.uk.eu (94.23.122.125)  17.843 ms 7  rbx-g1-a9.fr.eu (213.251.130.73)  14.172 ms  14.521 ms  14.788 ms  8  vss-2-6k.fr.eu (94.23.122.173)  220.993 ms * vss-2-6k.fr.eu (94.23.122.173)  221.692 m

Still see the losses in their network over a completely different path (not Linx).

Matt

Edited by uno (Tue 07-Jun-11 22:13:35)

Packet loss is certainly bad but a 140 ping isn't too nice either. I understand it's down to a third-party. Must be frustrating for you too. I am getting lag inside the Murphx network though.

I wouldn't be so annoyed if it wasn't the only server this side of the Atlantic running my game of choice. >.<

Edited by deleted (Tue 07-Jun-11 22:17:51)

There have been different reports of high latency on BE over the last week or two

The issue reported today is with latency to WoW servers

195.12.240.165
195.12.234.175

Routing via Telia

Common factor could be LINX, but possibly an unconneccted issue

From BT Broadband

C:\Users\Satta>ping 178.32.80.189

Pinging 178.32.80.189 with 32 bytes of data:
Reply from 178.32.80.189: bytes=32 time=18ms TTL=52
Reply from 178.32.80.189: bytes=32 time=17ms TTL=52
Reply from 178.32.80.189: bytes=32 time=17ms TTL=52
Reply from 178.32.80.189: bytes=32 time=17ms TTL=52

Ping statistics for 178.32.80.189:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 18ms, Average = 17ms


C:\Users\Satta>pathping 178.32.80.189

Tracing route to 178.32.80.189 over a maximum of 30 hops

0 Chalwa [192.168.1.67]
1 api.home [192.168.1.254]
2 217.47.71.58
3 217.47.71.161
4 213.1.69.134
5 217.32.24.234
6 217.32.24.74
7 217.32.24.182
8 109.159.249.232
9 core2-te0-0-0-2.ealing.ukcore.bt.net [109.159.249.155]
10 core2-pos5-0-0.telehouse.ukcore.bt.net [194.74.65.126]
11 195.66.226.220
12 rbx-g1-a9.fr.eu [94.23.122.66]
13 vss-2-6k.fr.eu [94.23.122.173]
14 178.32.80.189

Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Chalwa [192.168.1.67]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% api.home [192.168.1.254]
0/ 100 = 0% |
2 18ms 0/ 100 = 0% 0/ 100 = 0% 217.47.71.58
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 217.47.71.161
0/ 100 = 0% |
4 21ms 1/ 100 = 1% 1/ 100 = 1% 213.1.69.134
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% 217.32.24.234
0/ 100 = 0% |
6 20ms 0/ 100 = 0% 0/ 100 = 0% 217.32.24.74
0/ 100 = 0% |
7 19ms 0/ 100 = 0% 0/ 100 = 0% 217.32.24.182
0/ 100 = 0% |
8 17ms 0/ 100 = 0% 0/ 100 = 0% 109.159.249.232
0/ 100 = 0% |
9 24ms 22/ 100 = 22% 22/ 100 = 22% core2-te0-0-0-2.ealing.ukcore.bt.n
et [109.159.249.155]
0/ 100 = 0% |
10 20ms 17/ 100 = 17% 17/ 100 = 17% core2-pos5-0-0.telehouse.ukcore.bt
.net [194.74.65.126]
0/ 100 = 0% |
11 27ms 0/ 100 = 0% 0/ 100 = 0% 195.66.226.220
0/ 100 = 0% |
12 25ms 0/ 100 = 0% 0/ 100 = 0% rbx-g1-a9.fr.eu [94.23.122.66]
0/ 100 = 0% |
13 27ms 0/ 100 = 0% 0/ 100 = 0% vss-2-6k.fr.eu [94.23.122.173]
1/ 100 = 1% |
14 23ms 1/ 100 = 1% 0/ 100 = 0% 178.32.80.189

Trace complete.

C:\Users\Satta>

Edited by deleted (Wed 08-Jun-11 21:45:44)

IDNet, interleaved.

C:\Users\Bob>tracert 178.32.80.189

Tracing route to 178.32.80.189 over a maximum of 30 hops

  1     3 ms     1 ms    <1 ms  192.168.11.1
  2    13 ms    12 ms    13 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    13 ms    14 ms    13 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4    13 ms    12 ms    12 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  5    13 ms     *       16 ms  sw1.tc.lon.ovh.net [195.66.224.220]
  6    16 ms    18 ms    16 ms  rbx-g2-a9.fr.eu [91.121.131.181]
  7    18 ms     *        *     vss-2-6k.fr.eu [91.121.131.89]
  8    16 ms    16 ms    16 ms  178.32.80.189

Trace complete.

Thought I'd mention, it's been fine for the last couple of nights. Fingers crossed.