Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Internet Issues (gaming)
For the past month now whenever I game I have been having internet latency issues. Like as if it is having difficulty reaching its location. Below is my tracert and pathping and speedtest.
Tracing route to 63.240.161.189 over a maximum of 30 hops
1 2 ms 1 ms 1 ms (was my IP removed to be safe)
2 33 ms 13 ms 18 ms 10.146.160.1
3 58 ms 18 ms 12 ms 172.21.1.4
4 15 ms 14 ms 15 ms 70.169.74.56
5 17 ms 12 ms 12 ms 70.169.75.153
6 44 ms * 25 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 29 ms 24 ms 28 ms te0-7-0-20.ccr23.lax05.atlas.cogentco.com [154.54.13.129]
8 29 ms 37 ms 25 ms be2178.mpd22.lax01.atlas.cogentco.com [154.54.41.117]
9 80 ms 75 ms 60 ms be2065.ccr21.iah01.atlas.cogentco.com [154.54.5.65]
10 70 ms 65 ms 65 ms be2147.ccr22.dfw01.atlas.cogentco.com [154.54.27.18]
11 92 ms 90 ms 89 ms be2141.mpd22.mci01.atlas.cogentco.com [154.54.5.157]
12 88 ms 88 ms 87 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.130]
13 91 ms 88 ms 96 ms be2004.ccr21.ord03.atlas.cogentco.com [154.54.5.10]
14 157 ms 131 ms 177 ms att.ord03.atlas.cogentco.com [154.54.12.86]
15 130 ms 126 ms 130 ms cr1.cgcil.ip.att.net [12.122.81.18]
16 140 ms 149 ms 130 ms gar6.ipsin.ip.att.net [12.122.132.241]
17 122 ms 126 ms 123 ms 12.122.251.14
18 127 ms 140 ms 119 ms 63.240.130.202
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Tracing route to 63.240.161.189 over a maximum of 30 hops
0 lizzie-PC
1 (was my IP removed to be safe)
2 10.146.160.1
3 172.21.1.4
4 70.169.74.56
5 * 70.169.75.153
6 langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 te0-7-0-20.ccr23.lax05.atlas.cogentco.com [154.54.13.129]
8 be2180.ccr21.lax01.atlas.cogentco.com [154.54.41.57]
9 be2065.ccr21.iah01.atlas.cogentco.com [154.54.5.65]
10 be2144.ccr21.dfw01.atlas.cogentco.com [154.54.25.106]
11 be2064.mpd21.mci01.atlas.cogentco.com [154.54.5.217]
12 be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.130]
13 * be2006.ccr21.ord03.atlas.cogentco.com [154.54.5.18]
14 att.ord03.atlas.cogentco.com [154.54.12.86]
15 cr2.cgcil.ip.att.net [12.122.81.22]
16 gar6.ipsin.ip.att.net [12.122.132.241]
17 12.122.251.14
18 63.240.130.202
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 lizzie-PC
0/ 100 = 0% |
1 22ms 0/ 100 = 0% 0/ 100 = 0% (was my IP removed to be safe)
0/ 100 = 0% |
2 39ms 0/ 100 = 0% 0/ 100 = 0% 10.146.160.1
0/ 100 = 0% |
3 38ms 0/ 100 = 0% 0/ 100 = 0% 172.21.1.4
0/ 100 = 0% |
4 38ms 0/ 100 = 0% 0/ 100 = 0% 70.169.74.56
0/ 100 = 0% |
5 41ms 2/ 100 = 2% 2/ 100 = 2% 70.169.75.153
0/ 100 = 0% |
6 57ms 2/ 100 = 2% 2/ 100 = 2% langbprj02-ae2.rd.la.cox.net [68.1.1.19]
0/ 100 = 0% |
7 49ms 2/ 100 = 2% 2/ 100 = 2% te0-7-0-20.ccr23.lax05.atlas.cogentco.com [154.54.13.129]
0/ 100 = 0% |
8 55ms 0/ 100 = 0% 0/ 100 = 0% be2180.ccr21.lax01.atlas.cogentco.com [154.54.41.57]
0/ 100 = 0% |
9 80ms 1/ 100 = 1% 1/ 100 = 1% be2065.ccr21.iah01.atlas.cogentco.com [154.54.5.65]
0/ 100 = 0% |
10 81ms 0/ 100 = 0% 0/ 100 = 0% be2144.ccr21.dfw01.atlas.cogentco.com [154.54.25.106]
0/ 100 = 0% |
11 91ms 1/ 100 = 1% 1/ 100 = 1% be2064.mpd21.mci01.atlas.cogentco.com [154.54.5.217]
0/ 100 = 0% |
12 104ms 0/ 100 = 0% 0/ 100 = 0% be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.130]
0/ 100 = 0% |
13 103ms 0/ 100 = 0% 0/ 100 = 0% be2006.ccr21.ord03.atlas.cogentco.com [154.54.5.18]
8/ 100 = 8% |
14 146ms 8/ 100 = 8% 0/ 100 = 0% att.ord03.atlas.cogentco.com [154.54.12.86]
92/ 100 = 92% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.81.22]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar6.ipsin.ip.att.net [12.122.132.241]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.14
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.202
Trace complete.
| Start |  CoxNet | Download Speed | Upload Speed | Latency | Your IP Address | Cox Market |
|---|---|---|---|---|---|---|
| Mon Nov 25 2:08 PM | Yes | 7 Mbps | 19 Mbps | 34 millisec | 24.251.70.240 | Phoenix |
Health_Edge
+5 more
Valued Contributor III
•
Tracert looks to show no problems on Cox's end. Most of the latency appears to be occuring between hop 13 and 14 which seems to be the backbone between Kansas City and Denver. I don't know if this latency is abnormal without anything to compare it to.
First thing I would do is keep a constant ping (Ping -t 68.1.1.19) to the server as you play and see if you see latency increase in the ping at the same time you see it in the client.
Next I would turn on FPS counter with Control+R. Do you have frame loss when you experience the problem? There are a couple threads on the WoW forums about Freezing and loss of FPS because of some new changes made to the game engine. Here is 1 recent example.
0
0
mosteel
New Contributor
•
The latency is abnormal. As for the ping to 68.1.1.19 that one varies on day to day sometimes high sometimes low. Just tested it and its normal on that IP
I dont loose FPS during gaming just my latency is higher then normal. Is there a way to contact the people who run hop 13 and 14?
0
0
Health_Edge
+5 more
Valued Contributor III
•
http://cogentco.com/en/contact/general-inquiry
0
0