1 Message
be-36041-cs04.1601milehigh.co.ibone.comcast.net hop failing
Hop in the title has been dropping packets and failing the past two to three weeks. I have constant performance and disconnection issues even after extensive troubleshooting on my end. All hops leading up to that one work perfectly fine but as soon as traffic has to traverse that node, it's a 50/50 on if it actually makes it or not. After some routing tests, it looks like that hop is used anytime traffic needs to exit the Denver Metropolitan Area. It also looks like this has been the case since 2021 according to a quick Google search as well so I'm not sure how a failure like this hasn't been rectified yet.
XfinityBrianH
Official Employee
•
947 Messages
4 months ago
0
0
EG
Expert
•
107.1K Messages
4 months ago
The concern is not "accessibility / disability" help related.............................. Topic moved here to the proper help section for assistance.
0
0
Wilbos
11 Messages
4 months ago
The same issue is being reported on Seattle, Sacramento, Memphis, and Atlanta servers in the past week alone. There has been no fixes or resolutions and customer service refuses to escalate the issue.
0
0
Nebby5k
1 Message
16 days ago
Same issues here. Specifically with be-36121-cs02.seattle.wa.ibone.comcast.net (IP= 68.86.93.5). Getting pretty sick of this (has been going on for 6 months now). Makes some games unplayable when the server hops take me through this hub. Causes stutters in video calls and streaming movies. I have a few more months of patience until I am moving to Tmobile Home Internet.
EDIT: I actually did a long term ping plotter test while playing the game making time stamps of when I noticed lag and it coincides with packet loss on the test itself. Then I ran the results through chat GPT and the results show that only 60% of my actual packets are making it through the hop over a given amount of time.
(edited)
1
0