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
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
New Contributor
•
9 Messages
Closed
i've had this problem for several weeks now. i'm quite annoyed at cox saying its blizzard and blizzard saying its cox. i'm fairly certain i have definitive evidence its a pathing issue which cox (my provider) should step in to help resolve.
tracert from my local pc:
Tracing route to 12.129.209.68 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.128.32.1
3 8 ms 8 ms 8 ms 70.169.88.78
4 855 ms 7 ms 7 ms 70.169.88.36
5 8 ms 7 ms 7 ms btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
6 17 ms 17 ms 17 ms 68.1.2.121
7 68 ms 17 ms 18 ms xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
8 20 ms 18 ms 17 ms vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
9 * * * Request timed out.
10 18 ms 19 ms 19 ms ATT [4.68.62.230]
11 469 ms 63 ms 51 ms cr2.dlstx.ip.att.net [12.123.16.110]
12 55 ms 55 ms 55 ms cr2.la2ca.ip.att.net [12.122.28.178]
13 51 ms 50 ms 50 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 50 ms 51 ms 51 ms 12.122.251.190
15 51 ms 49 ms 49 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
16 50 ms 51 ms 51 ms 12.129.199.178
17 51 ms 51 ms 51 ms 12.129.209.68
Trace complete.
tracert from a remote desktop connection (connected to remote from my local pc):
Tracing route to 12.129.209.68 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 69.20.12.2
2 1 ms <1 ms <1 ms core7-aggr402a-2.iad3.rackspace.net [69.20.3.112]
3 1 ms <1 ms 1 ms corea-core7.iad2.rackspace.net [69.20.2.96]
4 1 ms <1 ms 1 ms corea-edge7.edge7.iad3.rackspace.net [69.20.1.241]
5 1 ms 1 ms 1 ms xe-2-3-1.er2.dca2.us.above.net [208.185.125.153]
6 <1 ms <1 ms <1 ms vlan52.ebr2.Washington12.Level3.net [4.69.146.222]
7 1 ms 1 ms <1 ms ae-204-3604.edge1.Washington12.Level3.net [4.69.158.45]
8 2 ms 67 ms 1 ms ae1.er1.iad10.us.above.net [64.125.31.206]
9 70 ms 68 ms 3 ms 192.205.36.125
10 70 ms 66 ms 70 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 69 ms 70 ms 67 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 69 ms 68 ms 67 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 66 ms 70 ms 67 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 66 ms 66 ms 66 ms gar20.la2ca.ip.att.net [12.122.128.181]
15 66 ms 66 ms 67 ms 12.122.251.190
16 67 ms 66 ms 67 ms 12.129.209.68
Trace complete.
i put a ticket in last week and the cox rep said 'its blizzards problem' and closed the ticket. i will open another ticket today but figured id try the forums as well...seems at least some of the posts here get responses.
i have several days worth of tracert files which all have the same issue...the one hop from level3 to the att node (which is actually on level3's backbone) is always 100% packet loss...hence a huge lag spike and resultant frustration.
please help!
Discussions
•
Updated
9.5K
19
0
0
Tv upgrade to HD
Discussions
1
0
Poor internet service
Discussions
0
0
Cox / spectrum sucks
Discussions
1
0
Spectrum is terrible
Discussions
6
Reapeating connectivity issues
Discussions
1
0
Tv upgrade to HD
Discussions
1
0
Cox bill wrong
Discussions
1
Poor internet service
Discussions
0
0
Cox / spectrum sucks
Discussions
1
0
Connection Issues After Isaias
Discussions
1
0