Recent LAG / Packet Loss from Networklayer.com
" It seems like it. Its too bad though really not fun playing the game with a ping of 350-500ms Dernière édition par DarkRaiderZA#1408, le 1 oct. 2013 à 12:28:58
|
![]() |
I can deal with the 350-500 ms (I like playing summoners go figure) but the random packet-loss that lags out and kills my character is another thing entirely...
Its just annoying because all my other online games have zero issues, so these lag issues are specific to only PoE. |
![]() |
" http://en.wikipedia.org/wiki/Internet_exchange_point |
![]() |
" I don't really get what you mean, I don't have any expertise in networking at all. What is the relevance of this to my problem? |
![]() |
" It was to explain a little bit about how the internet works. How routes are used, and why "other games" might work... because they could very well (and probably do) take a completely different route. Just because "something else" doesn't have connection problems, doesn't immediately place the problem on the game servers or PoE network... that's not how the internet works. Even WITHIN your ISP, different destinations go through different segments of their internal network. One of those could have issues while the rest don't. That's why we ask for traces and things so we can identify if there is a problem, and if so where the problem resides. Sometimes it is things that GGG can get involved in fixing (networklayer issues), and often times, it is a problem with the ISP. In some cases, there have been a few routing issues within NetworkLayer in Amsterdam. Those are being looked into/resolved as quickly as possible. In other cases, we have to refer people to their ISP since it is an ISP or carrier problem. I was just hoping to enlighten you a little on how the internet works with routing so you can further refrain from ever using phrases such as "other online games have zero issues" when it comes to the internet. |
![]() |
" Thanks for the explanation, that was much more helpful than just your earlier link. Dernière édition par Angryafrican#1756, le 1 oct. 2013 à 17:09:07
|
![]() |
Hi,
I work MTN Business in SA and can confirm that there are still problems. The problem seems to be on the NetworkLayer.com network. Since you peer with them, can you please ask them to investigate the problem. One router in particular. Notice in all the traceroutes that the below router(IP) from NetworkLayer has high latency. bbr01.lon01.networklayer.com 195.66.225.183 We don't peer with NetworkLayer but will ask our peers to ask NetworkLayer to investigate. ------------------ From Customer:- hop 7 high latency Traceroute:: 208.43.68.142-static.reverse.softlayer.com [208.43.68.142] 1 1 ms <1 ms <1 ms UNIXSERV9 2 10 ms 9 ms 9 ms 105-236-xxxxx-esr-lo.mtnbusiness.co.za [105.236.xxxxx] 3 12 ms 11 ms 12 ms ipc-xxxx-rb-3a.za.mtnbusiness.net [41.181.xxxxx] 4 12 ms 12 ms 12 ms rb-xxxxxx.za--rb-cr-1.za-a.mtnns.net [196.44.xxxxx] 5 12 ms 12 ms 13 ms jh-xxxxxx.za--rb-cr-2.za.mtnns.net [196.44.xxxx] 6 13 ms 12 ms 12 ms qux-jh-xxxxxxx.za-b.za.mtnbusiness.net [41.181.xxxxxx] 7 333 ms 332 ms 331 ms bbr01.lon01.networklayer.com [195.66.225.183] 8 329 ms 329 ms 329 ms ae1.bbr02.tl01.nyc01.networklayer.com [50.97.18.204] 9 331 ms 330 ms 330 ms ae7.bbr01.tl01.nyc01.networklayer.com [173.192.18.176] 10 345 ms 343 ms 342 ms ae1.bbr01.eq01.wdc02.networklayer.com [173.192.18.156] 11 345 ms 345 ms 345 ms ae0.dar01.sr01.wdc01.networklayer.com [173.192.18.197] 12 330 ms 331 ms 414 ms po1.fcr01.sr01.wdc01.networklayer.com [208.43.118.134] 13 344 ms 345 ms 343 ms 208.43.68.142-static.reverse.softlayer.com [208.43.68.142] From MTN network:- hop 6 high latency. hops 3-4 is SA to UK(avg. 140+ms which is normal) traceroute 208.43.68.142-static.reverse.softlayer.com. traceroute to 208.43.68.142-static.reverse.softlayer.com (208.43.68.142), 64 hops max, 52 byte packets 1 fe2-0-1.xxxxxxxx.za.mtnbusiness.net (196.30.xxxxxx) 0.616 ms 1.005 ms 0.494 ms 2 196.7.xxxxxx (196.7.xxxxx) 0.423 ms 0.454 ms 0.406 ms 3 tb-xxxx.za--tb-xxxx.za-a.mtn.net (196.44.xxxxxx) 1.908 ms 1.354 ms 1.430 ms 4 ls-xxxx--tb-xxxx.uk-b.mtnns.net (196.44.xxxxxx) 144.992 ms 144.991 ms 147.630 ms 5 ls-xxxx.uk--ls-xxxx.uk-a.mtn.net (209.212.xxxxxxx) 144.830 ms 144.831 ms 144.868 ms 6 bbr01.lon01.networklayer.com (195.66.225.183) 281.317 ms 281.367 ms 281.601 ms 7 ae1.bbr02.tl01.nyc01.networklayer.com (50.97.18.204) 281.326 ms 282.472 ms 281.280 ms 8 ae7.bbr01.tl01.nyc01.networklayer.com (173.192.18.176) 278.910 ms 282.910 ms 279.121 ms 9 ae1.bbr01.eq01.wdc02.networklayer.com (173.192.18.156) 278.450 ms 278.814 ms 278.075 ms 10 ae0.dar02.sr01.wdc01.networklayer.com (173.192.18.203) 278.831 ms ae0.dar01.sr01.wdc01.networklayer.com (173.192.18.197) 278.514 ms ae0.dar02.sr01.wdc01.networklayer.com (173.192.18.203) 279.006 ms 11 po2.fcr01.sr01.wdc01.networklayer.com (208.43.118.138) 279.690 ms 280.196 ms 280.604 ms 12 * * * ---------------------- EU IP from customer:- hop 7 high latency Traceroute:: 5.153.24.242-static.reverse.softlayer.com [5.153.24.242] 1 <1 ms <1 ms <1 ms UNIXSERV9 2 10 ms 12 ms 9 ms 105-236-xxxxx-esr-lo.mtnbusiness.co.za [105.236.xxxxx] 3 12 ms 12 ms 12 ms ipc-xxxxxxxxx-4a.za.mtnbusiness.net [41.181.xxxxx] 4 12 ms 14 ms 12 ms rb-xxxxx.za--rb-xxxx.za-a.mtnns.net [196.44.xxxxxx] 5 13 ms 13 ms 12 ms jh-xxxx.za--rb-xxxx.za.mtnns.net [196.44.xxxx] 6 13 ms 12 ms 12 ms qux-jh-xxxxx.za-b.za.mtnbusiness.net [41.181.xxxxxxx] 7 332 ms 332 ms 331 ms bbr01.lon01.networklayer.com [195.66.225.183] 8 333 ms 333 ms 332 ms ae7.bbr02.tg01.lon01.networklayer.com [50.97.18.207] 9 351 ms 389 ms 402 ms ae0.bbr02.eq01.ams02.networklayer.com [50.97.18.211] 10 434 ms 348 ms 333 ms ae6.dar02.sr01.ams01.networklayer.com [50.97.18.251] 11 333 ms 337 ms 333 ms po2.fcr01.sr01.ams01.networklayer.com [159.253.158.133] 12 348 ms 348 ms 349 ms 5.153.24.242-static.reverse.softlayer.com [5.153.24.242] EU IP from MTN Network:- hop 6 high latency. hops 3-4 is SA to UK(avg. 140+ms which is normal) traceroute 5.153.24.255 traceroute to 5.153.24.255 (5.153.24.255), 64 hops max, 52 byte packets 1 fe5-0-0.xxxxxx.za.mtnbusiness.net (196.30.xxxxx) 0.551 ms 0.403 ms 0.491 ms 2 196.7.xxxxx (196.7.xxxxx) 0.805 ms 0.424 ms 0.401 ms 3 tb-xxxx.za--tb-xxxx.za-a.mtn.net (196.44.xxxxxx) 1.382 ms 1.365 ms 1.292 ms 4 ls-xxxx--tb-xxxx.uk-b.mtnns.net (196.44.xxxxxx) 144.986 ms 145.007 ms 176.596 ms 5 ls-xxxx.uk--ls-xxxx.uk-a.mtn.net (209.212.xxxxxxx) 144.812 ms 144.781 ms 144.820 ms 6 bbr01.lon01.networklayer.com (195.66.225.183) 281.956 ms 281.210 ms 281.140 ms 7 ae7.bbr02.tg01.lon01.networklayer.com (50.97.18.207) 287.164 ms 289.063 ms 287.624 ms 8 ae0.bbr02.eq01.ams02.networklayer.com (50.97.18.211) 298.163 ms 293.189 ms 289.688 ms 9 ae6.dar01.sr01.ams01.networklayer.com (50.97.18.249) 289.748 ms ae6.dar02.sr01.ams01.networklayer.com (50.97.18.251) 295.681 ms ae6.dar01.sr01.ams01.networklayer.com (50.97.18.249) 293.375 ms 10 * * * 11 *^C |
![]() |
I got the same problem.
Seems to start at Level 3 in Amsterdam which is like 40 miles away. 200 msec is enough to cross the Atlantic twice. Get your shit together Level 3. Upgrade your spying equipment or something. (Perhaps one of the major internet providers (NSA) have a routing issue or something.) Tracing route to www.pathofexile.com [173.192.44.22] over a maximum of 30 hops: 1 2 ms 3 ms 2 ms mijnmodem.kpn.lan [192.168.2.254] 2 28 ms 29 ms 29 ms 195.190.228.7 3 39 ms 37 ms 34 ms nl-zl-dc2-git-cr02.kpn.net [213.75.64.237] 4 43 ms 36 ms 34 ms nl-rt-dc2-ice-ir02.kpn.net [213.75.64.236] 5 48 ms 41 ms 36 ms nl-rt-dc2-ice-ir02.wxs.nl [213.75.64.166] 6 * 34 ms 33 ms rt2-rou-1022.NL.eurorings.net [134.222.93.140] 7 33 ms 33 ms 33 ms asd2-rou-1043.NL.eurorings.net [134.222.199.105] 8 33 ms 34 ms 33 ms ae9.edge3.Amsterdam1.level3.net [213.244.164.205] 9 * 210 ms 210 ms ae-52-52.csw2.Amsterdam1.Level3.net [4.69.139.185] 10 205 ms 209 ms 215 ms ae-56-221.ebr2.Amsterdam1.Level3.net [4.69.153.201] 11 212 ms 213 ms 215 ms ae-48-48.ebr2.London1.Level3.net [4.69.143.82] 12 213 ms 212 ms 209 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78] 13 205 ms 209 ms 212 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74] 14 216 ms 210 ms 210 ms ae-3-80.edge3.NewYork1.Level3.net [4.69.155.145] 15 126 ms 111 ms 111 ms te2-5.bbr01.tl01.nyc01.networklayer.com [4.26.34.22] 16 163 ms 153 ms 153 ms ae1.bbr01.eq01.chi01.networklayer.com [173.192.18.132] 17 170 ms 175 ms 178 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.18.136] 18 176 ms 175 ms 174 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.18.211] 19 160 ms 157 ms 157 ms po1.fcr05.sr06.dal01.networklayer.com [66.228.118.221] 20 178 ms 175 ms 173 ms 173.192.44.22-static.reverse.softlayer.com [173.192.44.22] Trace complete. |
![]() |
same here, since last patch
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 5978 | 5978 | 0 | 0 | 2 | 0 | | 10.4.96.1 - 0 | 5979 | 5979 | 0 | 8 | 173 | 2 | | 81.200.9.242 - 0 | 5979 | 5979 | 0 | 1 | 69 | 1 | | bb-m9.westcall.ru - 3 | 5424 | 5284 | 1 | 1 | 19 | 2 | | 79.104.17.229 - 3 | 5428 | 5289 | 1 | 1 | 29 | 1 | | No response from host - 100 | 1196 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 1196 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 1196 | 0 | 0 | 0 | 0 | 0 | | ae5.dar02.sr01.ams01.networklayer.com - 3 | 5464 | 5334 | 49 | 54 | 134 | 49 | | po2.fcr01.sr01.ams01.networklayer.com - 4 | 5184 | 4984 | 44 | 50 | 497 | 45 | | 37.58.89.2-static.reverse.softlayer.com - 3 | 5520 | 5404 | 44 | 49 | 103 | 45 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
![]() |
Same problems here, just suddenly had massive ping/packetloss at 1:41 UTC during 3rd 12min burst race. From Lithuania.
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.254 - 0 | 260 | 260 | 0 | 0 | 11 | 0 | | No response from host - 100 | 52 | 0 | 0 | 0 | 0 | 0 | | 82-135-180-4.static.zebra.lt - 0 | 260 | 260 | 1 | 4 | 69 | 2 | | bbr01.eq01.ams01.networklayer.com - 35 | 108 | 71 | 0 | 116 | 120 | 117 | | ae1.bbr02.eq01.wdc02.networklayer.com - 11 | 185 | 166 | 0 | 196 | 220 | 196 | | ae7.bbr01.eq01.wdc02.networklayer.com - 10 | 189 | 171 | 195 | 203 | 255 | 199 | | ae0.bbr01.tl01.atl01.networklayer.com - 21 | 143 | 114 | 206 | 212 | 219 | 214 | | ae13.bbr02.eq01.dal03.networklayer.com - 11 | 185 | 166 | 222 | 228 | 267 | 227 | | ae1.dar02.sr01.dal01.networklayer.com - 12 | 177 | 156 | 225 | 231 | 243 | 230 | | po2.fcr05.sr06.dal01.networklayer.com - 11 | 181 | 162 | 223 | 229 | 252 | 230 | |173.192.44.22-static.reverse.softlayer.com - 12 | 177 | 156 | 226 | 230 | 236 | 230 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider Ign: Zel, Zelg Dernière édition par zelgadas#2174, le 23 nov. 2013 à 10:41:53
|
![]() |