Index Lock Status Frequency SNR Power Modulation
|555 MHz||561 MHz||567 MHz||573 MHz||579 MHz||585 MHz||591 MHz||597 MHz||603 MHz||609 MHz||615 MHz||621 MHz||627 MHz||633 MHz||639 MHz||645 MHz|
|40.1 dB||40.0 dB||39.8 dB||39.9 dB||39.9 dB||39.8 dB||39.7 dB||39.9 dB||39.9 dB||39.6 dB||39.6 dB||39.9 dB||39.4 dB||39.5 dB||39.3 dB||39.9 dB|
|0.7 dBmV||0.5 dBmV||0.0 dBmV||0.2 dBmV||0.2 dBmV||-0.1 dBmV||-0.3 dBmV||0.0 dBmV||-0.2 dBmV||-0.7 dBmV||-0.5 dBmV||0.2 dBmV||-0.4 dBmV||-0.7 dBmV||-0.3 dBmV||0.2 dBmV|
|256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM||256 QAM|
Upstream Channel Bonding Value Index Lock Status Frequency Symbol Rate Power Level Modulation Channel ID
|24.2 MHz||19.4 MHz||30.6 MHz||37.0 MHz|
|5120 Ksym/sec||2560 Ksym/sec||5120 Ksym/sec||2560 Ksym/sec|
|41.5 dBmV||41.3 dBmV||42.8 dBmV||44.5 dBmV|
CM Error Codewords Unerrored Codewords Correctable Codewords Uncorrectable Codewords
Up and down levels are both within the desired range. You can see that the modem's downstream error counters were reset to zero, which makes it impossible to see what is really taking place on the trunk cable. This often happens when you cycle power to the modem, so DON'T DO THAT! Capture and post the signal level page again after at least 12 hours.
At that time you should expect to see a few hundred corrected errors on each channel, but only a few uncorrectibles. Neither should increase much after the first 12 hours, when the modem "trains" and adjusts itself to the incoming DS signal levels. If uncorrectible errors greatly exceed correcteds, that usually points to ingress, which is signals or noise leaking into the cable system from the outside world. Corrected errors won't usually affect 'ping' times, but uncorrected errrors will add up quickly and increase network delays.
What do you honestly think the problem is? The modem? It's still the same ISP so shouldn't my routing to the game server be the exact same as before?
Nope. Nothing is guaranteed when any equipment is switched especially if you switched from TWC to Spectrum... Switching to higher speeds seems to increase gaming woes as well.
Well just a quick update for anyone who ends up with this problem as well. I returned the technicolor modem that spectrum had sent me, and got a ubee modem instead (I was using a ubee modem previously). Luckily my ping has dropped back to normal. I'm not sure if it's because of the new IP that it gave me, or if it was specifically the modem. Either way, I prefer the ubee modem because the web config has way more options!
On a side note, I noticed that even though I am located in New York, i ping lower to tests based in Chicago now with this modem. With the technicolor modem I was pinging lower to tests based in New York. Previously I was getting 16ms to the speedtests in New York, and now that has increased to 36-40, however my ping to Chicago and the west coast has dropped by about 16-20. Is that strange? it because my new ip has new routing? Or...does that not make any sense at all?
yes, makes sense, You need to compare tracert's and where the actual speedtests are going and how they're getting there. . It's why the only real benchmark is to use TWC's speedtest that goes to a server at the nearest TWC RDC(where the DNS is co located...)
the 5 I know of are in Columbus, Oh, Atlanta, NYC, Dallas and LA
Mine still shows Columbus and I'm back up to 22,3 down, 2,21 Up