very high ping to my modem (CGN3ROG)
Hi, over the past few months, I noticed constant lag and disconnects during online games.
It seems like I have very high ping to my modem(CGN3ROG). I'm on a wired connection.
I also made sure the modem didn't have any other devices connected to it when I was testing.
The things I tried are listed here, but I always got the same result:
Here's some screenshots:
Also, here's my Down and Up stream signals:
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Signal noise ratio (dB)||Channel ID|
|Port ID||Frequency (MHz)||BandWidth||Modulation Type||Signal Strength (dBmV)||Channel ID|
Any help would be greatly apprecated.
@edison12, your downstream signal levels are too high. They should be clustered around 0 dBmv. When you have time, can you take a quick look where the incoming cable connects to your house cables. Check for a passive splitter or for a powered amplifier. If its a powered amplifier, can you have a look at the model number at the front of the splitter and try to determine what port the internet cable is sitting on? Please let me know what you find.
The issue of high ping times to the modem was resolved a long time ago, so, I'd like to see a plot for the modem itself. Can you run a test, using 192.168.0.1 as the target and drop the time down to 0.1seconds. Let that run for 5 min and post the plot please.
The second point of interest is the time to the second hop, 18.104.22.168. That average time should be down around 12 ms or lower. 31 ms to the Cable Modem Termination System is pretty high. So, can you do the same for that address. Run that address as the target, with 0.1 second intervals and let it run for 5 min. Please post that as well.
The last point to look at is the Rogers to Cogent interface, which sits between hop #5 and #6. 22.214.171.124 is the last Rogers server outbound, 126.96.36.199 is the first Cogent server outbound. There is a 36.5 ms jump in time from server to server and that time offset carries on to the end target. Since this is outbound to Pingplotter.com I'm not overly concerned about it, but, if you happen to be gaming or running some application that runs thru those two servers, then that is a problem. The only way to solve that problem would be for the staff @CommunityHelps to forward an observation/complaint to the Network Operations Center to look at the problem. My guess would be a capacity problem in the link between the two servers. Only people who can resolve that are Rogers and Cogent network staff. Fwiw, Rogers uses Cogent to route traffic, so, there is a high probability that traffic that you're concerned with will route down thru the U.S. before returning to Canada, taking a circuitous route and adding latency to any traffic that runs from an original point in Canada to an end point in Canada.
I recently moved to a new unit in a condominium in Toronto at 10 York St (brand new condo). Rogers has a partnership apparently with the condo. As we have a 6 months free plan but if it's so slow like that I'll have to choose another ISP.... The technician from Rogers has recently installed internet in my unit but it doesn't work properly: it's very slow... When I test my connection on Speedtest everything seems perfect but in reality the connection is very slow. It's like I loose the internet signal for 5 seconds every 10-15 seconds and then the internet is back and again I loose the signal 5 seconds and so on. I noticed my ping is not good and presents some pics sometimes: some pics at 800 ms...
Please find below the results from Ping Plotter, windows console and other services:
Regarding my settings:
- Provider: Rogers
- Plan: Ignite 60u (60 Mega download and 10 Mega upload)
- Modem: Hitron
- Network: fiber
I spoke with my neighbours on the same floor in the condo and they experience the same issue. In their case, the technician from Rogers came three times, changed the hardware and everything but the issue is still here. Which is odd is that we have a public wifi in the amenities and it works perfectly without slowness. I read some posts on this forum about ping issues with Rogers, apparently it's quite common...
My questions are:
- What do you recommend me to do to diagnose my internet connection: what tests do you recommend do with which websites/softwares? If a technician comes I want to be aware of the issue and support him if possible.
- Apparently the root cause of this high ping is not between my computer and router/modem. What could be the causes for some pics of high ping? Are you aware of this technical issue in that condo? What does Rogers propose to fix that?
Thanks in advance fro your response and your help!
Welcome to the Rogers Community Forums!
Thank you for posting your concern with all the details and images. Such a high latency could happen for many reasons, and it's certainly not a pleasant occurrence.
Since the high ping is not internal in your network, we can run further run diagnostics to confine the issue. Please send us a private message at @CommunityHelps. You can find details about our private messaging in this blog.
Some General notes:
When you post a ping plotter image, using an IPV4 image isn’t a problem. IPV6 is a problem as it includes the modems exact IPV6 address, unless you’ve deleted the IP address from Hop #1 on the image. If you want to post an IPV6 plot please ensure that you’ve manually deleted/erased the Hop #1 IP address from the plot. I’ll ask the moderators to delete the first image from your post as I’d prefer that MAC addresses and IPV6 addresses are not left out in the open. This is for your own online security.
Pingplotter and Hitron modems can result in confusing results, which is why I indicated a stepped test approach detailed above, proving that the path to the modem is running correctly, then testing the path to the MDU or CMTS, then going beyond to the DNS. Only when that is done should anyone consider testing beyond the Rogers border. That applies to any ISP, not just Rogers. The assumption is that all is well within the ISP, but, that might not be the case, and the only way to know that is to step thru a test, starting with the modem itself and working outwards. You really need to know up front that the combination of Pingplotter and Hitron modems can result in confusing or quirky results and be able to determine what's a correct result, and what isn't.
Pingplotter averages the displayed data, but, doesn’t advertise that fact. It comes down to displaying a given number of horizontal data points in the selected display timeframe, ie: 60 seconds, 5 min, 10 min, etc. Every time you increase the timeframe to be displayed, Pingplotter crams more data points into the display. Instead of preserving the high and low points, it averages the data points. So, even if you had high ping times in the data, as seen in the MAX time data in the upper text data, the plot can actually look ok. As you increase the timeframe, up into the 24, 48 hour times or longer, the plot will flatten out and look fine. That’s due to Pingplotter’s choice to average the display instead of preserving the high and low points on the plot itself. The newest version of Pingplotter will display the number of data points and the high and low in a data pop up when you park the curser in the lower plot area of the display. As you scroll left or right, it will show the applicable data for the vertical data point that the curser is located on.
To get around the averaging problem, if you run the default 2.5 second interval, you should be able to display 24 hours of data without any averaging. You can let the tets run for a longer period of time using whatever interval you want, but, if you want to see the results without any averaging, select 2.5 second intervals and a time display of 24 hours or less. Running a test for 24 hours to the DNS will show if you have a persistent latency issue throughout the day. While the latency will increase during the evening when everyone is home, gaming, streaming video, etc, during the very early morning hours from midnight to about 6 am, that plot should flatten out with very few latency spikes if any. Continued latency spikes would confirm that there is some issue afoot. Using the DNS as a target for later testing will also allow you to keep any eye on whether or not any progress is being made over the next few days, weeks, months.
Hope this helps. Please let me know if you have any questions on the issue. @RogersMoin should be able to get the ball rolling for a field tech. The question is where does the problem lie? That will determine what level of tech is required, a contractor tech or Rogers tech who is qualified to repair or replace the MDU.
Edit: Can you expand the MAX, MIN, AVG, etc columns slight so that you can see the whole number. You can slide the column borders around to do that.
Oh thank god, Datalink is here
I've been getting high-ish ping numbers for the last week or so where previously, I would always get 9-11ms times. No matter when I perform a test now, the lowest I can achieve is 30ms. Strange.
@Dascombe can you repost the image. Looks like @RogersCilio deleted it, most likely due to a MAC address or IPV6 (?) WAN IP address on the image. Can you remove the data in question and repost the image? If you have a read thru my instructions above can you consider running the same stepped approach to test to the modem, CMTS/MDU and then the DNS? Hopefully that would shed some light on the situation.
Edit: Are you running the ping test via ethernet or wifi?
Thanks Datalink, I don't know why my image was deleted, it was a simple Tracert command from Windows command prompt to: www.google.com. My IP Address isn't shown and neither is my MAC address and I'm not using iPV6. Anyway, here it is again:
@Dascombe, to post a tracert or any other info from the command box, right click on the top title bar of the command box. Select Edit .... Select All. Right click on the title bar again and select Edit .... Copy. You can then paste that into a post, or paste it into something like notepad first if you want to clean up the data, then copy and paste from notepad. Here's a trace to google.com. In this case I have the modem running in Gateway mode for test purposes with my router behind it. Kinda goofy as it causes a double NAT situation behind the router, but, I can connect directly to the modem for testing at the same time.
By pasting the text data, the mods don't have to approve any images, so this is much faster.
Tracing route to www.google.com [188.8.131.52]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com
2 1 ms <1 ms 1 ms 184.108.40.206
3 13 ms 12 ms 9 ms 220.127.116.11
4 10 ms 11 ms 11 ms 18.104.22.168
5 16 ms 23 ms 15 ms 22.214.171.124
6 17 ms 15 ms 15 ms 9300-cgw01.bloor.rmgt.net.rogers.com [126.96.36.199]
7 15 ms 17 ms 15 ms 188.8.131.52
8 17 ms 15 ms 15 ms 184.108.40.206
9 * * * Request timed out.
10 17 ms 17 ms 17 ms 220.127.116.11
11 17 ms 17 ms 16 ms 18.104.22.168
12 16 ms 16 ms 15 ms yyz10s03-in-f4.1e100.net [22.214.171.124]
Ah, didn't realize that images were mod approved but I guess that's prudent. Anyway, here's the text of another Tracert:
Tracing route to www.google.com [126.96.36.199]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 11 ms 13 ms 8 ms 188.8.131.52
3 59 ms 11 ms 10 ms 184.108.40.206
4 19 ms 15 ms 17 ms 220.127.116.11
5 53 ms 40 ms 34 ms 18.104.22.168
6 106 ms 39 ms 41 ms 9301-cgw01.ym.rmgt.net.rogers.com [22.214.171.124]
7 33 ms 47 ms 43 ms 126.96.36.199
8 33 ms 33 ms 33 ms 188.8.131.52
9 * * * Request timed out.
10 34 ms 34 ms 32 ms 184.108.40.206
11 34 ms 37 ms 33 ms 220.127.116.11
12 44 ms 45 ms 47 ms 18.104.22.168
13 45 ms 44 ms 43 ms 22.214.171.124
14 43 ms 44 ms 43 ms 126.96.36.199
15 44 ms 42 ms 53 ms 188.8.131.52
16 43 ms 42 ms 42 ms ord37s07-in-f4.1e100.net [184.108.40.206]
Seems to be the latency spikes between hops 4 & 5.