Ever since the server move a few of us South Africans on Odin server have been experiencing weird bursts of lag, the game will run fun then pause for half a second or so then burst with speed.
i checked my resource monitor and i am running at 210ms, yet it feels otherwise.
this started since the server move.
Here's my pingplot pathing:
Target Name: N/A
IP: 195.82.50.47
Date/Time: 2015/10/21 05:02:22 PM to 2015/10/21 05:06:42 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 105 0 0.0 0 0 0 [192.168.0.1]
2 105 0 0.0 7 12 7 105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.3.129]
3 105 0 0.0 9 73 11 ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178.53]
4 105 2 1.9 9 35 12 rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 105 0 0.0 9 34 10 jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
6 105 0 0.0 9 75 13 qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 105 0 0.0 32 49 33 tb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.31.67]
8 105 2 1.9 185 190 186 [196.44.29.53]
9 105 2 1.9 191 265 197 caxtn-indust-1--jp-ad-1-a.mtnns.net [209.212.98.30]
10 105 0 0.0 172 230 175 [212.187.195.161]
11 67 56 83.6 196 198 196 ae-4-90.edge5.Frankfurt1.Level3.net [4.69.154.201]
12 60 56 93.3 196 197 196 ae-4-90.edge5.Frankfurt1.Level3.net [4.69.154.201]
13 105 17 16.2 187 189 188 KDDI-DEUTSC.edge5.Frankfurt1.Level3.net [212.162.4.98]
14 105 17 16.2 184 192 185 [195.82.60.29]
15 105 10 9.5 188 214 189 [195.82.61.14]
16 104 22 21.2 184 191 184 [195.82.50.234]
17 105 17 16.2 212 214 213 [195.82.50.47]
A little hard to follow since the formatting was lost, but looks like you are loosing packets before Frankfurt. Likely are also getting larger spikes too. Big spikes can also cause out of order delivery and trigger retransmits as well. So you may be getting tripped up be the TCP/IP protocol's error correction scheme kicking in...trying to get the packets delivered in proper order is basically causing the data stream to sort of pause, rewind a bit, and playback. It causes a lot of jerky rubberbanding like that.
Look into your ISP's support options to see if you can get this data to their tier3 support. They sometimes refer to it as an engineering department. Hopefully they have a forum or an email contact that you can just submit it through. They should be the first line of defense for clearing congested routing at that point in your route. It is their routing policies determining that pathing.