Dropped packets on ibone.comcast.net nodes.

So, I found this thread https://forums.xfinity.com/conversations/your-home-network/dropped-packets-on-ibonecomcastnet-nodes/62e022196f170a2f7efb6b82 that is closed, talking about the very issue I am seeing.

I have mtrs that are showing a lot of packet lose on the ibone.comcast.net nodes. I also experience issues with conference calls because of it and gaming lag times are all over the place from it too. I have two homes that use Xfinity and can confirm that it is happening from both locations but exiting at different ibone.comcast.net nodes.

The other piece of knowledge that I can add is it is only impacting traffic that is going through these nodes and not all traffic goes through these nodes. For instance if you were going to google.com you don't exit via one of those ibone.comcast.net nodes but if you were to go to say Chime (conference tech my company uses) or Battle.net it does route through these ibone.comcast.net nodes and you'll see the packet loss/lag.

My guess is that comcast is over subscribed at this layer and there is nothing they are going to do about it in the foreseeable future. However, I wanted to at least state that I am seeing this issue and would like to see if I am the only one :).

The screen shoot below is from dual mtrs, started at the same time from two different hosts on the same network to google.com and battle.net. As you can see it has an issue with the last two ibone nodes while the other mtr runs clean. I know that icmp is the first to get dropped in favor routing high priority packets, that being said, the fact that I can correlate packet loss while at the same time having lagging/conference call issues kind of leans towards there being congestion that is larger than a "these packets are the first to go as we prioritize traffic to deliver the best quality internet experience to you" (not that anyone at comcast has said this to me, just getting it out of the way).