cancel
Showing results for 
Search instead for 
Did you mean: 

Brutal latency/ping Recently

t27c
I plan to stick around

I am wired, with the gigabit package and all of the sudden have gotten constant ping spikes for over the last few days. I haven't been able to play any games online because the crazy ping spikes and latency make it completely unplayable. My speeds are what they are expected to be, no issues there. I have tried hard wiring straight into the modem but alas, the issue still persists. I have tried switching cables, power cycling my devices, factory resetting my devices. The issue still persists. I have called and contacted Rogers multiple times and they say everything seems fine on their end. But still, the issue persists and is steady. resulting in me not able to use any of my gaming devices due to the brutal and constant ping spikes. It's frustrating paying over $100 a month for internet I cant use for the things I want it for. Any help or suggestions are welcomed and appreciated. Thank you

 

*** Edited Labels ***

956 REPLIES 956

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert
@t27c what modem do you have, the white Hitron CODA-4582 (id on the back), or the black XB6 for the Ignite TV package, where the modem id is on the bottom of the modem. It will either be the Arris TG-3482ER or the Technicolor CGM-4140.

Re: Brutal latency/ping Recently

t27c
I plan to stick around
@Datalink I have the Hitron CODA-4582

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert
Ok, that makes this easier to resolve as its the same modem that I'm using. Can you log into the modem, navigate to the STATUS .... DOCSIS WAN tab, and copy the signal level stats, from the start of the "Downstream Overview" all the way to the bottom right hand corner of the table, which is the last line of the OFDMOFDMA Overview. Select that whole area, right click .... Copy. Then in a new post, right click .... Paste. Lets see what if anything is going on with the signal levels. After that, and when you have time, run a ping test to the Rogers Primary IPV4 DNS, 64.71.255.204: ping -n 3600 64.71.255.204 That will run for an hour and stop automatically. When its done, right click on the top title bar of the command prompt, right click and select Edit .... Select All. Right click on the top title bar again, right click, select Edit ... Copy. Then paste that into something like Notepad. Copy the bottom results and paste that into a post. Its possible for the signal levels to look ok, but still end up with packet loss if there's an issue with the external cable and its connectors. So, with both data sets, we'll hopefully be able to see whats up.

Re: Brutal latency/ping Recently

t27c
I plan to stick around
@DataLiink I could no get it to paste as a table. Only this jumbled mess lol. I am also pinging Rogers IPV4 DNS and getting a lot of "request timed out" results. Is that packet loss? Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 591000000 256QAM 2.200 7 40.366 2 855000000 256QAM -1.500 3 38.605 3 861000000 256QAM -2.000 4 37.636 4 579000000 256QAM 2.800 5 38.983 5 585000000 256QAM 2.800 6 38.983 6 849000000 256QAM -1.100 2 38.605 7 597000000 256QAM 2.600 8 38.983 8 603000000 256QAM 2.900 9 38.983 9 609000000 256QAM 2.300 10 38.983 10 615000000 256QAM 1.800 11 38.983 11 621000000 256QAM 2.300 12 40.366 12 633000000 256QAM 1.100 13 38.983 13 639000000 256QAM 1.500 14 38.983 14 645000000 256QAM 1.400 15 38.983 15 651000000 256QAM 1.900 16 38.983 16 657000000 256QAM 1.700 17 38.983 17 663000000 256QAM 1.900 18 38.983 18 669000000 256QAM 2.500 19 38.983 19 675000000 256QAM 2.200 20 38.983 20 681000000 256QAM 1.500 21 38.983 21 687000000 256QAM 1.000 22 38.983 22 693000000 256QAM 0.900 23 38.983 23 699000000 256QAM 0.700 24 38.605 24 705000000 256QAM 0.100 25 38.605 25 711000000 256QAM 0.000 26 38.983 26 717000000 256QAM 0.100 27 38.983 27 723000000 256QAM -0.900 28 38.605 28 825000000 256QAM -1.100 29 38.605 29 831000000 256QAM -1.500 30 38.605 30 837000000 256QAM -1.000 31 38.983 31 843000000 256QAM -0.700 32 38.605 32 279000000 256QAM 2.000 1 38.983 OFDM Downstream Overview Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv) 0 4K 275600000 YES YES YES 1.900002 1 NA NA NO NO NO NA Upstream Overview Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth 1 23700000 ATDMA - 64QAM 30.750 2 6400000 2 38596000 ATDMA - 64QAM 32.750 3 3200000 3 30596000 ATDMA - 64QAM 30.750 1 6400000 OFDM/OFDMA Overview Channel Index State lin Digital Att Digital Att BW (sc's*fft) Report Power Report Power1_6 FFT Size 0 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K 1 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert
Don't worry about the table. I've sorted it out and your signal levels are fine. One wouldn't expect any issues given those signal levels. so, the fact that your seeing time outs either means that the Cable Modem Termination System that you're modem connects to is heavily loaded, or, you have external cable issues. In either case, you would end up with packet loss that results in a timeout. I wouldn't expect the CMTS to be heavily loaded at this time of the morning. So, I'll be interested in the final results when the test finishes. If you run the test as: ping -t 64.71.255.204 it will continue until you use Ctrl C to bail out of the test. One other test you can to is to ping the CMTS itself. To do that, run a trace to anywhere: tracert -4 www.google.com The first hop is the modem if its in Gateway mode, the second hop is the CMTS. Use that second hop IP address and ping that address. Ignore any high time pings as that is the result of an internal modem timing issue. The task at hand is to look for packet loss to the CMTS, which you will see as the test progresses, if in fact there is an issue with your external cabling. One major note, the ping test must be done with an ethernet connected laptop or desktop to remove any wifi issues from the mix. It can be a useful test to ping the modem or router over wifi just to demonstrate how terrible wifi can be, but, for anything beyond the modem, it should always be done via ethernet. Ok, so, with the final test to the CMTS, run for an hour or more, you can use that loss number to report the problem to tech support. Your signal levels look good, but, the loss number will indicate a problem with your external cables and connectors. Does the external cable run underground to a nearby pedestal, or overhead to the nearest utility pole?

Re: Brutal latency/ping Recently

t27c
I plan to stick around
@Datalink was able to get it a bit better lol Downstream Overview Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 591000000 256QAM 2.200 7 40.366 2 855000000 256QAM -1.500 3 38.605 3 861000000 256QAM -2.000 4 37.636 4 579000000 256QAM 2.700 5 38.605 5 585000000 256QAM 2.800 6 38.983 6 849000000 256QAM -1.100 2 38.605 7 597000000 256QAM 2.600 8 38.983 8 603000000 256QAM 2.900 9 38.983 9 609000000 256QAM 2.300 10 38.605 10 615000000 256QAM 1.800 11 38.983 11 621000000 256QAM 2.300 12 40.366 12 633000000 256QAM 1.100 13 38.983 13 639000000 256QAM 1.500 14 38.983 14 645000000 256QAM 1.400 15 38.983 15 651000000 256QAM 1.800 16 38.983 16 657000000 256QAM 1.700 17 38.605 17 663000000 256QAM 1.900 18 38.983 18 669000000 256QAM 2.500 19 38.983 19 675000000 256QAM 2.100 20 38.983 20 681000000 256QAM 1.500 21 38.605 21 687000000 256QAM 1.000 22 38.983 22 693000000 256QAM 0.900 23 38.983 23 699000000 256QAM 0.700 24 38.983 24 705000000 256QAM 0.100 25 38.605 25 711000000 256QAM 0.000 26 38.983 26 717000000 256QAM 0.100 27 38.605 27 723000000 256QAM -0.900 28 38.605 28 825000000 256QAM -1.100 29 38.605 29 831000000 256QAM -1.600 30 38.605 30 837000000 256QAM -1.000 31 38.605 31 843000000 256QAM -0.700 32 38.605 32 279000000 256QAM 2.000 1 38.983 OFDM Downstream Overview Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv) 0 4K 275600000 YES YES YES 1.900002 1 NA NA NO NO NO NA Upstream Overview Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth 1 23700000 ATDMA - 64QAM 30.750 2 6400000 2 38596000 ATDMA - 64QAM 32.750 3 3200000 3 30596000 ATDMA - 64QAM 30.750 1 6400000 OFDM/OFDMA Overview Channel Index State lin Digital Att Digital Att BW (sc's*fft) Report Power Report Power1_6 FFT Size 0 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K 1 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert
Fwiw, the forum software is broken at the present time Its removing all line and paragraph spacing from a post when the user hits the post button. Aggravating to say the least.

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert
Have a look at my post, just above your last post. Signal levels are fine, looks like a packet loss issue which won't show up in the signal level table.

Re: Brutal latency/ping Recently

t27c
I plan to stick around
@Datalink Sorry, lol. I believe it is underground to my understanding. This is what I get when I run the tracert to www.google.com: 1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1] 2 60 ms 39 ms 18 ms 99.255.58.1 3 28 ms 37 ms 53 ms 8177-dgw02.ktgc.rmgt.net.rogers.com [69.63.242.189] 4 28 ms 102 ms 20 ms 209.148.236.189 5 34 ms 106 ms 22 ms 209.148.230.6 6 70 ms 45 ms 33 ms 72.14.222.87 7 41 ms 61 ms 21 ms 108.170.250.241 8 34 ms 20 ms 15 ms 108.170.226.221 9 26 ms 76 ms 17 ms yyz10s04-in-f4.1e100.net [172.217.1.164]

Re: Brutal latency/ping Recently

t27c
I plan to stick around
@Datalink Here is the results of pinging Rogers IPV4 DNS: Ping statistics for 64.71.255.204: Packets: Sent = 3600, Received = 2899, Lost = 701 (19% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 347ms, Average = 42ms

Re: Brutal latency/ping Recently

YbTL
I've been here awhile

I have same issue too. Hwy7 & bathurst. Already asked rogers to fix it, but the guy just came and changed a modem and said he cannot fix it, he said it is the same problem that happened in whole area 

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert

@t27c that 19% packet loss is pretty ugly.  Just to see whats up between the modem and the Cable Modem Termination System (CMTS), can you run the following ping test to the CMTS:

 

ping -n 3600 99.255.58.1

 

That will run for an hour and terminate when complete.  

 

The path from the modem outwards is:

 

modem -> splitter (?) -> Demarc -> Local Tap -> Neighbourhood node -> CMTS -> multiple servers -> target address

 

1.  You may or may not have a splitter, depending on whether or not you have other Rogers products running:

2.  The Demac is the demarcation between the Rogers external cable and the house cable system.  That's the 

      Rogers box mounted outside of your home;

3.  The local tap is the pedestal (possibly green in colour) close to your home.  That services your home and

      immediate neighbours on your side of the street;

4.  Everything from the modem to the neighbourhood node is connected with cable.

5.  From the neighbourhood node outward is fibre

 

So your test last night combined both cable and fibre to the DNS.  I'd like to see the results running solely to the CMTS, which would exclude any network issues beyond the CMTS.  Any packet loss issues are usually due to the external cable that connects your home to the local tap.  There is always the possibility of issues between the local tap and the CMTS, but, the external cable is typically the starting point in terms of investigating the situation. 

 

Can you confirm that you're running the ping tests via ethernet?

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert

@YbTL if that's the case, my question in response would have been, "ok, is there a ticket open to fix the area?".   If this is ongoing, I'd suggest calling tech support to ask specifically if there is a ticket in for the area to deal with the latency.  Don't hesitate when it comes to looking for an answer that indicates current or near term action will address the latency.  

Re: Brutal latency/ping Recently

t27c
I plan to stick around
@Datalink Can confirm I am running the test through an ethernet from the CODA to my desktop PC.

I am running the ping test solely to the CMTS. Anything in particular that I’m looking for?

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert

Hi, yes, we're looking for the packet loss stats, just to see if they are any different from last night.  You will see high times occur which are solely due to an internal timing issue within the modem.  In the case of a ping test to the CMTS with this modem, its only usable for packet loss stats. 

Re: Brutal latency/ping Recently

t27c
I plan to stick around

@Datalink so far no packet loss when solely pinging the CMTS. But I will post the results once it has completely finished just in case

Re: Brutal latency/ping Recently

t27c
I plan to stick around

@DatalinkHere are the final results:

 

Ping statistics for 99.255.58.1:
Packets: Sent = 3600, Received = 3600, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 612ms, Average = 45ms

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert

Ok, that's rather interesting.  Can you fire up a ping test to the DNS again, don't have to run it for very long, just long enough to see if you see the same packet loss indications as last night. You can run it for a long period of time if you prefer.  If you don't see the same loss to the DNS, stop the test and fire up your game to see how it runs.

 

ping -t 64.71.255.204

 

Use Ctrl C to bail out of the test.  

 

The lack of any packet loss would indicate that there isn't any issue with the external cabling.  We can run a test at a higher rate with a different application, but first, please run a quick check to the DNS and then switch to gaming mode 🙂

Re: Brutal latency/ping Recently

t27c
I plan to stick around

@Datalink 

Results to the DNS

Ping statistics for 64.71.255.204:
Packets: Sent = 169, Received = 127, Lost = 42 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 142ms, Average = 43ms

Re: Brutal latency/ping Recently

Datalink
Resident Expert
Resident Expert

Ok, lets try the same test to google's DNS and OpenDNS as well.  So, its interesting to see that there's no packet loss to the CMTS, but, beyond the CMTS there is packet loss, which would point to an possible overload situation at the CMTS.  

 

So, same idea here, run it long enough to check for packet loss

 

Google DNS;

 

ping -t 8.8.8.8

 

OpenDNS:

 

ping -t 208.67.222.222

 

Both of those will run a ping test for the purpose of checking for any packet loss when you actually ping something beyond the CMTS.