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.