When I had this issue on Saturday, where my ping just went sky high and everything around me just froze, I started at one occasion wireshark recording up prior to an engagement, which also ended up in a freeze...

The IPs connected to for the EU servers are
159.100.232.107 and 159.100.232.116
which is part of their whole range for EU it appears (159.100.224.0/20)

One thing I've noticed are a few TCP DUP ACK throughout the 32 second capture, notably in the last 4 seconds it occured more often than over previous time periods, ending in an TCP RST, after which it became quieter until I hit alt+f4 ingame 12 seconds later.

My traceroute for 159.100.232.107 at this moment (don't have a traceroute from Saturday) is

traceroute to 159.100.232.107 (159.100.232.107), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 0.575 ms 1.000 ms 1.311 ms
2 cpc3-tilb8-2-0-gw.basl.cable.virginm.net (77.101.113.1) 12.628 ms 12.816 ms 13.080 ms
3 basl-core-2a-ae11-613.network.virginmedia.net (81.96.1.73) 11.092 ms 12.156 ms 12.420 ms
4 brnt-bb-1a-ae10-0.network.virginmedia.net (81.96.0.145) 27.968 ms 26.957 ms 28.196 ms
5 * * *
6 popl-bb-1b-ae4-0.network.virginmedia.net (62.252.2.110) 19.670 ms 12.386 ms 52.615 ms
7 m674-mp2.cvx1-b.lis.dial.ntli.net (62.254.42.162) 15.835 ms 21.121 ms 21.282 ms
8 193.159.224.57 (193.159.224.57) 20.092 ms 80.150.170.5 (80.150.170.5) 19.628 ms 19.914 ms
9 217.239.44.46 (217.239.44.46) 104.336 ms 111.324 ms 112.286 ms
10 193.159.226.18 (193.159.226.18) 113.348 ms 113.758 ms 113.569 ms
11 ns99.rookdns.com (195.122.154.4) 116.156 ms 115.992 ms ns99.rookdns.com (195.122.154.3) 115.816 ms
12 159.100.232.107 (159.100.232.107) 99.115 ms 99.695 ms 102.823 ms

and the one ending with 116 is:

traceroute to 159.100.232.116 (159.100.232.116), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 0.936 ms 1.350 ms 1.661 ms
2 cpc3-tilb8-2-0-gw.basl.cable.virginm.net (77.101.113.1) 10.377 ms 11.214 ms 28.032 ms
3 basl-core-2b-ae11-710.network.virginmedia.net (81.96.1.217) 16.959 ms 17.947 ms 18.185 ms
4 popl-bb-1b-ae11-0.network.virginmedia.net (81.96.0.149) 19.124 ms 19.287 ms 19.425 ms
5 m674-mp2.cvx1-b.lis.dial.ntli.net (62.254.42.162) 24.790 ms 25.753 ms 25.989 ms
6 80.150.170.5 (80.150.170.5) 29.327 ms 193.159.224.57 (193.159.224.57) 17.950 ms 16.456 ms
7 217.239.44.22 (217.239.44.22) 89.590 ms 90.549 ms 94.136 ms
8 193.159.226.18 (193.159.226.18) 95.573 ms 95.834 ms 95.971 ms
9 ns99.rookdns.com (195.122.154.3) 97.132 ms 96.917 ms ns99.rookdns.com (195.122.154.4) 96.678 ms
10 159.100.232.116 (159.100.232.116) 96.065 ms 96.201 ms 96.337 ms

I've posted several this evening in the other thread, this one is typical:

Just had another couple of minutes with two DCs and other crap, again this isn't our end it's well on the way to ZOS:

First is a good one ...

c:\ >tracert 159.100.230.103

Tracing route to 159.100.230.103 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.250
2 6 ms 7 ms 5 ms 10.93.144.1
3 8 ms 7 ms 7 ms bagu-core-2b-xe-132-0.network.virginmedia.net [80.5.167.253]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 17 ms 14 ms 13 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254.42.90]
9 14 ms 15 ms 19 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
10 14 ms 13 ms 13 ms 80.150.170.5
11 29 ms 29 ms 29 ms 217.239.44.62
12 30 ms 30 ms 29 ms 193.159.226.18
13 30 ms 30 ms 29 ms ns99.rookdns.com [195.122.154.4]
14 31 ms 30 ms 30 ms 159.100.230.103

Trace complete.

this is when it was pear-shaped ...

c:\ >tracert 159.100.230.103

Tracing route to 159.100.230.103 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.250
2 6 ms 8 ms 6 ms 10.93.144.1
3 7 ms 7 ms 7 ms bagu-core-2b-xe-132-0.network.virginmedia.net [80.5.167.253]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 27 ms 13 ms 23 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254.42.90]
9 13 ms 13 ms 13 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
10 16 ms 13 ms 13 ms 80.150.170.5
11 28 ms 29 ms 29 ms 217.239.44.62
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * 450 ms * 159.100.230.103
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 31 ms 33 ms 33 ms 159.100.230.103

Trace complete.

Note that other traces shows the route for the section after hop 11 is the same as ... in comparison my BT connection ends up ...

C:\>tracert 159.100.230.103

Tracing route to 159.100.230.103 over a maximum of 30 hops

12 27 ms 27 ms 27 ms 217.239.45.198
13 27 ms 27 ms 27 ms 193.159.226.18
14 27 ms 26 ms 27 ms ns99.rookdns.com [195.122.154.3]
15 26 ms 26 ms 26 ms 159.100.230.103

Trace complete.


The very interesting thing is that both Virgin Media and BT are routing through the 193.159.226.18 hop yet the VM packets are dropping on the floor while BT's go through: both tracerts are being done at the same time, I have both VM and BT connections available to me concurrently.

I've trapped three such events this evening over a 2+ hour period, they last around 1 min each time then VM's packets get through again normally.

I started having horrid latency after the 1.6 patch. I thought maybe it was just a broken addon, but I've disabled all addons and the same thing keeps happening. I'll open the game with a decent latency (I'm in Asia so I don't expect perfection) averaging 200 - 300. This is what I used to get before 1.6 but now after about 20 min of that, it jumps into the 800 - 900 range and after about 30 min of playing I'll get up into the 1200 - 1500 range. After another 10 min I'll see spikes over 5000 and the game will boot me.

I've tried DNS flushes, restarting the router & modem, I've run traces and used the client test utility and I've not seen anything that would suggest a problem on my end. I can post traces and test reports later (not at my house right now) but I'm just curious if anyone else is still having issues?

I play on the NA server.