Packet loss confirmed via winMTR (instructions included)

[VexacionR]

So if we do see a problem on the route to the server how would someone go about altering the route to avoid the problem point? I used this method and tracert against some other known server ip address and I found a common issue with tinet-gw.customer.alter.net but I don't know how I would go about getting around it...:

[Appleh4x]

So if we do see a problem on the route to the server how would someone go about altering the route to avoid the problem point? I used this method and tracert against some other known server ip address and I found a common issue with tinet-gw.customer.alter.net but I don't know how I would go about getting around it...:

Your best bet is to use a VPN, or just wait it out until you are routed through a different node on their end.

[svann]

So if we do see a problem on the route to the server how would someone go about altering the route to avoid the problem point? I used this method and tracert against some other known server ip address and I found a common issue with tinet-gw.customer.alter.net but I don't know how I would go about getting around it...:

The pic you show is not showing a problem. If you have loss on one step and not on following steps then that is meaningless. Think about it. How would you have loss on step 7 but not on step 8, when it has to go through 7 to get to 8? Some servers give low priority to pings and that is likely what you are seeing. The only time you can take a tracert seriously is if 7 is lossy, and they every step after that was also lossy. Then you would know the problem starts at 7.

[KisaiTenshi]

So if we do see a problem on the route to the server how would someone go about altering the route to avoid the problem point? I used this method and tracert against some other known server ip address and I found a common issue with tinet-gw.customer.alter.net but I don't know how I would go about getting around it...:

Doesn't mean anything... case in point:

[Shizue]

Well, seems someone did something on SE's end today. This afternoon I was experiencing severe lag and packet loss on the last 2 hops (as seen in the OP). This evening I had no lag at all during FATEs, dungeons or anything else. No packet loss noted on the last 2 hops at the moment (left winMTR running a trace for a good hour or so).

Ninja fixed?

And Kisai and Svann are both accurate. As long as the destination is receiving all of the packets you are in good shape... also as long as the latency is acceptable as well. There are many reasons why one or more hops may show packet loss but ultimately it's moot if the packets reach the destination.