Forum Discussion
- Xearu5 years agoNew Contributor II
Did this, eventually led to a tech being sent out and find nothing out of the ordinary. The issue is intermittent and the tech doesn't stick around for too long, internet was disconnected for around 15 minutes each check so I assume around 10 minutes of that was hooked-up to his diagnostic tool. Tech would need to sit out here, monitor, and chart the data in real-time for the duration of the 2 hour visit window to see what Im seeing.
I'm not sure what other technical info is needed for this to get properly escalated. Attached picture has more info and also speedtests using Cox.coms speedtest. (https://www.cox.com/residential/support/internet/speedtest.html)"According to Cisco, jitter tolerance is as follows:
- Jitter should be below 30 ms.
- Packet loss shouldn’t be more than 1%.
- Network latency should not go over 150 ms. This is the latency in one direction meaning the round trip time (RTT) would be 300 ms.
These figures are best practices for maintaining quality of service (QoS)."
According to Cisco on what is considered acceptable jitter tolerance, I have a major issue.
IMPORTANT: pingplotter screenshots - the 12 hour scale is crunched so the jitter data gets averaged to make the graph fit. All of the Cox.com speedtests were run within a 10 minute window. Please read the notes next to the pingplotter screenshots for clarity.
https://imgur.com/lRTYwA6- KevinM25 years agoFormer Moderator
Xearu, can you please email PingPlotter results to us at cox.help@cox.com? Please also bypass your wireless router and perform the tests while hard-wired to the modem. -Kevin M. Cox Support Forum Moderator
- Xearu5 years agoNew Contributor II
I have already done this as directed by LisaH 11 days ago. Will resupply the info to cox.help.
Related Content
- 2 years ago
- 4 years ago
- 5 years ago
- 5 years ago