Quantcast
Viewing all articles
Browse latest Browse all 4291

Packet Loss / Choke Timewarner

For about a week now I have been experiencing a lag spike at one minute intervals at lasts about 2-4 seconds and spikes as high as 1500ms ping and as low as 900ms. It really only affects real time PC games like League of Legends.

Details:
Location: Orono, ME. 04473. In a house with multiple apartments. TWC the only real provider in the area.
Provider: Timewarner Cable, just internet, Extreme Package 30↓ 5↑
Router/Modem: Netgear C3700 Cable Modem Router
Connection: Amped Wireless PCI20E High Power AC1200 Wi-Fi PCI-E Adapter


Event Logs:
1970-1-1, 00:00:29.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:32.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2015-5-30, 13:32:57.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:14:f1:e8:48:9f;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:30.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:14:f1:e8:48:9f;CM-QOS=1.0;CM-VER=3.0;
2015-5-30, 20:36:22.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:14:f1:e8:48:9f;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:30.0 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:32.0 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:36.0 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:14:f1:e8:48:9f;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:41.0 Notice (6) Honoring MDD; IP provisioning mode = IPv4
1970-1-1, 00:00:43.0 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:14:f1:e8:48:9f;CM-QOS=1.0;CM-VER=3.0;
2015-5-30, 22:52:43.0 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:14:f1:e8:48:9f;CM-QOS=1.1;CM-VER=3.0;
2015-5-30, 22:52:43.0 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:14:f1:e8:48:9f;CM-QOS=1.1;CM-VER=3.0;
2015-5-30, 22:53:26.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:fc:af:a6:78:ce;CMTS-MAC=00:14:f1:e8:48:9f;CM-QOS=1.1;CM-VER=3.0;

Upstream/Downstream:

Downstream Bonded Channels
Channel Modulation Frequency Power SNR Correct Uncorrect
1 QAM256 633000000 Hz -3.2 dBmV 38.7 dB 16 0
2 QAM256 615000000 Hz -1.6 dBmV 39.4 dB 6 0
3 QAM256 621000000 Hz -1.7 dBmV 39.1 dB 10 0
4 QAM256 627000000 Hz -2.5 dBmV 39 dB 8 0
5 Unknown 0 Hz 0.0 dBmV 0.0 dB 0 0
6 Unknown 0 Hz 0.0 dBmV 0.0 dB 0 0
7 Unknown 0 Hz 0.0 dBmV 0.0 dB 0 0
8 Unknown 0 Hz 0.0 dBmV 0.0 dB 0 0
Upstream Bonded Channels
Channel US Channel Type Channel ID Symbol Rate Frequency Power
1 2560 Ksym/sec 21900000 Hz 36 dBmV 21900000 Hz 36 dBmV
2 2560 Ksym/sec 25100000 Hz 36 dBmV 25100000 Hz 36 dBmV
3 2560 Ksym/sec 32800000 Hz 37.5 dBmV 32800000 Hz 37.5 dBmV
4 2560 Ksym/sec 36000000 Hz 39 dBmV 36000000 Hz 39 dBmV

Ping Test of North American League Servers

tracert 192.64.170.252
Tracing route to 192.64.170.252 over a maximum of 30 hops
1 5 ms 5 ms 2 ms 192.168.0.1
2 13 ms 11 ms 15 ms 142.254.208.233
3 9 ms 10 ms 10 ms ten1-2-1-501.bngrmebc-rtr001.ne.northeast.rr.com
[24.31.157.8]
4 13 ms 12 ms 14 ms 204.210.69.20
5 62 ms 33 ms 37 ms 24.58.49.104
6 39 ms 35 ms 35 ms be25.albynyyf01r.northeast.rr.com [24.58.32.64]
7 32 ms 31 ms 31 ms bu-ether36.nycmny837aw-bcr00.tbone.rr.com [107.1
4.19.100]
8 35 ms 38 ms 30 ms 0.ae1.pr1.nyc20.tbone.rr.com [107.14.17.218]
9 52 ms 37 ms 34 ms 66.109.7.42
10 34 ms 31 ms 31 ms ae8.cr1.lga5.us.zip.zayo.com [64.125.26.161]
11 * 33 ms 30 ms ae10.mpr3.lga7.us.zip.zayo.com [64.125.20.77]
12 35 ms 30 ms 29 ms 128.177.169.158.IPYX-089814-970-ZYO.zip.zayo.com
[128.177.169.158]
13 35 ms 35 ms 31 ms 104.160.132.44
14 56 ms 48 ms 51 ms 104.160.159.14
15 104 ms 98 ms 98 ms 104.160.159.11
16 117 ms 126 ms 117 ms 104.160.159.2
17 116 ms 106 ms 107 ms 104.160.159.1
18 107 ms 109 ms 108 ms 104.160.128.103
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.

In-Game test of Lag intervals (using in-game time as a marker)

1. 1:55
2. 2:49
3. 3:51
4. 4:50
5. 5:48
6. 6:47
7. 7:47
8. 9:48
9. 10:46
10. 12:47
11. 13:46
12. 14:48
13. 15:46
14. 16:47
15. 18:47
16. 19:47

Out of a 20 minute game, 16 events occurred with about an average of once per minute. There were three instances of no lag around the 45-50 second mark of the minute but this could be due to human error only one instance I can guarantee was not error and no event present. This test has been repeated to the same extent, the time varies but the interval does not; usually every minute.

Wireless does not make a difference, I have tested my connection with an ethernet cable and I still get the same lag event with no real sign of change.

Viewing all articles
Browse latest Browse all 4291

Trending Articles