Zone lag issues

169.47.47.87 was the IP for southern forest above first w/lag, 2nd w/out same servers.
Below, friends hideout lag first, my hideout no lag

To other people posting in this thread.

You are making it difficult to help King. For the love of whatever God you believe in (or lack thereof), make your own thread if you want some help. It's in the first paragraph of the first sticky to NOT do exactly what you all are doing. If you want to follow the thread, fine. If you want to try anything I may ask King to do, fine. Just knock off the posting in his thread unless you are going to HELP HIM. I am not going to help 5/10/15 people in a thread. It's too much of a hassle and if you can't see why that is, then just bugger off.

This is King's thread to get help in, not a free for all like the rest of the forums.


King:

First trace. At least you aren't getting packet loss on this one. Don't mind that single packet going bye bye..it's nothing to worry about. The jump in latency is though.

Concern starts here:
| ae7---0.scr01.mias.fl.frontiernet.net - 1 | 106 | 105 | 10 | 13 | 122 | 12 |
| ae2-0.scr02.dlls.tx.frontiernet.net - 0 | 110 | 110 | 37 | 39 | 44 | 40 |

| ae5.cbs02.eq01.dal03.networklayer.com - 56 | 34 | 15 | 0 | 42 | 44 | 41 |
| ae0.cbs01.tl01.atl01.networklayer.com - 47 | 39 | 21 | 40 | 43 | 48 | 43 |

While this ^^ isn't true packet loss, it's indicative of traffic congestion. The Dallas/ATL hops have always been a bit fluky especially under load, which they tend to get to often. I am not particularly blaming those hops, just some info for you from what I have seen over the years...they have caused issues before.

Second and third traces are again pretty much the same. That mias.fl. - Dallas hop is acting up..and the latency stays throughout the rest of the route. Same thing applies to the second/third set on networklayer's end here as well.

There is nothing demonstrably different between the first three traces that would actually show any issues which could be causing this.

Last trace. This is where it gets sorta interesting as you actually did get a 1% packet loss carrying forward from your second hop (Your cable modem it would look like), which if let run for longer would probably jump up to a 2/3%. Even that small amount can affect things in POE in a bad way. I have had even 2% PL make the game unplayable, and I go through only about 6 hops to get to the DC server.

A couple of things I'd like you to do.

Since you are actually getting some packet loss from that 4th trace. Unplug both router and modem for at least a minute. Plug 'em back in and turn 'em on. Run a good long test to 500 this time. Once to a login server, then another to your hideout. If that packet loss goes away, perfect; not so much if it stays.

If it stays, time to yell at your ISP. Make sure and tell them you are getting packet loss and make sure they see the MTR's with said packet loss, as that's the proof that you are going to need to show them that something is borked.

If the packet loss goes away, I would still give them a call anyway. It "looks" like frontier is having some issues atm. Frontier has had many many many issues before, and you aren't the first to have issues using them and trying to play POE. It goes in cycles it seems. You may want to ask them if they can try to reroute your traffic around those two nodes noted above (You may need to ask to speak to a level 2 tech). At the very least, ask them if they know of any network issues they are experiencing currently and let them know that your online experience is being affected, you aren't exactly happy, and just complain a little bit. :)

Last thing I would do, is email GGG tech support. Those networklayer hops may be having some issues and the only ones in any real position to see if anything is truly going on and can be done about it is GGG. Drop them an email at techsupport@grindinggear.com with a copy of your MTR's. They can use them, if there are issues, as ammo to help get things sorted out. You may want to also link them to this thread so they can see what steps you have gone through etc.

I know none of this actually fixes your issues, but it may get you closer to getting things resolved sooner rather than later.

~Dune