Another packet loss and ping spike issue
Does this seem like an oversaturated node issue? Im in Norfolk, VA where Cox has zero competition and for the past month my internet has been trash. I pay for cox gigablast and the speed tests are fi...
Forum Discussion
allanIve had three tech come out so far. The first tech was certain my line from the tap to my house was bad and he said it was at least 10 years old and from before COX switched to digital, tested it and confirmed that the line needed to be replaced. Second tech came out (pissed he was going to have to do his job) and then he claimed the line was fine so he left. Third tech was just here today, she did a bit more than the second tech but claimed the line was fine, said there was some work in the area recently and my problems are probably resolved (theyre not). She told me that she was going to talk to her supervisor and try to get in touch with the first tech and try to get the work scheduled. I pay the extra $10 a month for Cox complete care. Idc at this point bc if anything I want the old line replaced to at least rule that out since nobody ahs been able to tell me what the problem is except the first guy that seemed quite confident in his diagnosis.
Picture is as Im typing this at 10:36pm EST, 7 hours after the tech told me everything is working properly
@Scoomas, I recommend reaching out to us via email at cox.help@cox.com so we can take a closer look at this issue for you. -Allan, Cox Support Forums Moderator.
Noted. I will email cox support again and schedule a tech to come out for a 5th time
Those pictures were screenshot around 6:30PM after the internet has been fine all day long. Now that its in the evening and more people are home, the connection goes to ***. How is that anything other than node congestion?
Also got the advanced support tech to admit that it sounds like node congestion. I guess that's a start on the right direction
scoomas Did you ever get a solid answer on this? I haven't had connection issues for the past few days and I'm curious if it turned out to be node congestion like you had guessed.
