Xfinity plant
Xfinity globe
Community Forum

Suddenly getting 20% packet loss

New Poster

Suddenly getting 20% packet loss

I live in central Illinois and I often stream to twitch. No problems at all since I upgraded my networking equipment a few months ago. I've restarted my equipment multiple times to no avail. I have a Netgear R6400 router and a Motorola MB8600 docsis 3.1 modem. When I stream to twitch I get 20%+ packet loss to their chicago server Live-ord.Twitch.TV. I've included a WinMTR to comcast.net and screenshots of my modems power levels. My twitch bitrate is set at 2000 kb/s. I contacted comcast and I have Upstream Signal Quality (SNR) 30.4 dB. Receive Power Level (upstream)(Dbmv) -0.1 dBmV. I have 100/10 service and I've been getting around 105/3 since having this problem. Its just my upload being affected it seems.

 

After factory resetting my modem I get these errors in the log:

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

No Ranging Response received - T3 time-out

TLV-11 - unrecognized OID

Started Unicast Maintenance Ranging - No Response received - T3 time-out

 

 

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
10.13.37.1 0 1933 1933 0 0 1 0
96.120.24.249 6 1607 1525 5 9 34 7
162.151.161.1 5 1615 1535 6 9 35 12
be-168-ar01.area4.il.chicago.comcast.net 6 1599 1515 12 15 41 13
be-33491-cr02.350ecermak.il.ibone.comcast.net 5 1619 1540 12 16 47 16
be-10305-cr02.newyork.ny.ibone.comcast.net 5 1627 1550 31 35 66 34
be-7922-ar03.ivyland.pa.panjde.comcast.net 5 1667 1600 33 36 66 35
ae100-ur12-d.newcastlerdc.de.panjde.comcast.net 6 1607 1525 34 38 69 40
urlrw01.cable.comcast.com 6 1587 1500 31 38 63 37

 

modem levels 1.JPGmodem levels 2.JPG

New Poster

Re: Suddenly getting 20% packet loss

Hey I live up in nw suburbs Chicago area and am getting the exact same thing. 1%-30% packet loss and t3 errors. 1000ping to my modem through my router and 0% loss. Comcast keeps insisting it's on my end. Yeah funny joke. Wanted to pop in so you're not the only one, but hope we can get this fixed.