I'v been experiencing short spurts of high latency recently and after a bit of troubleshooting I found that the first hop out has 60+ms response times.
I have only really noticed this at night as I'm usually working during the day but have been observing this behavior the last week between 7PM and 11PM
Note: most of my testing I have done from my router (Linksys WRT 1200AC) which is connected directly to the modem (Surfboard SB6183).
When in online games I see the latency spike upwards of 200-400ms when this happens and generally results in the game being unplayable for a second or two and then it starts working again for anywhere between a few seconds and 20ish minutes.
Example traceroute to a valve server (although the extreme latency isn't caught in this trace it still shows the first hop out over 50ms)
C:\>tracert 192.69.96.1
Tracing route to eat.valve.net [192.69.96.1]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms LINKSYS10265 [192.168.0.1]
2 56 ms 69 ms 68 ms 10.36.72.1
3 21 ms 63 ms 66 ms 100.127.66.6
4 9 ms 8 ms 10 ms 70.169.73.196
5 22 ms 21 ms 21 ms langbprj01-ae7.0.rd.la.cox.net [68.1.0.149]
6 77 ms 65 ms 66 ms te-0-5-0-3-pe02.600wseventh.ca.ibone.comcast.net
[173.167.57.109]
7 23 ms 23 ms 23 ms hu-0-5-0-1-cr02.losangeles.ca.ibone.comcast.net
[68.86.83.21]
8 * * * Request timed out.
9 39 ms 38 ms 38 ms be-10925-cr01.9greatoaks.ca.ibone.comcast.net [6
8.86.87.158]
10 58 ms 57 ms 57 ms be-12125-cr02.seattle.wa.ibone.comcast.net [68.8
6.85.197]
11 83 ms 97 ms 55 ms he-0-12-0-0-pe05.seattle.wa.ibone.comcast.net [6
8.86.84.54]
12 54 ms 54 ms 53 ms as32590-1-c.seattle.wa.ibone.comcast.net [66.208
.233.26]
13 * * * Request timed out.
14 * * * Request timed out.
15 50 ms 52 ms 51 ms eat.valve.net [192.69.96.1]
Trace complete.
Here are some screenshots of the testing from the router:
http://s13.postimg.org/ywfkh9aif/first_hop_out_latancy.png
http://s13.postimg.org/65e5dgfav/first_hop_out_latancy.png
http://s13.postimg.org/ywfkh9aif/first_hop_out_latancy.png
http://s15.postimg.org/5qzj9yb4r/first_hop_out_latancy.png
Channel status:
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 49 813000000 Hz 0.3 dBmV 40.9 dB 0 0
2 Locked QAM256 50 819000000 Hz 0.7 dBmV 41.2 dB 0 0
3 Locked QAM256 51 825000000 Hz 0.1 dBmV 40.7 dB 0 0
4 Locked QAM256 52 831000000 Hz 0.3 dBmV 41.0 dB 0 0
5 Locked QAM256 53 837000000 Hz -0.1 dBmV 40.7 dB 0 0
6 Locked QAM256 54 843000000 Hz -0.2 dBmV 40.2 dB 0 0
7 Locked QAM256 55 849000000 Hz 0.0 dBmV 41.0 dB 0 0
8 Locked QAM256 56 855000000 Hz -0.3 dBmV 40.5 dB 0 0
9 Locked QAM256 65 909000000 Hz -3.2 dBmV 40.0 dB 0 0
10 Locked QAM256 66 915000000 Hz -3.2 dBmV 39.9 dB 0 0
11 Locked QAM256 67 921000000 Hz -3.3 dBmV 39.9 dB 0 0
12 Locked QAM256 68 927000000 Hz -3.1 dBmV 39.9 dB 0 0
13 Locked QAM256 69 933000000 Hz -3.2 dBmV 39.9 dB 0 0
14 Locked QAM256 70 939000000 Hz -3.4 dBmV 39.8 dB 0 0
15 Locked QAM256 71 945000000 Hz -3.1 dBmV 39.9 dB 0 0
16 Locked QAM256 72 951000000 Hz -3.7 dBmV 39.6 dB 0 0
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 23300000 Hz 35.5 dBmV
2 Locked TDMA and ATDMA 1 2560 Ksym/sec 18400000 Hz 35.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 29800000 Hz 37.0 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 39.0 dBmV
I'v got a tech scheduled to come out day after tomorrow so I'll post again with any findings.
- Kevin
↧