New Poster
•
4 Messages
Latency 500ms+ starting yesterday on gigabit tier
Background: I have a CM1000 which has been happily running since the first month of gigabit offerings in my area about 2 years ago. I have never had high latency, and beyond some intermittent outages the service has been fine (pricing and "usage fees" aside). I am a computer programmer and often work from home. Today I started noticing intermittent strange behavior from my devices - slow to connect to sites, hiccups in voip, etc.
The TLDR is the latency is just too high:
Pinging comcast.com [69.252.80.75] with 32 bytes of data:
Reply from 69.252.80.75: bytes=32 time=710ms TTL=55
Reply from 69.252.80.75: bytes=32 time=527ms TTL=55
Reply from 69.252.80.75: bytes=32 time=563ms TTL=55
Reply from 69.252.80.75: bytes=32 time=728ms TTL=55
Ping statistics for 69.252.80.75:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 527ms, Maximum = 728ms, Average = 632ms
From inside the house, there is no problem with the router, the cabling, or the LAN-side NIC in the CM1000:
Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Reply from 192.168.100.1: bytes=32 time<1ms TTL=63
Ping statistics for 192.168.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
I have checked my signal levels in the CM1000, and they appear to be fine:
|
|
I have checked the error logs on the CM1000, and there are 1-2 errors every 2 months or so, but very very rare.
Tracert to comcast.com shows same as ping:
Tracing route to comcast.com [69.252.80.75]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 465 ms 483 ms 530 ms cm-1-acr02.arvada.co.denver.comcast.net [96.120.12.169]
3 253 ms 271 ms 187 ms 96.110.242.193
4 95 ms 69 ms 83 ms ae-9-ar01.denver.co.denver.comcast.net [68.86.128.129]
5 367 ms 384 ms 448 ms be-33652-cr02.1601milehigh.co.ibone.comcast.net [68.86.92.121]
6 426 ms 345 ms 378 ms ae0-0-ar03-d.cmc.co.ndcwest.comcast.net [68.86.90.74]
7 428 ms 453 ms 426 ms be-10-ur25-d.cmc.co.ndcwest.comcast.net [68.86.132.26]
8 291 ms 375 ms 397 ms po-5-sw303a-d.cmc.co.ndcwest.comcast.net [162.151.85.194]
9 413 ms 371 ms 319 ms urlrw01.cable.comcast.com [69.252.80.75]
Trace complete.
I feel like the problem is really just comcast here. What can I do to resolve the problem? I know that speaking to a rep on the phone will just yield "speeds show fine" which they do, if you ignore the insane latency it takes to rev up to the eventual data flow.
puargs
New Poster
•
4 Messages
6 years ago
I should note that I did try resetting the modem several times (as well as the rest of my internal network). I also tried leaving it off for a few hours and starting it back up.
Tomorrow I will go and purchase a new modem from a local retailer to see if it resolves the issue.
0
0
puargs
New Poster
•
4 Messages
6 years ago
0
0
EG
Expert
•
111.7K Messages
6 years ago
FWIW, if this Is this with a WiFi connection, for a test, see if a computer hardwired directly to the router / gateway device with an ethernet cable has the same problem if it comes back.
0
0
puargs
New Poster
•
4 Messages
6 years ago
Just as a note, the problem was present on both ethernet and wifi last night. I have a large wired 10/100/1000 switch with a 48 Gbps backplane, and a managed commercial AC wireless system. There were no issues pinging the router or CM1000 internally from the network on either wired or wireless, and no issues communicating between devices on the house's intranet.
At this point I have to conclude the issue was on Comcast's end. To their credit, it seems the issue was resolved on Friday night possibly due to routine maintenance or equipment reboots. I will report back in a week to see if the problem stays gone.
0
0