Didn't find what you were looking for?
We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.
Network congestion on Charter/Spectrum nodes upstream
Been dealing with this for the last three days. It gets noticeably worse in the afternoons and evenings. Connection is completely normal from 8am-12pm PT.
Ran a couple of tracert (see attached - google and cloudfare). They all seem to be related to charter/spectrum nodes in the 'middle' of the trace. Beginning/ending are just fine.
I live in the Los Angeles area.
Could anyone provide any feedback or advice?
Unfortunately, my 'evening job' is a content creator for online gaming and I'm unable to play competitively with this latency.
Answers
-
Hello @TeamZaimes
Welcome to our community! I'm sorry to hear about the latency issues. I was able to locate your account using your community registration. It looks like there is a technician visit scheduled tomorrow. If the technician isn't able to address the latency issues, definitely let us know.
0 -
Hi @Renee_T thank you for your response!
The technician came out and confirmed that the line connection was good. To be safe, he did also switch out the modem to a new one (Spectrum provided).
However, the latency issue still exists starting in the early afternoon (again, it's completely fine in the morning, it's just the afternoon-evening). I ran a tracert at 8am this morning to the google dns server 8.8.8.8 and everything looked great.
But it's awful again. And again, it seems to happen on the lag-3.hcr01vnnzca24.netops.charter.com [24.30.169.206] server.
Given this gets worse in the afternoon/evenings, I'm presuming this is network congestion?
If this is temporary or maintenance related, then I can wait it out. However, if this is going to be the new norm, I'll absolutely have to switch ISPs.
I don't know what the next troubleshooting step would be. The technician said his role is to just check things locally in the house. And everything looked fine at home.
0 -
No sweat! The endpoint RTT's account for the cumulative expediency by which all of the routers along the way are forwarding the echo requests to, and the echo replies back from the endpoint, regardless of the variable non-QoS ICMP reply heuristics (not to be confused with forwarding of same) of any of the routers along the way.
🔗
2 -
As @HT_Greenfield mentioned... the endpoint latency is showing good results there. (Last I looked at our metrics, Spectrum published averages were upper 20's in my market)
Forwarding is the priority of those hops, not ICMP ECHO requests.
And they are DNS servers... not game servers.
0 -
Have you checked in with the game's support to see if they have any troubleshooting guidance/tools. Have seen some companies have servers open for running diagnostics, looking glass tools, monitoring/reporting tools built into the clients… may be worth asking around.
Could be a return path issue you may not find just looking from your end. For example, Spectrum may path me out through Durham, but pathing pushed from their servers/ISP may come back through Myrtle Beach.
0


