Recent LAG / Packet Loss from Networklayer.com

Same here! EU gateway.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| - 0 | 44 | 44 | 0 | 0 | 0 | 0 |
| - 0 | 44 | 44 | 1 | 1 | 2 | 2 |
| - 3 | 40 | 39 | 1 | 2 | 31 | 31 |
| ************************ - 0 | 44 | 44 | 2 | 5 | 24 | 4 |
| ************************ - 0 | 44 | 44 | 44 | 44 | 47 | 45 |
| bbr01.lon01.networklayer.com - 0 | 44 | 44 | 44 | 45 | 53 | 45 |
| ae7.bbr02.tg01.lon01.networklayer.com - 0 | 44 | 44 | 44 | 45 | 52 | 45 |
| ae0.bbr02.eq01.ams02.networklayer.com - 3 | 40 | 39 | 123 | 135 | 140 | 140 |
| ae7.bbr01.eq01.ams02.networklayer.com - 3 | 40 | 39 | 124 | 136 | 145 | 140 |
| ae1.bbr02.eq01.wdc02.networklayer.com - 3 | 40 | 39 | 131 | 132 | 153 | 131 |
| ae7.bbr01.eq01.wdc02.networklayer.com - 0 | 44 | 44 | 131 | 132 | 148 | 132 |
| ae0.bbr01.tl01.atl01.networklayer.com - 10 | 32 | 29 | 0 | 141 | 147 | 141 |
| ae13.bbr02.eq01.dal03.networklayer.com - 3 | 40 | 39 | 163 | 164 | 165 | 164 |
| ae1.dar02.sr01.dal01.networklayer.com - 0 | 44 | 44 | 158 | 159 | 160 | 158 |
| po2.fcr05.sr06.dal01.networklayer.com - 3 | 40 | 39 | 158 | 160 | 181 | 158 |
|173.192.44.22-static.reverse.softlayer.com - 0 | 44 | 44 | 158 | 158 | 161 | 159 |
|________________________________________________|______|______|______|______|______|______|

Same stuff here, I am in Pakistan and my ISP is totally different from anyone else. Pretty sure it's not our ISP's end sort of fault.


Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 70 0.4 1.4 0.3 22.5 4.6
2. 182.178.128.1 0.0% 70 45.0 45.8 35.9 101.7 13.8
3. 182.184.2.217 0.0% 70 36.4 42.9 35.4 98.1 14.6
4. 10.0.3.1 0.0% 69 36.3 45.7 35.5 165.0 20.3
5. static.lhr63.pie.net.pk 1.4% 69 75.7 84.9 74.3 200.2 20.8
6. 221.120.252.1 5.8% 69 87.1 86.3 74.2 188.0 20.9
7. khi275-P01-pie.net.pk 7.2% 69 73.6 86.4 69.8 251.1 30.8
8. static-khi-ni02-swa.pie.net.pk 5.9% 69 72.5 84.0 71.5 250.9 27.7
9. habib-rafiq.khi77d2.pie.net.pk 5.9% 69 140.9 149.8 138.5 278.7 21.8
10. 36351.sgw.equinix.com 5.8% 69 154.7 151.1 138.0 304.4 28.2
11. ae1.bbr01.eq01.tok01.networklayer.com 11.6% 69 219.3 221.2 212.2 339.0 19.9
12. ae2.bbr02.eq01.sjc02.networklayer.com 1.5% 69 395.1 340.1 329.3 403.0 19.3
13. ae7.bbr01.eq01.sjc02.networklayer.com 0.0% 69 325.5 334.7 323.8 426.1 23.7
14. ae0.bbr02.cs01.den01.networklayer.com 5.8% 69 344.6 356.1 343.4 462.1 24.7
15. ae0.bbr02.eq01.chi01.networklayer.com 8.7% 69 370.8 382.1 369.5 445.5 19.9
16. ae7.bbr01.eq01.chi01.networklayer.com 5.9% 69 366.2 374.3 361.8 463.6 22.5
17. ae0.bbr02.tl01.nyc01.networklayer.com 4.3% 69 426.7 403.4 390.8 548.1 24.2
18. ae0.bbr01.tg01.lon01.networklayer.com 4.3% 69 341.6 347.8 335.9 505.5 24.6
19. ae7.bbr02.tg01.lon01.networklayer.com 4.3% 69 335.2 341.2 334.0 464.1 18.2
20. ae0.bbr02.eq01.ams02.networklayer.com 7.4% 69 339.8 345.5 338.0 422.6 16.2
21. ae6.dar01.sr01.ams01.networklayer.com 8.8% 69 338.6 345.0 338.0 413.9 14.7
22. po1.fcr01.sr01.ams01.networklayer.com 50.0% 69 427.4 356.5 338.1 464.6 31.5
23. 37.58.67.210-static.reverse.softlayer.com 7.4% 69 383.9 349.6 337.4 457.9 23.

No love? :/

"

Angryafrican a écrit :

"

Drakier a écrit :

"

Angryafrican a écrit :

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.

Another explanation would be if a company (Or your computer) wanted to deliver goods to different people at different locations and there was a traffic accident at intersection X. Delivery Truck A normally takes a route involving the affected intersection in order to reach their destination, however in this case they need to take an alternate lengthier route. Delivery Truck B avoids the problem entirely as they're traveling to a different destination and never encounter the traffic accident.

The only thing bad about this explanation is that it doesn't explain packet loss, but that can be easily explained as the goods somehow getting damaged or stolen during transit.

Here is what I have taken away from this thread.

GGG (Grinding Gear Games) has an infrastructure problem.
The problem is with "Networklayer" hops and NOT the ISPs of the people trying to play.
The problem has been here since September and it is now December.
The problem is preventing me and other players from enjoying this game at any meaningful level.


Now I have questions...

Will the problem be resolved?
If Yes, when?

I have this same problem starting in september, but it mostly just manifests itself in disconnects during instance changes, logging in, and character list loading.

"

thyran0 a écrit :

I have this same problem starting in september, but

Okay, that's really not "this same problem", as you go on to tell us it's different.

You should do an MTR while you are having the disconnections though, this MTR report looks fine to me.

having those dc's at session changes, log->char select, char select->game for already month

losing packages at usa ip that is told to be in dallas on so called "networklayer"

any ideas?

sadly couldnt catch the 70%+ packet loss spikes in MTR but saw them real time in PingPlotter
edit: catched the spike