No GGG, LAG is YOUR problem. Look at this,

I don't want to be mean or anything but with this traceroot...



1077 ms... -.-
I am Drakunia... and you are not! And I am also GFL (Gamer For Life)
Actually.. according to the screenshot you posted, your problem is a SEABONE problem.

You're losing over 50% of your packets through there.

How is that a GGG issue?
"
Drakier wrote:
Actually.. according to the screenshot you posted, your problem is a SEABONE problem.

You're losing over 50% of your packets through there.

How is that a GGG issue?


Diablo 3 also goes through seabone and doesn't have any problems.

| 192.168.1.1 - 0 | 323 | 323 | 0 | 0 | 19 | 0 |
| [IP REDACTED] - 11 | 228 | 204 | 22 | 39 | 317 | 23 |
| [IP REDACTED] - 1 | 316 | 314 | 21 | 34 | 89 | 24 |
| [IP REDACTED] - 1 | 316 | 314 | 22 | 34 | 91 | 23 |
| 195.22.193.41 - 2 | 307 | 303 | 21 | 32 | 82 | 22 |
| xe-10-3-3.franco31.fra.seabone.net - 1 | 315 | 313 | 78 | 92 | 170 | 79 |
| ffm-b12-link.telia.net - 2 | 303 | 298 | 76 | 87 | 142 | 77 |
| ffm-bb2-link.telia.net - 3 | 299 | 293 | 73 | 95 | 189 | 74 |
| hbg-bb2-link.telia.net - 2 | 300 | 294 | 78 | 103 | 207 | 85 |
| adm-bb4-link.telia.net - 1 | 312 | 309 | 78 | 102 | 195 | 79 |
| adm-b5-link.telia.net - 2 | 308 | 304 | 78 | 104 | 165 | 96 |
Different hops.

D3 and PoE are on completely separate networks. The path they take to get to their destination is completely different.

That's like saying "There is construction on the road in front of the grocery store, so I can't get in there, but there is no problem getting to the library!"

See the problem there? The grocery store and library are on completely different streets. The route you drive to get to both of them is probably different for a majority of the trip once you leave your neighborhood, no?

The internet works very much in the same way as streets. Locations on the internet are on different streets, and construction on various roads can be different depending on where you are going.
"
Drakier wrote:
Different hops.

D3 and PoE are on completely separate networks. The path they take to get to their destination is completely different.

That's like saying "There is construction on the road in front of the grocery store, so I can't get in there, but there is no problem getting to the library!"

See the problem there? The grocery store and library are on completely different streets. The route you drive to get to both of them is probably different for a majority of the trip once you leave your neighborhood, no?

The internet works very much in the same way as streets. Locations on the internet are on different streets, and construction on various roads can be different depending on where you are going.


In the end... the Networklayer is losing immense amounts of packets... is it or isn't their fault?
I am Drakunia... and you are not! And I am also GFL (Gamer For Life)
"
Drakunia wrote:
In the end... the Networklayer is losing immense amounts of packets... is it or isn't their fault?


No.. it doesn't work that way.

If you're losing packets early on, that packet loss can carry on (and does) to the later hops.

Think of it like this...

Say you're driving to work one day. On a normal day without construction/traffic/etc it takes you 20 minutes. Your average drive time is 20 minutes total. That is made up of a bunch of smaller segments which you can reduce in many different ways.. intersections, miles/kilometers/whatever.

Now.. lets say that one day, you hit a blocked/closed road about half way to work, and it delays you by 5 minutes. You can't say that you were delayed by 5 minutes turning into your work parking lot. You were delayed 5 minutes much earlier on. The problem is with the blockage as you encounter it.

So because you're losing a LOT of packets through seabone, that packet loss carries on to the hops after it, as the packets have troubles reaching their destination due to this packet loss.

You need to contact Seabone or your ISP (who will contact seabone) and see if they can get it restored. Yours isn't the first post recently that has had an issue with seabone through Italy.
Hmmm... I hope you are right. I called them and they said they will call me back.

But how do you explain the different numbers of packets lost on the Networklayer and how do you explain this:

After Seabone there is little to none packets lost. (pre 1.0.0)
I am Drakunia... and you are not! And I am also GFL (Gamer For Life)
Same problem here (I'm from Italy too).
Lag is almost killing my experience with the game.
"
Drakunia wrote:
Hmmm... I hope you are right. I called them and they said they will call me back.

But how do you explain the different numbers of packets lost on the Networklayer ...

After Seabone there is little to none packets lost. (pre 1.0.0)


Coincidence.

Network conditions are constantly changing. The fact that Seabone has an issue now could be purely coincidental to the 1.0.0 patch timing.

It could also be that the patch was so popular that the demand through that node broke it... but I find that pretty unlikely.
I'm with your same ISP (Telecom Italia), i've been investigating this problem for 2 weeks now and I am almost absolutely sure the problem relies in a malfunctioning seabone node causing around 18-20% packet loss during peak hours to all the traffic going through it. The only way i can play from 18:00 to 24:00 is using my office VPN, with sub-par but acceptable performance.

POE is not the only service that's not working. I have been able to replicate the problem with pingtest.net and their Copenhagen server (same routing as poe servers), just to name one. Find an IP in Netherland or Denmark and you are very likely to be in the same situation.

I'll be speaking with Telecom Italia tech support this evening, i'll see if I can talk them to forward the issue to their provider (Telecom Italia Sparkle, owners of the seabone.net network) but, honestly, I don't have much hope.

Bye

Last edited by ThePlash#0157 on Oct 28, 2013, 2:45:37 PM

Report Forum Post

Report Account:

Report Type

Additional Info