Skip to content

Instantly share code, notes, and snippets.

@jhenkens

jhenkens/.Cox Latency Issues.md

Last active August 29, 2015 14:08
Show Gist options
  • Save jhenkens/618b65180c9a20bdf4d8 to your computer and use it in GitHub Desktop.
Save jhenkens/618b65180c9a20bdf4d8 to your computer and use it in GitHub Desktop.
Download ZIP
Cox Latency And Speed Issues
Raw
.Cox Latency Issues.md

Figured I'd try to put together all the packet traces and stuff for cox in one spot to try to get my issues figured out.

Basically, the issue is that during prime time every day, my internet becomes basically unusable for any media usage. Burst speeds of 28Mbps are my normal speed during primetime, when I'm expected to get 100Mbps+ on my current tier. These tests are using their servers! Using Speedtest.net, I get wildly inconsistent speeds - from <10Mbps to >45Mbps during primetime.

WoW and CS:GO have been unplayable, with sustained reported ping of 150+, spikes in the 400 range, and felt latency of around 1 second or more. Streaming videos buffer constantly. I had a SB6120 modem. I replaced it with a SB6183 modem on 11/4/2014, after @coxhelp suggested I may need to get an 8-channel bonded modem. This new modem is up to 16-channels. But I still only see 4 bonded, UP/Down.

11/3/2014 - 10PM Pacific - 30 Mbps Cox Speedtest
Router utilization during 11/3/2014 speed test
11/4/2014 - 7:15PM Pacific - 25Mbps Cox Speedtest
11/4/2014 - 9:30PM Pacific - traceroute to valve servers
11/4/2014 - 9:30PM Pacific - 18MBps Cox Speedtest
11/4/2014 - 9:45PM Pacific - Cox Gateway 150ms Pings
11/5/2014 - 8:45AM Pacific - Non-Peak, 110Mbps Cox Speedtest
11/11/2014 - 7:45PM Pacific - <10Mbps, 500+ ping, 200+ jitter, Router Status

My passive utilization is essentially zero. This same setup used to hit 75+ 24/7 at my old apartment, and sometimes hits 80+ here with Cox's "doubled speeds", but that is only ever at like 8am on a weekday. The fact that during prime time I was AVERAGING 100ms ping to the FIRST HOP outside of my modem, is unnacceptable. A half hour later, I'm still averaging near 50, with spikes every 8 pings to well over 100ms. For the first hop. For comparison, Menlo Park Comcast, same $$ package, is sitting nicely at about 6ms ping to first hop during primetime.

Our initial findings on 10/3/2014 with one traceroute was that there was a ping spike in AT&T's backbone network. Cox rep seemed to be brushing it off as not part of their problem anymore. Really, they should be talking to AT&T and issuing their tech a ticket saying they are causing routing problems, or to route around the bad connection. However, that can't be the only issue. Obviously this neighboorhood's node is just insanely impacted during prime-time hours.

Raw
comedy_central_mtvnservices_com_path_ping.txt
Tracing route to 184.180.124.2 over a maximum of 30 hops
0 SamwellBlue.lan [192.168.11.124]
1 OpenWrt.lan [192.168.11.1]
2 10.6.44.1
3 ip68-4-12-20.oc.oc.cox.net [68.4.12.20]
4 ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
5 * * *
Computing statistics for 100 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 SamwellBlue.lan [192.168.11.124]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% OpenWrt.lan [192.168.11.1]
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% 10.6.44.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-12-20.oc.oc.cox.net [68.4.12.20]
0/ 100 = 0% |
4 17ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
Trace complete.
Raw
comedy_central_mtvnservices_com_path_ping2.txt
Tracing route to 184.180.124.33 over a maximum of 30 hops
0 SamwellBlue.lan [192.168.11.124]
1 OpenWrt.lan [192.168.11.1]
2 10.6.44.1
3 ip68-4-12-22.oc.oc.cox.net [68.4.12.22]
4 ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
5 mtc1bbrj01-ge710.rd.om.cox.net [68.1.0.136]
6 184.180.124.33
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 SamwellBlue.lan [192.168.11.124]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% OpenWrt.lan [192.168.11.1]
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% 10.6.44.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-12-22.oc.oc.cox.net [68.4.12.22]
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% mtc1bbrj01-ge710.rd.om.cox.net [68.1.0.136]
0/ 100 = 0% |
6 20ms 0/ 100 = 0% 0/ 100 = 0% 184.180.124.33
Trace complete.
Raw
CSGO Server tracert
How does this look alright? Look at how wild everything is.
C:\Users\Johan Henkens>tracert 192.69.97.207
Tracing route to 192-69-97-207.valve.net [192.69.97.207]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms OpenWrt.lan [192.168.11.1]
2 21 ms 181 ms 36 ms 10.6.44.1
3 65 ms 22 ms 28 ms ip68-4-12-20.oc.oc.cox.net [68.4.12.20]
4 67 ms 40 ms 38 ms ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
5 194 ms 36 ms 167 ms 68.1.5.137
6 28 ms 65 ms 48 ms xe-7-2-3.edge2.LosAngeles9.Level3.net [4.53.230.
65]
7 74 ms 251 ms 45 ms 4.68.105.13
8 112 ms 65 ms * 4.68.105.13
9 72 ms 94 ms 90 ms VALVE-CORPO.edge2.Seattle3.Level3.net [4.53.159.
214]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
Raw
kg_path_ping
11/4/2014 7:00PM Pacific
Tracing route to 12.129.209.68 over a maximum of 30 hops
0 SamwellBlue.lan [192.168.11.124]
1 OpenWrt.lan [192.168.11.1]
2 10.6.44.1
3 ip68-4-12-20.oc.oc.cox.net [68.4.12.20]
4 ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
5 68.1.5.137
6 xe-9-2-2.edge2.LosAngeles9.Level3.net [4.53.230.205]
7 ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
8 ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
9 192.205.37.145
10 cr2.la2ca.ip.att.net [12.122.129.106]
11 12.123.132.209
12 12-122-254-230.attens.net [12.122.254.230]
13 mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
14 12.129.209.68
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 SamwellBlue.lan [192.168.11.124]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% OpenWrt.lan [192.168.11.1]
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% 10.6.44.1
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-12-20.oc.oc.cox.net [68.4.12.20]
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
0/ 100 = 0% |
5 20ms 0/ 100 = 0% 0/ 100 = 0% 68.1.5.137
0/ 100 = 0% |
6 25ms 0/ 100 = 0% 0/ 100 = 0% xe-9-2-2.edge2.LosAngeles9.Level3.net [4.53.230.205]
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
0/ 100 = 0% |
8 27ms 0/ 100 = 0% 0/ 100 = 0% ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
0/ 100 = 0% |
9 30ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.145
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.129.106]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 12.123.132.209
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-230.attens.net [12.122.254.230]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
0/ 100 = 0% |
14 26ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68
Trace complete.
Raw
KJ traceroute
11/11/2014
Tracing route to 12.129.209.68 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms OpenWrt.lan [192.168.11.1]
2 * * * Request timed out.
3 226 ms 804 ms 225 ms ip68-4-12-20.oc.oc.cox.net [68.4.12.20]
4 344 ms 289 ms 401 ms ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
5 969 ms 906 ms 631 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 333 ms 270 ms 725 ms xe-9-2-2.edge2.LosAngeles9.Level3.net [4.53.230.205]
7 676 ms 759 ms 259 ms ae-108-3508.bar2.Tustin1.Level3.net [4.69.158.110]
8 203 ms 740 ms 262 ms ae-108-3508.bar2.Tustin1.Level3.net [4.69.158.110]
9 782 ms 480 ms 519 ms 192.205.37.145
10 130 ms 89 ms 499 ms cr2.la2ca.ip.att.net [12.122.129.106]
11 483 ms 525 ms 652 ms 12.123.132.209
12 753 ms 859 ms 804 ms 12-122-254-230.attens.net [12.122.254.230]
13 102 ms 251 ms 443 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
14 377 ms 852 ms 534 ms 12.129.209.68
Trace complete.
Raw
malganis_path_ping
11/4/2014 7:00PM Pacific
Tracing route to 63.240.104.93 over a maximum of 30 hops
0 SamwellBlue.lan [192.168.11.124]
1 OpenWrt.lan [192.168.11.1]
2 10.6.44.1
3 ip68-4-12-22.oc.oc.cox.net [68.4.12.22]
4 ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
5 mtc1bbrj01-ge710.rd.om.cox.net [68.1.0.136]
6 xe-5-0-1.edge2.LosAngeles9.Level3.net [4.53.230.85]
7 ae-107-3507.bar2.Tustin1.Level3.net [4.69.158.106]
8 ae-107-3507.bar2.Tustin1.Level3.net [4.69.158.106]
9 192.205.37.145
10 cr1.la2ca.ip.att.net [12.122.128.102]
11 cr1.slkut.ip.att.net [12.122.30.29]
12 cr2.dvmco.ip.att.net [12.122.30.26]
13 cr1.cgcil.ip.att.net [12.122.31.86]
14 cr2.cgcil.ip.att.net [12.122.2.54]
15 cr1.n54ny.ip.att.net [12.122.1.1]
16 gar1.nw2nj.ip.att.net [12.122.131.81]
17 12.122.251.10
18 * * *
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 SamwellBlue.lan [192.168.11.124]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% OpenWrt.lan [192.168.11.1]
0/ 100 = 0% |
2 24ms 0/ 100 = 0% 0/ 100 = 0% 10.6.44.1
0/ 100 = 0% |
3 26ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-12-22.oc.oc.cox.net [68.4.12.22]
0/ 100 = 0% |
4 31ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
0/ 100 = 0% |
5 31ms 0/ 100 = 0% 0/ 100 = 0% mtc1bbrj01-ge710.rd.om.cox.net [68.1.0.136]
0/ 100 = 0% |
6 35ms 0/ 100 = 0% 0/ 100 = 0% xe-5-0-1.edge2.LosAngeles9.Level3.net [4.53.230.85]
0/ 100 = 0% |
7 32ms 0/ 100 = 0% 0/ 100 = 0% ae-107-3507.bar2.Tustin1.Level3.net [4.69.158.106]
0/ 100 = 0% |
8 35ms 0/ 100 = 0% 0/ 100 = 0% ae-107-3507.bar2.Tustin1.Level3.net [4.69.158.106]
0/ 100 = 0% |
9 44ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.145
100/ 100 =100% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.128.102]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.29]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.30.26]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.31.86]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.2.54]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.1.1]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar1.nw2nj.ip.att.net [12.122.131.81]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.10
Trace complete.
Raw
Modem Channel Info.md

11/4/2014 - 6PM Status The statuses listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

###Startup Procedure###

Procedure Status Comment
Acquire Downstream Channel Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

###Downstream Bonded Channels###

Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 85 813000000 Hz 0.3 dBmV 39.3 dB 0 0
2 Locked QAM256 86 819000000 Hz 0.6 dBmV 39.4 dB 0 0
3 Locked QAM256 87 825000000 Hz 0.5 dBmV 39.3 dB 0 0
4 Locked QAM256 88 831000000 Hz 0.2 dBmV 39.2 dB 0 0

###Upstream Bonded Channels###

Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 2 2560 Ksym/sec 30200000 Hz
2 Locked TDMA and ATDMA 1 2560 Ksym/sec 26900000 Hz
3 Locked ATDMA 3 2560 Ksym/sec 33500000 Hz
4 Locked ATDMA 4 2560 Ksym/sec 36800000 Hz
Raw
Modem channel info2.md

11/5/2014 8:30am Status The statuses listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

###Startup Procedure###

Procedure Status Comment
Acquire Downstream Channel Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

###Downstream Bonded Channels###

Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 89 837000000 Hz 0.0 dBmV 39.8 dB 0 0
2 Locked QAM256 90 843000000 Hz -0.1 dBmV 39.5 dB 0 0
3 Locked QAM256 91 849000000 Hz -0.5 dBmV 39.7 dB 0 0
4 Locked QAM256 92 855000000 Hz -1.1 dBmV 39.6 dB 0 0
5 Locked QAM256 93 861000000 Hz -1.3 dBmV 39.6 dB 0 0
6 Locked QAM256 94 867000000 Hz -1.7 dBmV 39.5 dB 0 0
7 Locked QAM256 95 873000000 Hz -2.1 dBmV 39.4 dB 0 0
8 Locked QAM256 96 879000000 Hz -2.0 dBmV 39.3 dB 0 0

###Upstream Bonded Channels###

Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked TDMA and ATDMA 1 2560 Ksym/sec
2 Locked ATDMA 2 2560 Ksym/sec 30200000 Hz
3 Locked ATDMA 3 2560 Ksym/sec 33500000 Hz
4 Locked ATDMA 4 2560 Ksym/sec 36800000 Hz
Raw
pathping commands
pathping 63.240.104.93 > malganis_path_ping.txt
pathping 12.129.209.68 > kj_path_ping.txt
pathping 192.69.96.1 > valve_path_ping.txt
pathping 184.180.124.2 > comedy_central_mtvnservices_com_path_ping.txt
pathping 184.180.124.33 > comedy_central_mtvnservices_com_path_ping2.txt
Raw
valve_path_ping
11/4/2014 - 7:30 PM Pacific
Tracing route to eat.valve.net [192.69.96.1]
over a maximum of 30 hops:
0 SamwellBlue.lan [192.168.11.124]
1 OpenWrt.lan [192.168.11.1]
2 10.6.44.1
3 ip68-4-12-20.oc.oc.cox.net [68.4.12.20]
4 ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
5 68.1.5.137
6 xe-9-0-3.edge2.LosAngeles9.Level3.net [4.53.230.221]
7 4.68.105.13
8 4.68.105.13
9 eat.valve.net [192.69.96.1]
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 SamwellBlue.lan [192.168.11.124]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% OpenWrt.lan [192.168.11.1]
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% 10.6.44.1
0/ 100 = 0% |
3 14ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-12-20.oc.oc.cox.net [68.4.12.20]
0/ 100 = 0% |
4 20ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
0/ 100 = 0% |
5 22ms 0/ 100 = 0% 0/ 100 = 0% 68.1.5.137
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% xe-9-0-3.edge2.LosAngeles9.Level3.net [4.53.230.221]
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 4.68.105.13
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 4.68.105.13
0/ 100 = 0% |
9 51ms 0/ 100 = 0% 0/ 100 = 0% eat.valve.net [192.69.96.1]
Trace complete.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment