1 edit | [Speed] intermittent latency spikes - Louisville, KYThe first time I noticed the issue was last week. Up till then when I notice things like netflix having to pause and rebuffer i just assumed it was because of high neighborhood traffic. But last week it started getting really bad. During the "events" any kind of streaming is impossible, as well as any gaming or latency sensitive traffic.
It usually occurs at night between 8pm and midnight (at least that's when I give up and go to bed) but sometimes spikes happen during the day.
Here is a sample ping to google from one of the bad latency events.
Reply from 173.194.75.147: bytes=32 time=95ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1849ms TTL=48
Reply from 173.194.75.147: bytes=32 time=45ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1796ms TTL=48
Reply from 173.194.75.147: bytes=32 time=67ms TTL=48
Reply from 173.194.75.147: bytes=32 time=161ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1219ms TTL=48
Reply from 173.194.75.147: bytes=32 time=41ms TTL=48
Reply from 173.194.75.147: bytes=32 time=198ms TTL=48
Reply from 173.194.75.147: bytes=32 time=685ms TTL=48
Reply from 173.194.75.147: bytes=32 time=278ms TTL=48
Reply from 173.194.75.147: bytes=32 time=65ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1057ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1832ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1793ms TTL=48
Reply from 173.194.75.147: bytes=32 time=47ms TTL=48
Reply from 173.194.75.147: bytes=32 time=60ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1343ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1752ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1265ms TTL=48
Reply from 173.194.75.147: bytes=32 time=2670ms TTL=48
Reply from 173.194.75.147: bytes=32 time=129ms TTL=48
Reply from 173.194.75.147: bytes=32 time=48ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1523ms TTL=48
Reply from 173.194.75.147: bytes=32 time=124ms TTL=48
Reply from 173.194.75.147: bytes=32 time=46ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1307ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=155ms TTL=48
Reply from 173.194.75.147: bytes=32 time=150ms TTL=48
Reply from 173.194.75.147: bytes=32 time=2103ms TTL=48
Reply from 173.194.75.147: bytes=32 time=74ms TTL=48
Reply from 173.194.75.147: bytes=32 time=2523ms TTL=48
Reply from 173.194.75.147: bytes=32 time=44ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1837ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1874ms TTL=48
Reply from 173.194.75.147: bytes=32 time=44ms TTL=48
Reply from 173.194.75.147: bytes=32 time=41ms TTL=48
Reply from 173.194.75.147: bytes=32 time=522ms TTL=48
Reply from 173.194.75.147: bytes=32 time=44ms TTL=48
Reply from 173.194.75.147: bytes=32 time=618ms TTL=48
Reply from 173.194.75.147: bytes=32 time=41ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=50ms TTL=48
Reply from 173.194.75.147: bytes=32 time=302ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1895ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1973ms TTL=48
Reply from 173.194.75.147: bytes=32 time=650ms TTL=48
Reply from 173.194.75.147: bytes=32 time=66ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Reply from 173.194.75.147: bytes=32 time=2113ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1568ms TTL=48
Reply from 173.194.75.147: bytes=32 time=240ms TTL=48
Reply from 173.194.75.147: bytes=32 time=3467ms TTL=48
Request timed out.
Reply from 173.194.75.147: bytes=32 time=517ms TTL=48
Reply from 173.194.75.147: bytes=32 time=114ms TTL=48
Reply from 173.194.75.147: bytes=32 time=2231ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1171ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1059ms TTL=48
Reply from 173.194.75.147: bytes=32 time=108ms TTL=48
Reply from 173.194.75.147: bytes=32 time=279ms TTL=48
Reply from 173.194.75.147: bytes=32 time=187ms TTL=48
Reply from 173.194.75.147: bytes=32 time=265ms TTL=48
Reply from 173.194.75.147: bytes=32 time=143ms TTL=48
Reply from 173.194.75.147: bytes=32 time=680ms TTL=48
Reply from 173.194.75.147: bytes=32 time=578ms TTL=48
Reply from 173.194.75.147: bytes=32 time=189ms TTL=48
Reply from 173.194.75.147: bytes=32 time=54ms TTL=48
Reply from 173.194.75.147: bytes=32 time=731ms TTL=48
Reply from 173.194.75.147: bytes=32 time=57ms TTL=48
Reply from 173.194.75.147: bytes=32 time=50ms TTL=48
Reply from 173.194.75.147: bytes=32 time=445ms TTL=48
Reply from 173.194.75.147: bytes=32 time=117ms TTL=48
Reply from 173.194.75.147: bytes=32 time=399ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1003ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1109ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=90ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1039ms TTL=48
Reply from 173.194.75.147: bytes=32 time=720ms TTL=48
Reply from 173.194.75.147: bytes=32 time=2323ms TTL=48
Reply from 173.194.75.147: bytes=32 time=56ms TTL=48
Reply from 173.194.75.147: bytes=32 time=2156ms TTL=48
Reply from 173.194.75.147: bytes=32 time=44ms TTL=48
Reply from 173.194.75.147: bytes=32 time=876ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=52ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1694ms TTL=48
Reply from 173.194.75.147: bytes=32 time=42ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1556ms TTL=48
Reply from 173.194.75.147: bytes=32 time=379ms TTL=48
Reply from 173.194.75.147: bytes=32 time=2230ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1858ms TTL=48
Reply from 173.194.75.147: bytes=32 time=42ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1846ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1855ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1834ms TTL=48
Reply from 173.194.75.147: bytes=32 time=41ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1839ms TTL=48
Reply from 173.194.75.147: bytes=32 time=43ms TTL=48
Reply from 173.194.75.147: bytes=32 time=1180ms TTL=48
Reply from 173.194.75.147: bytes=32 time=46ms TTL=48
Reply from 173.194.75.147: bytes=32 time=312ms TTL=48
Reply from 173.194.75.147: bytes=32 time=48ms TTL=48
Reply from 173.194.75.147: bytes=32 time=729ms TTL=48
Ping statistics for 173.194.75.147:
Packets: Sent = 166, Received = 162, Lost = 4 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 3467ms, Average = 685ms
As you can see the latency is spiking to 2000ms or more. (or dropping packets depending on which cable modem i use)
I contacted support and initially they sent a service tech out to look at it. He removed all splitters and what he referred to as a legacy channel blocker from the line so right now my line is basically a homerun, the cable from insight comes directly to the cable modem with nothing in between.
He also replaced my Motorola 6121 (my modem) with one of the insight "rental" ones (arris dg860A). At the time he said everything looked fine from his end.
To be fair changing to the new modem took the connection from 25-40% packet loss to 1% loss but with 2000 spikes in rtt. but both are practically the same in terms of usability.
The connection is still doing the same thing even after the cable change and modem change. I've called insight several times and they've scheduled another tech to come out Monday night but they all say variations of the same thing "the cable quality looks fine" or sometimes they'll say i have intermittent Signal noise on the line.
Any tips on what they can check next? it seems like the techs i'm talking to are running out of predefined answers and they really need to move it to the next level of support but it seems to be difficult to get that to happen. I called support again today when i was getting 2000-3000ms pings to google for a good 2 hours and they said everything looked fine on their end.
I've attached a ping plot of a ping to google from today where you can see its still spiking to 2000ms , even after a cable modem reboot.
In Summary:
Issue: high latency spikes on cable internet
Attempted solutions:
1.) rebooted cable modem and router
2.) made line to house a home run
3.) replaced cable modem
4.) tested ping problem exists from any computer on the network
5.) tried directly connecting computer to cable modem issue still persisted. (to rule out router issue)
I have a bad feeling that the tech is going to come out tommorow night and say everything looks fine again. |
|
| Please let me know how this turns out. I've been noticing the same latency issues, but I never get a reply of less than 90ms... I have an Arris router as well. I have the Insight Digital Telephone service, so I had to go with theirs...I live on the East-end of Louisville, Zip 40245...
I did have the 30.0 service but never realy got 30.0 speed as promised. So I've switched back to 20.0...I check my work connnection (which is downtown 40217) and it is always pretty good. |
|
| I notice the same thing been going on for months at 8 P.M. Sharp the latency skyrockets for 2-3 hours. I understand its prime time but its never an issue until 8 o clock rolls in.(zip 40245) |
|
| Well the ended up removing an old telephone box that was between where the cable line came in and my router (which apparently they don't use anymore) they also ran a new line from the neighborhood main and my house.
been running since yesterday morning a lot better, still some jitter on the pings but not 1000+ ms anymore.
Now i'm getting about 45 ms average ping to google with occasional jumps to 80 then go back to 45.
Probably about as good as its going to get unless they do a review of their routing process and find out whats causing that jitter. |
|
