Intermittent Lag in online game

I'm having the same issue in a post below yours HAHA what server do you play on?

Anyway, run a tracert 204.2.229.9 in your command prompt and see what you get there. Copy and post the results.

Ultros! The lag is killing me right now, i cant even do gathering. Everyone i play with seems to be fine. Looks like a local issue?

Also, here is the tracert:

 1     7 ms     8 ms     8 ms  10.115.60.1
  2     7 ms    27 ms    12 ms  100.127.73.56
  3    11 ms    10 ms     9 ms  wsip-70-166-189-128.ph.ph.cox.net [70.166.189.128]
  4    31 ms    54 ms    30 ms  langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
  5    22 ms    21 ms    21 ms  ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
  6    48 ms    49 ms    48 ms  ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
  7    41 ms    39 ms    48 ms  ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
  8    45 ms    51 ms    46 ms  ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
  9    67 ms    73 ms    76 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 10    49 ms    47 ms    48 ms  ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
 11    54 ms    59 ms    55 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 12    51 ms     *       49 ms  204.2.229.242
 13    67 ms    49 ms    50 ms  204.2.229.10

and the other server:

Tracing route to 204.2.229.9 over a maximum of 30 hops

  1    16 ms     9 ms    12 ms  10.115.60.1
  2     8 ms     8 ms     9 ms  100.127.73.58
  3     8 ms    25 ms     9 ms  wsip-70-166-189-130.ph.ph.cox.net [70.166.189.130]
  4   138 ms    51 ms    63 ms  langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
  5    23 ms    22 ms    29 ms  ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
  6    47 ms    47 ms    49 ms  ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
  7    39 ms    40 ms    41 ms  ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
  8    45 ms    55 ms    46 ms  ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
  9    58 ms     *       44 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 10    47 ms    56 ms    47 ms  ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
 11    51 ms     *       52 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 12     *       50 ms     *     204.2.229.242
 13    52 ms    53 ms    50 ms  204.2.229.9

I can't say for sure only cox can give us answers! GL 

Hi TiffanyR,

I have the premier package 150/10. The speedtest is below:

The upload looks like its having issues. Also, my PC has no Wifi connection, only a hardwire. So Wifi for this device would be impossible.

@jdent,

The modem is reporting good signals and I am not seeing any latency to the modem when I ping it. Is this happening with all devices in the home or just this one?

Thanks,

Allan - Cox Support Forums Moderator.

simlar to http://forums.cox.com/forum_home/internet_forum/f/5/p/19309/72447.aspx#72447

This issue is happening with all devices connected. It is most apparent when playing the game we both play. Video streaming applications (like netflix)  do not seem affected by any lag or reduction in quality.

2 PCs are hardwired to the modem. The lag issues in our game occur usually in the evenings. Ordinarily i would say it was the game itself and their server connections, however other friends that we play with on the same server are not having any lag issues.

@jdent

Please send us an email with your full address, name, brief description/link to this thread, and a tracreoute to the game server so we can research this issue further for you. 

Thanks,

Allan - Cox Support Forums Moderator.

Thank you,

Thank you, what is the email address?

I just emailed. Thanks for your help.

Just an FYI, the lag we are experiencing in game is pretty gnarly currently - the trace routes run are changing each time i run i and show packet loss in various places. 

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    32 ms    24 ms     9 ms  10.115.60.1
  2    12 ms    12 ms     7 ms  100.127.73.58
  3     9 ms    10 ms    10 ms  100.120.100.4
  4    22 ms    21 ms    22 ms  langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
  5    24 ms    24 ms    21 ms  ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
  6    49 ms    52 ms     *     ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
  7    38 ms    38 ms    39 ms  ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
  8    48 ms    48 ms    63 ms  ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
  9     *       54 ms    74 ms  ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
 10    50 ms    50 ms    48 ms  ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
 11    58 ms    52 ms    52 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 12    79 ms    53 ms    56 ms  204.2.229.242
 13    52 ms     *       50 ms  204.2.229.97

IN ADDITION,

I contacted NTT, where the issues seem to be originating, and they told me to contact Cox and have them escalate, copy of the email below:

"Hello,

If you are not an NTT customer, please open a ticket with your provider and have them
escalate if you believe there is an issue.

Best Regards,

Jon Abdul - CCNA | JNCIA
Network Analyst
NTT Communications Global IP Network Operations Center"

So really, I hope the Cox team can escalate and find where the issue is.

Thank you.

Just wanted to chime in and say i am also getting this exact same issue,

Tracing route to 204.2.229.9 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  READYSHARE [192.168.1.1]
  2    13 ms     9 ms    11 ms  10.39.120.1
  3    12 ms    10 ms    11 ms  100.127.73.174
  4    11 ms    11 ms    11 ms  70.169.73.196
  5    25 ms    20 ms    23 ms  langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
  6    23 ms    23 ms    21 ms  ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
  7    58 ms     *       47 ms  ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
  8    41 ms    40 ms     *     ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
  9    46 ms     *       48 ms  ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
 10     *       46 ms    49 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 11    52 ms     *       58 ms  ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
 12    48 ms     *       49 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 13     *        *        *     Request timed out.
 14    49 ms    50 ms    49 ms  204.2.229.9

Trace complete.

I would love to hear any news on this matter, please Cox send it on up the ladder!

NTT is dropping packets on all 5 of their hops. I've run 5 traces and 4 out of 5 have dropped data. 

Their response to me is the same : 

Alex,

Unfortunately, we are not able to open tickets to investigate circuits
not owned by the contact. Please have your upstream open a ticket and we
will be happy to investigate these circuits.

Cox, they are not listening to the end-users even though we have pointed out that there is a problem on there end.

Please escalate! This has been happening for a few days now.

Tracing route to 204.2.229.97 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 7 ms 7 ms 7 ms 10.48.64.1
3 9 ms 8 ms 7 ms 100.127.74.54
4 7 ms 8 ms 7 ms 70.169.74.152
5 19 ms 20 ms 19 ms langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
6 25 ms 22 ms 21 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 33 ms 32 ms 33 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 20 ms 20 ms 19 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 *     27 ms 27 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 29 ms 28 ms 29 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 51 ms 30 ms 30 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 34 ms 33 ms 33 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 39 ms 32 ms 33 ms 204.2.229.242
14 33 ms 29 ms 29 ms 204.2.229.97

Tracing route to 204.2.229.97 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 7 ms 10 ms 6 ms 10.48.64.1
3 7 ms 8 ms 9 ms 100.127.74.54
4 7 ms 7 ms 7 ms 70.169.74.152
5 20 ms 20 ms 19 ms langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
6 19 ms 19 ms 21 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 43 ms 32 ms 31 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 20 ms 20 ms 20 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 27 ms 33 ms 28 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 35 ms 29 ms 28 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 30 ms 30 ms * ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 33 ms 33 ms 33 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 34 ms 32 ms 33 ms 204.2.229.242
14 30 ms 29 ms 30 ms 204.2.229.97

Tracing route to 204.2.229.97 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 6 ms 6 ms 8 ms 10.48.64.1
3 8 ms 7 ms 14 ms 100.127.74.54
4 8 ms 7 ms 7 ms 70.169.74.152
5 28 ms 20 ms 22 ms langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
6 20 ms 20 ms 21 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 32 ms 32 ms 31 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 19 ms 20 ms 19 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 28 ms * 26 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 29 ms 30 ms 29 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 31 ms 34 ms 30 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 33 ms 33 ms 33 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 33 ms 33 ms 32 ms 204.2.229.242
14 30 ms 30 ms 29 ms 204.2.229.97