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
Resident Expert
Resident Expert
Posts: 6,942

Re: Brutal latency/ping Recently

Ok, got it, thanks. 



Highlighted
Resident Expert
Resident Expert
Posts: 6,942

Re: Brutal latency/ping Recently

@Visuria can you run a ping test to Rogers DNS as well.  In this case, I'm looking for packet loss.  To run this, using the same command box, type in:

 

ping -n 600 64.71.255.204

 

That will run a 10 min ping test.  I'd prefer a longer test, but for now, if you're seeing the same amount of packet loss, it will show up in a short test.  I'm interested in the final packet loss %.



Highlighted
Resident Expert
Resident Expert
Posts: 6,942

Re: Brutal latency/ping Recently

@RogersAndy are you able to have a look at this?  @t27c is seeing packet loss and unstable latency when gaming.  Ping tests to the CMTS don't show any losses.  Ping test to the Rogers Primary IPV4 DNS 64.71.255.204 show losses in the order of 20 to 25%, which isn't good.  Ping tests to google's and OpenDNS don't show any packet loss, so the loss appears to solely within Rogers network.  The question from this is, where do the paths to the DNS and the gaming server overlap, to the point that @t27c sees packet loss and unstable latency?

 

@Visuria is seeing similar issues although both are not co-located off of the same CMTS.  The traces to the DNS marry up at hop #5 and are the same from there to the end IP address at 64.71.255.204

 

Fwiw, pinging the same DNS IP address from ottawa does not show any packet loss.



Highlighted
I Plan to Stick Around
Posts: 31

Re: Brutal latency/ping Recently

@Datalink 

did another tracert and got a different result this time. Although I'm not sure if that maters or not in this situation lol

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 18 ms 51 ms 66 ms 99.255.58.1
3 77 ms 22 ms 54 ms 8177-dgw02.ktgc.rmgt.net.rogers.com [69.63.242.189]
4 44 ms 19 ms 87 ms 69.63.249.209
5 43 ms 43 ms 130 ms 209.148.227.157
6 * 48 ms 31 ms 10.202.47.161
7 52 ms 36 ms * dns.cp.net.rogers.com [64.71.255.204]
8 27 ms 24 ms * dns.cp.net.rogers.com [64.71.255.204]
9 47 ms * 89 ms dns.cp.net.rogers.com [64.71.255.204]

Highlighted
I Plan to Stick Around
Posts: 31

Re: Brutal latency/ping Recently

I should also mention that this did happen over the holidays and it lasted for about a week and it did end up going away. although the fact that it has come back has me thinking there is something wrong here. Especially with the 20% packet loss when I ping the IPV4 DNS

Highlighted
Resident Expert
Resident Expert
Posts: 6,942

Re: Brutal latency/ping Recently

Your routing is the same, and the route times aren't great.  Someone has to look at the CMTS which is at 99.255.58.1

 

As a comparison, here's the trace from Ottawa:

 

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1   <1 ms   <1 ms   <1 ms   RT-AC86U 
2   18 ms    15 ms    45 ms  174.112.15x.x
3     9 ms     22 ms     8 ms   67.231.221.73
4   13 ms    12 ms   15 ms   209.148.236.161
5   18 ms    15 ms   15 ms   69.63.248.70
6   17 ms    12 ms   15 ms   209.148.227.169
7          *             *            *      Request timed out.
8   12 ms    12 ms   18 ms   dns.cp.net.rogers.com [64.71.255.204]

 

Trace complete.

 

There's one high time on hop two and hop seven times out in my case but, the overall numbers are normal.



Highlighted
I Plan to Stick Around
Posts: 31

Re: Brutal latency/ping Recently

@DatalinkAh, I also do normally run in bridge mode. I also have a RT-AC86U router. But I have it unplugged so I could be directly connected to the modem. Hopefully someone is able to have a look at this and see what is going on

Highlighted
Resident Expert
Resident Expert
Posts: 6,942

Re: Brutal latency/ping Recently

Looks like @RogersAndy may have checked out for the night.  He should see the references tomorrow if he's in.  Failing that, both of you need to talk to a Tier II tech, specifically regarding the loading at your respective CMTS.  The Tier I tech that you will chat with first will give you some static about the request, to which my response would be, "Can you fix a CMTS loading problem?  If yes, lets chat, if not, pass me onto a Tier II tech", as in don't waste your time.  

 

@t27c your signal levels are fine, and there doesn't appear to be any packet loss to the CMTS, so the question is, what's up at the CMTS and beyond.  Your observation that this has come and gone over the holidays is interesting.  That would have occurred when people are home, gaming, streaming, etc, etc, so this looks more like a load issue.  

 

I'd put your modem back into Bridge mode and reconnect the 86U.  It won't make any difference whether the modem is in Gateway mode or Bridge mode, the problem is at the CMTS and beyond.  For troubleshooting purposes, Rogers staff prefers the modem in Gateway mode, with no router in the mix, so, its up to you as to when to reconnect the router.  

 

If you do chat with a Tier II tech regarding the performance of the CMTS, and beyond please let us know how the conversation went. 



Highlighted
I Plan to Stick Around
Posts: 14

Re: Brutal latency/ping Recently

Reply from 64.71.255.204: bytes=32 time=30ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=17ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=45ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=17ms TTL=58
Reply from 64.71.255.204: bytes=32 time=33ms TTL=58
Reply from 64.71.255.204: bytes=32 time=17ms TTL=58
Reply from 64.71.255.204: bytes=32 time=25ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=24ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=41ms TTL=58
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Reply from 64.71.255.204: bytes=32 time=45ms TTL=58
Reply from 64.71.255.204: bytes=32 time=6ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=34ms TTL=58
Reply from 64.71.255.204: bytes=32 time=46ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=30ms TTL=58
Reply from 64.71.255.204: bytes=32 time=47ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=60ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=61ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=37ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=41ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=27ms TTL=58
Reply from 64.71.255.204: bytes=32 time=30ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=17ms TTL=58
Reply from 64.71.255.204: bytes=32 time=19ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Reply from 64.71.255.204: bytes=32 time=25ms TTL=58
Reply from 64.71.255.204: bytes=32 time=29ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=28ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=58ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=51ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=17ms TTL=58
Reply from 64.71.255.204: bytes=32 time=31ms TTL=58
Reply from 64.71.255.204: bytes=32 time=23ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=26ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=14ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=38ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Reply from 64.71.255.204: bytes=32 time=32ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=26ms TTL=58
Reply from 64.71.255.204: bytes=32 time=38ms TTL=58
Reply from 64.71.255.204: bytes=32 time=33ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=34ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=77ms TTL=58
Reply from 64.71.255.204: bytes=32 time=27ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=19ms TTL=58
Reply from 64.71.255.204: bytes=32 time=50ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=39ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=29ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=26ms TTL=58
Reply from 64.71.255.204: bytes=32 time=26ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=49ms TTL=58
Reply from 64.71.255.204: bytes=32 time=104ms TTL=58
Reply from 64.71.255.204: bytes=32 time=21ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=36ms TTL=58
Reply from 64.71.255.204: bytes=32 time=37ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=53ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=20ms TTL=58
Reply from 64.71.255.204: bytes=32 time=19ms TTL=58
Reply from 64.71.255.204: bytes=32 time=28ms TTL=58
Reply from 64.71.255.204: bytes=32 time=30ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=40ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=25ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=27ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=20ms TTL=58
Reply from 64.71.255.204: bytes=32 time=30ms TTL=58
Reply from 64.71.255.204: bytes=32 time=98ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=14ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=14ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=22ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=29ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=32ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=14ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=39ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=23ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=23ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Reply from 64.71.255.204: bytes=32 time=32ms TTL=58
Reply from 64.71.255.204: bytes=32 time=63ms TTL=58
Reply from 64.71.255.204: bytes=32 time=14ms TTL=58
Reply from 64.71.255.204: bytes=32 time=29ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=22ms TTL=58
Reply from 64.71.255.204: bytes=32 time=26ms TTL=58
Reply from 64.71.255.204: bytes=32 time=59ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=34ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=35ms TTL=58
Reply from 64.71.255.204: bytes=32 time=27ms TTL=58
Reply from 64.71.255.204: bytes=32 time=19ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=20ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=26ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=24ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=17ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=20ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=17ms TTL=58
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=17ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Reply from 64.71.255.204: bytes=32 time=6ms TTL=58
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Reply from 64.71.255.204: bytes=32 time=14ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=7ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=14ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=9ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=25ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=20ms TTL=58
Reply from 64.71.255.204: bytes=32 time=6ms TTL=58
Reply from 64.71.255.204: bytes=32 time=10ms TTL=58
Reply from 64.71.255.204: bytes=32 time=8ms TTL=58
Reply from 64.71.255.204: bytes=32 time=28ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=20ms TTL=58

Ping statistics for 64.71.255.204:
Packets: Sent = 600, Received = 451, Lost = 149 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 104ms, Average = 19ms

C:\Windows\system32>

Highlighted
Resident Expert
Resident Expert
Posts: 6,942

Re: Brutal latency/ping Recently

Ugh 24% loss.  That shouldn't be happening.  Take a look at my post just above.