Brutal latency/ping Recently

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
I Plan to Stick Around
Posts: 31

Re: Brutal latency/ping Recently

@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
Highlighted
I've Been Here Awhile
Posts: 3

Re: Brutal latency/ping Recently

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 

Highlighted
Resident Expert
Resident Expert
Posts: 6,987

Re: Brutal latency/ping Recently

@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?



Highlighted
Resident Expert
Resident Expert
Posts: 6,987

Re: Brutal latency/ping Recently

@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.  



Highlighted
I Plan to Stick Around
Posts: 31

Re: Brutal latency/ping Recently

@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?
Highlighted
Resident Expert
Resident Expert
Posts: 6,987

Re: Brutal latency/ping Recently

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. 



Highlighted
I Plan to Stick Around
Posts: 31

Re: Brutal latency/ping Recently

@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

Highlighted
I Plan to Stick Around
Posts: 31

Re: Brutal latency/ping Recently

@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

Highlighted
Resident Expert
Resident Expert
Posts: 6,987

Re: Brutal latency/ping Recently

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 🙂



Highlighted
I Plan to Stick Around
Posts: 31

Re: Brutal latency/ping Recently

@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