1 Message
Latency Issues at regional Comcast nodes 10.22.113.2 and 96.216.209.1
Hi Comcast Support,
I’ve continued to experience irregular latency and spikes during normal internet use, especially while video conferencing. I've run multiple traceroutes and identified consistent issues occurring within your internal network. Here's a summary of recent findings:
Consistent problem nodes:
10.22.113.2 – often spikes between 200–350ms
96.216.209.1 – continues to show high latency and packet loss (previously spiked at 3440ms, now fluctuating between 289–347ms)
Latest traceroute to google.com (142.250.190.46) showed:
Moderate to severe jitter starting at hop 3
Spike behavior continuing through your regional routing
Latency bleeding into the Google network due to earlier instability
My home network is stable (low latency at hop 1), and I've rebooted my modem and router, which improved local performance, but these upstream issues remain.
I am happy to provide logs or additional trace results. I would greatly appreciate any action your team can take to address the performance on or around the affected nodes.
Thank you,
user_ryxmdc
jason_it
1 Message
14 days ago
Comcast - I am having similar issues. No latency across my LAN, but significant latency on the WAN.
This issue occurs regularly in the late afternoon and into the early evening.
Please advise.
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 40 byte packets
1 setup.ubnt.com (192.168.200.1) 5.395 ms 5.317 ms 3.463 ms
2 96.120.3.77 (96.120.3.77) 1107.650 ms 930.398 ms 987.853 ms
3 po-301-1209-rur01.ashleyriver.sc.chrlstn.comcast.net (96.110.122.9) 970.499 ms 1215.238 ms 1003.924 ms
4 be-15-rar01.charleston.sc.chrlstn.comcast.net (68.86.130.205) 635.625 ms 617.941 ms 695.541 ms
5 ae-50-ar02.southside.fl.jacksvil.comcast.net (68.87.164.125) 736.191 ms 689.425 ms 787.671 ms
6 c-50-149-168-110.hsd1.tn.comcast.net (50.149.168.110) 923.123 ms 715.344 ms 724.149 ms
7 one.one.one.one (1.1.1.1) 947.318 ms 838.654 ms 867.967 ms
64 bytes from 1.1.1.1: icmp_seq=0 ttl=58 time=1497.477 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=1430.786 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=1130.718 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=890.589 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=1365.615 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=58 time=1389.170 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=58 time=1239.279 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=58 time=1622.094 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=58 time=1596.580 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=58 time=1418.071 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=58 time=1098.270 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=58 time=894.506 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=58 time=1298.552 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=58 time=1288.939 ms
64 bytes from 1.1.1.1: icmp_seq=14 ttl=58 time=1388.511 ms
64 bytes from 1.1.1.1: icmp_seq=15 ttl=58 time=1069.802 ms
64 bytes from 1.1.1.1: icmp_seq=16 ttl=58 time=1440.432 ms
64 bytes from 1.1.1.1: icmp_seq=17 ttl=58 time=1080.956 ms
64 bytes from 1.1.1.1: icmp_seq=18 ttl=58 time=1016.302 ms
64 bytes from 1.1.1.1: icmp_seq=19 ttl=58 time=1452.007 ms
64 bytes from 1.1.1.1: icmp_seq=20 ttl=58 time=1888.333 ms
1
0
XfinityBenjaminM
Official Employee
•
2K Messages
13 days ago
Click "Sign In" if necessary
• Click the "Direct Message" icon (upper right corner of this page)
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
• Type your message in the text area near the bottom of the window
• Press Enter to send your message
0
0
EG
Expert
•
110.1K Messages
13 days ago
@user_ryxmdc @XfinityBenjaminM
Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.
0
0