- last edited on by
RogersCorey
Could be any of the above.
Are you able to log into the modem itself and get the signal levels?
That will at least narrow down if its something more direct at the house.
Beyond that.. yes, could be an over saturation of more people on, etc..
I normally where I am can get OVER the 500mbps of my plan on regular speed tests during the day. Now struggle to pull 400? But there is a lot more people home. (and same situation, a lot of rogers subscribers, as bell only does 10mbps dsl here)
Could be even outside that though.. one of the more local nodes, etc.. having issues, or same thing over saturated.
Only way to really test that is.. you would need to see, for those games, where the servers are, and do some trace routes between you and that end point. That should see if/where the problem lays. Could be something even outside of rogers themselves and between rogers and the end server location.
@sukhwinder2392 wrote:
PS4 Packet Loss
I have 1gb down and 30mbps up...I have been getting packetloss, I have netgear xr500 router, which allows to connect to closer server, but even then i have packetloss. I have QOS on. For some reason I get high latency and packet loss..I dont understand why. I called yesterday and they restarted the modem but even then i have packetloss and the person kept saying make sure your ports forwarding are correct. but i have a open NAT.
So I dont know what to do.
Actually, enabling QoS (or any other forms of prioritization or traffic shaping) will likely make your situation worse, not better. You need to implement QoS carefully and prescriptively. Any time that you implement traffic prioritization, you are creating separate internal priority queues in your router and splitting network traffic across those queues. If the majority of traffic on your network is gaming (and/or from one computer) and if you have (for example) two internal priority queues, then you are effectively halving the number of available packet buffers... and if they overflow, you get packet loss. Secondly, if your QoS scheme implements some form of rate limiting, one of the ways that it does this (and force a network client to slow down transmission) is to intentionally drop network packets. Furthermore, once you start rate-limiting traffic, this will also force a network client to queue packets locally... and this will result in additional packet loss because network packets will get dropped when the local queues overflow.
QoS is meant to be used in times when your network is congested; when you need to implement controls to smartly manage traffic from multiple computers and multiple applications as it flows from a high-speed network to a lower-speed network and you do not have sufficient egress bandwidth. The only way to eliminate packet loss is to have sufficient end-to-end bandwidth and to over-engineer the network to eliminate constraints.
It's also unrealistic to demand network performance that is superior to the ones used in telerobotic surgery. That expectation is neither practical nor feasible on a service that is designed to meet the needs of the masses as cost-effectively as possible, and that is why residential Internet (from any provider) is best-effort only and does not offer any service level commitments. Rogers can and should take steps to minimize jitter and to eliminate large latency spikes (that are currently being introduced at the point where traffic is routed at the local node) but they cannot guarantee zero packet loss, especially when the Internet itself can only deliver traffic on a best-effort basis.
- last edited on by
RogersTony
Ping Plotter Packet Loss Help
Hey,
I was wondering if someone is able to help me diagnose my internet issues and what could be the problem, here are my ping plotter results, as you can see I have packet loss pinging from my Modem and the jitter seems to be unstable also, any help would be appreciated.
@Marando This looks like the same issue that all of us here have been seeing (to varying degrees) for the past few months. Fortunately, I am no longer seeing 8000 ms ping RTTs but when I ping 8.8.8.8, I still see regular latency spikes that vary from 20 to 150 ms... and on rare occasions, much more. One of the things that I do is perform simultaneous, timestamped ping tests (in two separate windows) to my CMTS router and to 8.8.8.8, and I note the results. Sometimes, the ping RTT to the first upstream router exceeds that of the corresponding ping all the way to Google's server, and that's indicative not only of the latency that is getting introduced at the network edge but also that the router is busy enough doing something that it cannot immediately respond to ICMP Echo Requests.
@Marando wrote:
Is there nothing that can be done to fix this?
I don't think so. This seems to be the new normal for now. I presume that the problem was caused by an upgrade and/or configuration change that should have "just worked" but clearly had an unexpected negative impact on network performance. Rogers hasn't confirmed or denied anything. They also have not publicly acknowledged the problem or promised to fix it... and they don't really need either to because this technically is not an outage and does not impact any of their other services. I would love to be in the room when they discuss this issue with their vendors.
Here are the results of my ping tests from earlier this afternoon:
To my CMTS router:
3600 packets transmitted, 3600 received, 0% packet loss, time 3604178ms
rtt min/avg/max/mdev = 4.205/21.422/176.413/17.944 ms
To 8.8.8.8:
3600 packets transmitted, 3600 received, 0% packet loss, time 3604122ms
rtt min/avg/max/mdev = 5.468/19.362/171.595/13.333 ms
Not a problem at all for the average Internet user. Ignite TV still works perfectly fine. MUCH better that it was before. However, not great if you are a gamer that needs consistent network performance.
@Marando the best thing you can do is determine if Bell's Fibre service is available, or soon to be, or look for DSL/VDLS service with Bell or one of the TPIAs. The TPIAs also have numerous customers complaining as well. The common denominator? Those particular customers are using Rogers network to access the TPIA services. The TPIA companies were supposed to tackle Rogers on this issue, but, interestingly, they've gone silent as well. So, no one outside of Rogers or the TPIAs knows what Rogers has been up to for the last three months that is causing this problem.
If you're looking for low latency, you're best bet outside of fibre is DSL or VDSL services. You can run that as a secondary service without any impact on the cable service. The tricky part is whether you might want to run a dual WAN router which can use both services, or keep the services separate so that you can game via DSL/VDSL.
@Marando wrote:
@Datalink @-G- , Appreciate the feedback,
I already looked into Bell Fibre how ever it isn't available at my address, Bell DSL is however but it is only 10 down and 1 up. It sucks that these are my only options.
Do you know if upgrading to ignite will have any affect, or is it basically the same thing?
No, switching to Ignite Internet will not make any difference. I am an Ignite TV customer, so I have Ignite Internet, and this issue affects me as well. As @Datalink mentioned, TPIA customers using the Rogers infrastructure are also impacted.
I would also advise sticking with the legacy Rogers Internet and the CODA modem.
I have contacted rogers to maybe swap out my modem so I am waiting to get the new Coda modem shipped, but I dont have high expectations, because Internet problems are very hard to track down the exact issue, but the fact that I am getting Packet Loss on the first IP ping means that the issue is either my Modem or Cables either inside or outside of my house correct?
Not necessarily. You'll get packet loss whenever you get an uncorrectable codeword error on your line. Packet loss can also be caused by congestion in your local node. (If you have a high bit error rate on your line, you will see network performance degrade.) However, in my case, my signal levels are normal and the number of uncorrectable codeword errors are extremely low, so this is not caused by "noise" or any other problem between my house and the CMTS.
I'm also sure that if I called into tech support, they would tell me that the problem is with my Wi-Fi or my computer, because every test at their end would likely indicate that everything is fine.
@Marando keep in mind that gaming doesn't necessarily require a large data rate, latency is the key here, so, DSL/VDSL might be absolutely fine for gaming. If you're gaming at the semi- professional / professional level, I would think that you've heard of, or read discussions regarding latency in fibre, cable and DSL/VDSL systems. Fibre is probably the optimum, but then you're contending with Bell's routing thru Chicago or other strange routes. DSL/VDSL is probably next in line followed by cable. Just keep in mind, latency is the key point, not data rate.
As for Pingplotter, pingplotter and the 4582 modem don't play well together due to internal timing in the modem. You can and will see false packet loss from the modem and hop #2 which is the Cable Modem Termination System (CMTS). Ping the following and only the following, in this order to demonstrate:
1. Ping the modem - you should see no packet loss from the modem. Drop the ping interval time down to 0.05 (seconds) using a manual entry of 0.05
2. Ping hop #2 - You should see no packet loss from hop #2 (the CMTS), but you should see false packet loss from the modem where you just proved to yourself that there is no packet loss from the modem.
3. Ping Rogers IPV4 DNS - 64.71.255.204 - You should see no packet loss from the DNS, but, given that you're running a ping test beyond the CMTS, you should see false packet loss from the modem and CMTS where you just proved that there is no packet loss from either one.
Any case of packet loss shown with Pingplotter should be confirmed by a manual ping test using a command line ping.
So, at the present time, don't be in a hurry to swap the modem. The modems are actually pretty reliable, despite what the users actually think, and despite tech support's immediate reaction to swap the modem. So, this requires a little more diagnosis, but, personal opinion, you're probably in the same boat as many other users with high latency which is no good for gaming.
Right click on the top title line of Pingplotter to bring up the display column menu. Select MAX and ERR to display those columns and drag them to the right to sit beside the Min and Avg columns.
Hope this clears the air (somewhat) regarding pingplotter. If you run low interval ping tests, pingplotter gets to a point where there is too much data to display one data point per horizontal pixel. Pingplotter will then display the average of the data that is held per pixel. The end result, the data flattens out and the plot looks better and better as you scale up in plot time from 60 seconds up to 72 hours. If you hover your mouse over the plot when that happens, pingplotter will indicate how many data points are in that particular horizontal pixel It never did that until recently, so, despite the "no warning" of the data averaging in the plot, at least you can see how many data points are in a particular horizontal pixel. If the text data above is set to Auto, it will display the data for the lower plot time. The text data will be correct despite the plot flattening out with higher time frames.
Edit: Its very unfortunate that pingplotter averages the data in "large data" situations instead of preserving the max and min data points and plotting those instead. Usually when you decide to use pingplotter, you're trying to diagnose high latency issues. You can't do that when pingplotter averages the data and flattens the curve in high timeframe plots. That forces you to drop down into low timeframes, either 60 seconds or 5 minutes to actually see the data plotted correctly as it should be. It becomes rather laborious to review 24, 48, 72 hours of data in 1 or 5 minute segments. End solution at this point is to capture the data with Wireshark and plot the results, where Wireshark doesn't average the data.
The issue with false packet loss indicated with pingplotter forces Rogers pingplotter users to test from the pc / laptop outwards, checking the modem, CMTS and end target, step by step to determine where any packet loss is occurring. At the end of the day, you should see no packet loss from the modem, essentially no packet loss from the CMTS although its never perfect, and no packet loss from Rogers DNS, although as with the CMTS, the return from the DNS is never perfect either. In both cases, the CMTS and DNS, you should only see a handful of packets lost over the course of a 24 hour ping test.
The minute that you test a target beyond the ISP border, and that's for any ISP, all bets are off, as you're now subject to peering and routing to your end target or server. There has never been any discussion in this forum regarding peering or routing, which is very unfortunate. I'd love to see that discussion with the Rogers network staff, but, I don't hold out any hope that it would ever happen.
-
207101 views
-
156 Likes
-
-
