10.61.x.y IP -- My Equipment or Xfinity's?

@user_0ef58c​ even though this wasn't a full cutout, I was able to screenshot my numbers during a latency spike/fluctuation which almost reached the point of disconnect. But I dont see anything alarming I don't think?

Also, interestingly, when I pulled up Xfinity at that time to look into downgrading deals out of curiosity from another thread, it said "channel(s)" are "impaired" as an outage notice. Hm. May just be related to some work they're trying for me but thought that was interesting.

The most consistent thing noticing today is that the latency spikes seem to start at the 10.61.x.x hop, which has the highest maximum latency out of all my hops (despite being the first one out of my house). Odd

@user_0ef58c​ Welp, the tech just left. The poor guy, he offered some potential things he could do--replace the drop etc.--all had already been done. Fortunately, I was having stream drops while he was there and had his supervisor, Matt, on the phone. We didn't see anything in the modem numbers etc.  even in the middle of a drop. 

Matt said he escalated this to the line supervisor and others. I begged him to emphasize the September work (I was unsure whether to focus on the 10.61.x.x hop because I don't want to complicate the main correlation, as far as I know the 10.61.x.x hop existed before the September work, but I for sure know the September work correlates with the start of my issue). He said my call will be on hold for now, ugh. But, he assured me the line supervisor/line people will be directly communicating with me, FINALLY, instead of Tech fellas having to be the middlemen for something out of their hand. Matt's only idea would be that it might be something at the plant, because he wasn't seeing issues in the neighborhood nor the node (then again, mine looks like there's no issues even though today it was oddly consistently about 30 minutes between each drop).

Hoping I hear from the line level people soon and that they don't give me the runaround. In the meantime, I will be testing the Tmobile home network. I have my doubts ha, but I need something that works.

@user_0ef58c​ He reappeared at my door haha. The supervisor, Matt, said that he spoke with the line supervisor people and that they are going to start to try to isolate the issue by checking the plant first and then each pole along the way to mine (I thought we had already opened a ticket for this, but it is what it is). Matt set up a tech appointment for next Sunday as a follow-up. While I like this, I don't like that it resulted back in Matt/tech folks being middlemen for the line/maintenance level people. I urged Matt to emphasize to the line folks that I would like an open line of communication with them. Again, I understand that not every situation warrants that, but when a customer has done their due diligence, and the tech folks have exhausted their ideas, why does maintenance/line get to be impervious to communication with customers? I hope Matt also emphasized that this started after the September work: though I support them trying to isolate the issue, that coincidence is just too glaring. Hopefully those things got communicated to the line folks, but having an open line of communication would guarantee that and also would allow me to collaborate with them and their monitoring data.

@user_0ef58c​ Sorry for the repeat replies, this should be the last one today. But a lot has happened--and they're separate events/relevant updates. I laid down to nap and woke up to some man in the house! (Lol, my husband let him in.) Finally, a line worker!! He had an upstream SNR chart, which apparently techs can't see, and fluctuations seemed to correspond with my latency spikes/cutouts!! Finally! Since the T3s didn't correspond, I am super happy to hear him agree with me and plan to tell his supervisor, Adam, that. The maintenance tech (Zach) seemed to take genuine interest in his job and a desire to "be the guy that solves" what has probably been an infamous issue for the local teams lol (it seems tech and line couldn't agree whose issue it was to handle). That's what I like to see. 

He is going to try to come out tomorrow or for sure Monday, preferably with multiple guys, to try to pinpoint where the noise is coming from. His biggest concern is that that likely wouldn't relate to the September work, and that after he isolates and solves the SNR issue, if the issue continues, they're kind of at a loss. Still, I am just happy to have a direct line of communication with someone who can actually address the issue; to have it clarified that the T3s aren't the primary concern--the latency spikes are; and to have something being done. Praying they can figure it out, and the 10.61.x.x device and September work aren't related, and that the SNR issue resolves the whole thing! Final update for the day, I promise haha. 

Edit: One frustrating thing though is this whole time, now over a month, tech folks--both local and corporate--made it clear they can't track specific incidents (i.e., when I said I could tell them exact times of the issues, they said that they can just see the number of t3 timeouts etc since the last modem reset). For weeks, including in this thread but elsewhere as well, I have been stressing how valuable it would be for me to share specific times with maintenance level people. Perhaps the delay was because Xfinity was focused on the t3 timeouts, but it was quite ironic to hear Zach ask me today if I could write down when the next drops happen so he can compare them with their chart--which for maintenance goes back 2 weeks!! The exact thing I've been wanting to collaborate with--and fortunately I already had exact times for the drops this morning so we immediately were able to collaborate and come up with the most likely hypothesis yet! I did get his number (not only because hes tall and handsome lol), so that we can have that open line of communication. Figured I'd mention the irony that, once Xfinity finally opened a line of communication with a maintenance tech, we immediately came up with our best hypothesis yet. Only reaffirms my suggestion that Xfinity adjust it's s.o.p. for customers who have done their due diligence and tech has exhausted their ideas.

I am / have been having the same issues. It is all Comcast - Natting the WAN link. Trace with a tool like PingPlotter - latency from my devices (wired / wireless to router) <4ms - Router to the 10.61.x.x spikes to 300-700MS.. multiplayer games freeze up for a second or two CONSTANTLY.  The next hop from the router used to be to the external interface (Public IP address) since the geniuses decides to change this - I have CONSTANT issues with (games, video freezing etc). GOOD LUCK trying to get someone on the phone that understands anything besides "let me send a test signal and reboot your modem). I have tried new (Comcast) "Gateways" - garbage. Upgraded to 10GB router and my own Motorola 2.5GB modem - same issue. ITS ALL COMCAST - and they could care less about it. All they want is to be able to say "BANDWIDTH is 1GB) - hey a Ferrari goes fast too - not much good if it keeps shutting off is it? COMCAST is  a joke - and they could care less about the stability of their network. QoS doesn't help, VLANS etc. I wish I had an alternative - I would jump at the chance to switch to pure internet instead of this unreliable overpriced, oversubscribed garbage.

@user_0ef58c​ Fortunately, Adam has been in continuous contact. His guys found something "significant" today and believe they have repaired it. He is not sure that it was the cause of my issue, but at least it's taken care of regardless heh. He says both they and I will monitor today and tomorrow (since they have off for Thanksgiving, of course), and then confirm whether it's fixed on Friday, or crosscheck our data if the issue is not fixed.