Forum Discussion

KSparx's avatar
KSparx
New Contributor

lags & packet loss at hops.

I've been having problems accessing the server for World of Warships game. They say that the lag / packet loss at hops 5/6 are the issue. I ran a trace to cox.net, along with the two hops. Following are the results:

tracert cox.net [68.99.123.161] over a max of 30 hops:
1 < 1  ms 1  ms 1  ms 192.168.1.1
2 7  ms 7  ms 7  ms 10.35.48.1
3 9  ms 7  ms 7  ms 100.127.65.152
4 7  ms 7  ms 8  ms 70.169.73.90
5 53  ms 54  ms 52  ms dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
6 53  ms 54  ms 53  ms 68.11.15.234
7 53  ms 53  ms 56  ms 68.99.123.4
8 53  ms 51  ms 51 ms ww2.cox.com [68.99.123.161]
Trace Complete.
-----------------------------------------------------------------------------------------------------------------
tracert ae-1-11.bear1.Phoenix1.Leevel3.net  [4.69.210.157] over a max of 30 hops:
1 <1  ms 1  ms 1  ms 192.168.1.1
2 7  ms 7  ms 7  ms 10.35.48.1
3 8  ms 7  ms 9  ms 100.127.65.154
4 9  ms 10  ms 8  ms 70.169.73.196
5 9  ms 13  ms 15  ms lag-157.bear2Phoenix1.Level3.net [4.28.82.53]
6 9  ms 9  ms 9  ms ae-1-11.bear1.Phoenix1.Level3.net [4.69.210.157]
Trace Complete.
-------------------------------------------------------------------------------------------------------------------
tracert lag-157.bear2.Phoenix1.Level3.net [4.28.82.53] over a max of 30 hops:
1 <1  ms 1  ms 1  ms 192.168.1.1
2 7  ms 7  ms 7  ms 10.35.48.1
3 9  ms 7  ms 7  ms 100.127.65.152
4 7  ms 7  ms 8  ms 70.169.73.90
5 9  ms 14  ms 10  ms lag-194.bear1.Phoenix1.Level3.net [4.31.188.61]
6 9  ms 9   ms 9  ms lag-157.bear2.Phoenix1.Level3.net [4.28.82.53]
Trace Complete.
Also, here's a copy of PingPlotter file to game server:

Any ideas on how to prevent this from happening? Thx in advance for any help.

4 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • DannyS's avatar
    DannyS
    Moderator

    Hello KSparx,

    Sorry that it appears you may be experiencing some routing concerns.  We have looked into this and this is not a cox issue.  The first 3 will show you route off a 100.127.65 net block with no issue to any destination thru that point.  The ping plotter shows latency showing up later on down the trace at 4.69.210.157 and appears to belong to Level 3 communications which is a trunk carrier.  You can find this here. https://www.whois.com/whois/4.69.210.157.   They do have contact information in that link as well to ask for assistance.

  • KSparx's avatar
    KSparx
    New Contributor

    Thanks for the info, Danny. I'll contact them & see what's up.

    KS

  • KSparx's avatar
    KSparx
    New Contributor

    Is there any way I can not go through Level3? They're causing problems for a lot of people it appears.  Thanks.

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @KSparx

    Looking at your pingplotter results I'm not thinking there's an issue at Level 3. Your traffic is reaching it's intended destination without any loss which make me believe what you're seeing is intentional ICMP de-prioritization.