jitter

9 Topics

Packet loss, help explain these graphs (thank you!)
I am having a packet loss issue, I recently downloaded PingPlotter and have taken some IP's of servers that I game on (I hope I did it right). I am looking to get some insight into what these charts mean and if there is anything I can personally do about it. I have 500d and 10u; late-night gamer (Fortnite, CSGO, Warzone, Halo, etc.): Here is what I have taken from Google, Fortnite, and Akamai. Google: https://imgur.com/a/zcrGGb0 Fortnite (NA-West): https://imgur.com/d9qY3T3 Akamai: https://imgur.com/qm0q3Qd
se6astian
4 years ago Place Internet
500Views
0likes
1Comment
as awful as cox's service is, packet loss / ping spikes cant be exclusively blamed on them (outages though)
i think this website should be stickied at the top of the forum with the others https://www.badmodems.com/ start at the 'whats the issue?' page the amount of modems / gateways out there with the intel puma 5/6/7 is unreal. i actually upgraded from one intel puma to another. i didnt start seeing real stable, consistent internet until i migrated to a broadcom chipset based modem. if youre really too lazy to read the link. millions and millions of modems out in the wild feature a chipset by intel named the puma that is absolute dog water for any type of jitter or latency sensitive application. the chance that youre on one right now is pretty high.
roomonfirethisi
5 years ago Place Internet
343Views
0likes
0Comments
Lots of Jitter, Tons of Packet Loss
Hey there! I have been having severe packet loss and lag in games lately and noticed my ping spiking quite a bit. I contacted Cox, and I was told everything looked fine on my end and the node in my neighborhood was overloaded because of COVID. I had a tech come out about a month ago and he reiterated the overloaded node issue and installed an attenuator on our line. I followed up with COX about a week ago and they sent out a supervisor who just knocked on the door, said the same thing about the overloaded node, and left. Didn't make any changes or attempt to do any diagnostics. They said they split my node on Friday, but I am still seeing a lot of issues. I just ran some of my own diagnostics and found some interesting info. I ran pingplotter and MTR on Google and EAs servers (I mostly play Apex Legends). I discussed the results with some more technical friends who believe it might not just be a local issue but rather peering congestion between COX and Zayo. Please see the images below. https://ibb.co/ThD2R7Z https://ibb.co/ysC10pt https://ibb.co/BsY2G3Z https://ibb.co/8BH34rC We have Gigablast and have just upgraded both our modem and router. I am kind of lost with what to do currently. I have seen people file FCC complaints with some success. But certain applications are just unusable with the jitter and packet loss I am getting. Thank you!
corb3421
5 years ago Place Internet
2.5KViews
0likes
7Comments
Upstream packet loss and jitter
We're experiencing latency spikes and packet loss throughout the day. It appears to be upstream based on testing I've done so far. All the details are below. It comes and goes suddenly and seemingly at random, and does tend to fade away during the night as if it were congestion. Had a tech come out, he just left. Said he checked the line all the way from the modem to the tap and the signals were all excellent. Once he reconnected the service I could immediately see high jitter and packet loss in PingPlotter. He said there's not much we can do since the signals are all good. We have the Panoramic WiFi Gateway. The modem was originally bridged, but I factory reset it in an attempt to debug this issue -- didn't help. Jitter and packet loss is seen simultaneously by two desktops wired directly into the modem (well, through a wall). I recently saw the modem reboot itself on its own when the issue was happening. Not sure if related. I've been running PingPlotter for a few days against the following targets: Google DNS (8.8.8.8) CloudFlare DNS (1.1.1.1) The default gateway assigned to my modem (resolves to ipxx-xxx-xx-x.ph.ph.cox.net) The modem itself (192.168.1.1) The jitter spikes and packet loss occur simultaneously in all of these targets except for the modem itself which remains stable. I will attach plenty of screenshots at the end of this post. When analyzing results from Google or CloudFlare in PingPlotter, I see the same thing many others on these forums have seen: The first hop is the modem (192.168.1.1) with no issues. The second hop is a private IP that is likely the CMTS (10.97.32.1). Continuous packet loss always begins here. The default gateway (that IP which resolves to ipxx-xxx-xx-x.ph.ph.cox.net) shows the same packet loss but does not have any intermediary hops like the CMTS. I've also been running basic tests with packetlosstest.com and have been able to reliably correlate those results to the packet loss shown in PingPlotter. According to packetlosstest.com the loss is only upstream. I've performed dozens of tests and I have only ever seen upstream packet loss. During the worst times I've had speed tests show nearly 0.1 Mbps upload. The download was also poor, but speedtest.net uses TCP so that's not necessarily an issue. See screenshot further below. This can get extremely disruptive of any online activities that require stability, especially VoIP and live screen sharing. I usually have to tether my phone and use expensive LTE to do some of these tasks. If it can be looked into or if we can get any advice on how to proceed, we would highly appreciate it! Now for some screenshots... PingPlotter 24h Summary: Please ignore the red block towards the end, that was the technician doing his work. You can see the 24 hour pattern here. It seems to follow a congestion pattern, though I've also experienced this issue as late as 2-3am several times (haven't caught it that late on PingPlotter yet). PingPlotter to CloudFlare: Just an example showing continuous PL starting at the famous second hop (CMTS) for a regular web connection. It's the same exact story across all target websites. Packet Loss Test: This is one of many examples of packetlosstest.com showing upstream packet loss. The activity on the right from PingPlotter occurred during the test and correlates with the packet loss seen in the test. The order of targets in PingPlotter are different and there's more, but the top timeline graph is still the modem and the rest include the same targets as above. PingPlotter (while I was typing up this post): I was going to look for a time to zoom in on where it goes from decent to bad very suddenly, and I didn't need to look for one as it started happening right then and there. If I was on a voice call, sharing my screen, or playing an online game right now, I'd be having a very rough time. I ran packetlosstest.com shortly after but it had calmed down by then, still showed 1.7% though. Speed Test: I got lucky with this one since the packet loss comes and goes very quickly and it's hard to capture in some tests without blowing 20 minutes doing them repeatedly. It slowed down this speed test to such an extent that my 300/30 Mbps connection became this. The next speed test was a lot better. This was on Feb 20 long before I began monitoring with PingPlotter. I will try to reproduce in the future and correlate with PingPlotter. Modem upstream: The tech said all the signals were excellent so I'm not really concerned with it being an issue on my end. Downstream signals have been steady all this time with SNR always at least 35 dB and usually in the 40-41 range. Power levels have also been good, well within -5 and 5 dBmV. Here's upstream: There are "uncorrectable codewords" on the modem, but these only appeared after the technician came and disconnected service for his testing. Before that, there were 0 uncorrectables. I'm not sure if that could have caused them, so I'll include this image just in case.
wildbailey
5 years ago Place Internet
3.7KViews
0likes
7Comments
Packet loss and jitter so bad I can't even work from home
This issue seems to be getting worse and worse with time. It started a few months ago, occasional missed ping/packet, small ping spikes every once in a while, but over time the issue is getting worse. As I am typing now I am seeing 26% packet loss, and the pings that do come back are for the most part well over 100ms, sometimes even greater than 200. A few times a day the connection is going down completely for anywhere from 10 min to a half hour at a time. I'm trying to work from home, but I have to keep refreshing web pages for them to actually load half the time, I can't use my virtual softphone through my desktop to make calls, and I have a very important Zoom call this afternoon which I am confident I won't be able to participate in now. For some background, here is my setup and how I have tested. I am using a desktop PC with a direct wired connection to my router. Using an SB8200 modem which I just bought 2 weeks ago hoping the modem was the issue (it wasn't). I have verified the router is not the issue, as I have tested by plugging my PC directly into the modem and rebooting the modem. Even after the modem boots up and my PC connects to the internet, I still see the abhorrent ping times and packet loss. I did have a Cox technician come a week ago who was very courteous. He replaced the coax connections from the modem to the demarcation point as a precaution, despite his tests showing that part of the connection was fine. However when he ran a test from the box in the street out to a server on the internet, his tool indicated high jitter and packet loss. He said he would pass the issue up to a higher level engineering team, but I haven't heard back from Cox at all if the issue is being looked at, identified, or addressed. I know others around me have been having similar issues. How can I find out if something is going to be fixed if it is at this higher level? Making it so I can't do my job is a fairly significant impact, and if Cox isn't going to fix this issue, can I at least be allowed to cancel my internet plan without paying a fee? I need to switch to an ISP with a stable connection. I can't withstand going through the online live chat or phone call support anymore. They are nice and well-intentioned, but I know they can't help with what is clearly an issue at a higher level. The link below shows what I am currently seeing with my ping loss, jitter, and the traceroutes I have performed indicating the issue seems to be happening at the neighborhood level. https://imgur.com/a/hfwiEC9
Veze1000
5 years ago Place Internet
5.6KViews
0likes
10Comments
Packet Loss langbprj01-ae1.rd.la.cox.net
https://ibb.co/NZPBsQv Howdy! I've been doing several mtrs in the past 30 days from our network to meet.google.com, Zoom, and 8.8.8.8 and I'm getting packet loss & jitter. I am using a Cox Gigablast Modem, connected to Cox Orange County, speedtest.cox.com is yielding a whopping 960Mbps down and 30Mbps up, I am directly connected to the cable modem via ethernet, my wifi is turned off, and I get packet loss averaging 1.8% and as high as 5% (which cuts my video and audio calls at home during the pandemic). Could you please offer some advice? This seems to be the offending gateway: langbprj01-ae1.rd.la.cox.net - 1.8% Packet Loss
Solved
trabuco
5 years ago Place Internet
2.5KViews
0likes
4Comments
High packet loss, extremely slow speeds, and modem errors
Hello! As of a few days ago after I have recently purchased an aftermarket modem (Netgear cm600) I have noticed that at during certain times of the day the connection of the internet will just drop incredibly low and will pertain for quite a few hours. I have always had high ping on one game abnormally named League of Legends, where I usually sit at 78-85 ping which instead should be 50-55 ping. That's not really the issue as of right now though, as I end up having about 92 ping on the game whenever this happens but on top of that I end up dealing with 15-25% packet loss which is extremely detrimental and makes the game feel like I'm playing on 300 ping. From just general research on the internet of where people have had similar problems, I've seen that sometimes the registration processes just haven't been fully done which would be generally possible since this router has just been registered recently. There is also the possibility that the line near my house is faulty and needs to be updated, but other than that I guess that would be up to you guys to figure out. If I could nip this in the butt and to also possibly figure out why I am not getting the ping I should be getting in my video games I would greatly appreciate that. I'd like to for sure figure out why I am dealing with this packet loss though as this is extremely detrimental. I can't surf the internet without pages taking a long time to load and my games feel torturous. Here are my modem logs ever since I have received it. 2020-05-11, 13:08:25 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-11, 11:48:31 Warning (5) Unicast DSID PSN startup error 2020-05-11, 11:46:05 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-11, 11:37:30 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-11, 11:36:25 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-11, 11:36:11 Notice (6) TLV-11 - unrecognized OID;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-10, 12:50:01 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-06, 23:10:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-05, 16:04:53 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-04, 14:12:10 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-04, 14:10:12 Critical (3) Resetting the cable modem due to docsDevResetNow 2020-05-04, 14:09:39 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2020-05-04, 14:06:55 Critical (3) Resetting the cable modem due to docsDevResetNow 2020-05-03, 16:56:12 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; 2019-06-02, 15:16:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=redacted;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Vecxy
5 years ago Place Internet
717Views
0likes
1Comment
Why have your prices climbed when your service is unusable?
Your prices have climbed so high. We have had cox for a long time like 10+ years, and your prices have only gotten higher while your service has degraded. I had problems with latency, ping, and jitter even before corona. I got tired of doing the run around, but its so sad that with all the revenue from overselling your Nodes and hiking prices; the company was never able to upgrade their infrastructure. A lot of people are filing FCC complaints, and I hope it does something ( I doubt it.) I cant even go to class without getting Packet loss. Its futile. The worst part is, the company is policing the threads, and we cant even voice our concern. I understand its your company, but its OUR money that your taking. You are liable to delivering that service.
MakeMoreNodes
6 years ago Place Internet
653Views
1like
2Comments
High Pings and Jitters along with Packet Loss
Hi all, I have been having high pings and large packet loss every single day for the past 2 months (before the COVID-19 outbreak), and have had bufferbloat every time I connect to wifi. I thought the problem was with the Ethernet and hence bought a new wire to test yet this problem persisted. The following is my trace route to google: Tracing route to www.google.com [2607:f8b0:4007:804::2004] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 2600:8800:802:900:120c:6bff:fe78:2352 2 56 ms 52 ms 39 ms 2600:8800:87f:ffff::1111 3 * 12 ms * 2001:578:801:fffc::e 4 202 ms 38 ms 77 ms 2001:578:800:4:9800::2 5 33 ms 55 ms * 2001:578:1:0:172:17:249:33 6 49 ms 39 ms 26 ms 2001:4860:1:1::131a 7 34 ms 59 ms 26 ms 2607:f8b0:820d::1 8 29 ms 31 ms 38 ms 2001:4860:0:110f::1 9 31 ms 28 ms 25 ms 2001:4860:0:110f::13 10 24 ms 43 ms 37 ms 2001:4860::c:4000:de3c 11 * 30 ms * 2001:4860::9:4000:de3b 12 23 ms 72 ms 67 ms 2001:4860:0:1::1039 13 26 ms 44 ms 35 ms lax28s15-in-x04.1e100.net [2607:f8b0:4007:804::2004] Trace complete. The third hop almost always times out and I have no idea why. Please let me know what I can do, I have tried everything contacted all technicians but they have not been able to figure out anything. I currently use a 150mbps residential connection with a Netgear C6250 router modem.
sahilp
6 years ago Place Internet
1.4KViews
0likes
1Comment