Suffering Packet loss

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: 56

Re: Suffering Packet loss

high latency, packet loss and diminished speeds are very normal with Rogers nowadays. 

 

Do yourself a favor and open a CCTS complaint and accept a resolution only when it implies you're not paying for your internet. This is honestly the only reasonable thing you can do at this point. Rogers is just wasting/buying time hoping everything goes away/fixes itself on its own it seems. They have kept the customers in the dark and that alone might be their biggest mistake.

 

The issues were around before  the COVID19 everyone at home situation.👎

 

 

I've Been Here Awhile
Posts: 3

Re: Suffering Packet loss

I have been struggling with multiple outages, modem reboots and so on for months. Swapped out modems, had techs to my home, etc.

 

I am now trying to work this out myself.

 

I ran pingplotter over the last few days and all I see is a struggle between my modem and the first hop, which I understand is called the CMTS?

 

Does the 47.7% packet loss suggest an issue between modem (CODA) and the CMTS? I am assuming it does. pingplotter just to the modem directly shows <3ms.

 

If I do a pingplot to google or to pingplotter themselves all the extra hops look fine, it is still always this link between modem and ROgers box that seems to show up as an issue.

 

Or am I not reading this correctly?

 

 

 

Rogers Packet Loss CODA to first hopRogers Packet Loss CODA to first hop

Highlighted
Moderator
Moderator
Posts: 1,831

Re: Suffering Packet loss

Hello, @thecommunicator.

 

Thank you for joining this conversation, and welcome to Rogers Community Forums!

 

The first hop you see in the plotter is your gateway modem. Are you running the test on a WiFi connection? If your computer is hardwired to the modem, then try reseating the Ethernet cable at both ends. If possible, replace the Ethernet cable.

 

Please check the knowledge base article Troubleshooting Latency (Wired Devices), run the ping test, traceroute and post the results. 

 

Cheers,

RogersMoin

Highlighted
I've Been Here Awhile
Posts: 3

Re: Suffering Packet loss

The tests are run on two separate laptops both directly connected to the modem via ethernet cables connected specifically for the purposes of testing. I would normally be connected via ethernet, but via a switch. All this testing is direct connected. The cables used were both supplied by Rogers with the latest replacement modems. Now on the third in as many weeks.

 

I have tried this with no other devices connected to the switch except the two direct connected laptops. One laptop is older and only has 100M, the one from the image provided is a newer laptop with a 1G connection.

 

I will run the pingtest and the traceroute and update shortly.

 

Mike

Highlighted
I've Been Here Awhile
Posts: 3

Re: Suffering Packet loss

a mix of ping and tracert to various sites.

 

c:\Users\mpcra\Documents>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

c:\Users\mpcra\Documents>ping pingplotter.com

Pinging pingplotter.com [216.92.151.75] with 32 bytes of data:
Reply from 216.92.151.75: bytes=32 time=27ms TTL=54
Reply from 216.92.151.75: bytes=32 time=27ms TTL=54
Reply from 216.92.151.75: bytes=32 time=26ms TTL=54
Reply from 216.92.151.75: bytes=32 time=28ms TTL=54

Ping statistics for 216.92.151.75:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 28ms, Average = 27ms

c:\Users\mpcra\Documents>ping pingplotter.com

Pinging pingplotter.com [216.92.151.75] with 32 bytes of data:
Reply from 216.92.151.75: bytes=32 time=28ms TTL=54
Reply from 216.92.151.75: bytes=32 time=27ms TTL=54
Reply from 216.92.151.75: bytes=32 time=25ms TTL=54
Reply from 216.92.151.75: bytes=32 time=28ms TTL=54

Ping statistics for 216.92.151.75:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 28ms, Average = 27ms

c:\Users\mpcra\Documents>tracert www.pingplotter.com

Tracing route to pingplotter.com [216.92.151.75]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * 10 ms 10 ms 99.228.176.1
3 10 ms 17 ms 14 ms 8079-dgw02.mtnk.rmgt.net.rogers.com [69.63.255.157]
4 18 ms 14 ms 11 ms 0-5-0-5-cgw01.wlfdle.rmgt.net.rogers.com [209.148.233.201]
5 26 ms 29 ms 34 ms 209.148.233.102
6 * * * Request timed out.
7 37 ms 28 ms 33 ms be3083.ccr41.dca01.atlas.cogentco.com [154.54.30.53]
8 31 ms 31 ms 34 ms be2819.rcr21.pit02.atlas.cogentco.com [154.54.82.222]
9 32 ms 32 ms 30 ms 38.104.120.218
10 * * * Request timed out.
11 26 ms 27 ms 35 ms pingplotter.com [216.92.151.75]

Trace complete.

c:\Users\mpcra\Documents>tracert www.pingplotter.com

Tracing route to pingplotter.com [216.92.151.75]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * 49 ms * 99.228.176.1
3 12 ms 12 ms 14 ms 8079-dgw02.mtnk.rmgt.net.rogers.com [69.63.255.157]
4 13 ms 21 ms 16 ms 0-5-0-5-cgw01.wlfdle.rmgt.net.rogers.com [209.148.233.201]
5 29 ms 27 ms 42 ms 209.148.233.102
6 * * * Request timed out.
7 48 ms 34 ms 38 ms be3083.ccr41.dca01.atlas.cogentco.com [154.54.30.53]
8 35 ms 30 ms 28 ms be2819.rcr21.pit02.atlas.cogentco.com [154.54.82.222]
9 31 ms 47 ms 34 ms 38.104.120.218
10 * * * Request timed out.
11 36 ms 48 ms 53 ms pingplotter.com [216.92.151.75]

Trace complete.

c:\Users\mpcra\Documents>ping twitter.com

Pinging twitter.com [104.244.42.1] with 32 bytes of data:
Reply from 104.244.42.1: bytes=32 time=74ms TTL=57
Reply from 104.244.42.1: bytes=32 time=60ms TTL=57
Reply from 104.244.42.1: bytes=32 time=65ms TTL=57
Reply from 104.244.42.1: bytes=32 time=68ms TTL=57

Ping statistics for 104.244.42.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 74ms, Average = 66ms

c:\Users\mpcra\Documents>tracert twitter.com

Tracing route to twitter.com [104.244.42.1]
over a maximum of 30 hops:

1 * 1 ms 1 ms CODA4582 [192.168.0.1]
2 * 14 ms 14 ms 99.228.176.1
3 16 ms 28 ms 19 ms 8079-dgw01.mtnk.rmgt.net.rogers.com [69.63.255.153]
4 14 ms 17 ms 11 ms 3000-dgw02.mtnk.rmgt.net.rogers.com [209.148.232.57]
5 8 ms 17 ms 13 ms 209.148.229.85
6 35 ms 33 ms 39 ms 209.148.233.102
7 42 ms 33 ms 32 ms eqix1.cr1.iad1.twttr.com [206.126.236.97]
8 * * * Request timed out.
9 61 ms 61 ms 53 ms 104.244.42.1

Trace complete.

c:\Users\mpcra\Documents>tracert twitter.com

Tracing route to twitter.com [104.244.42.1]
over a maximum of 30 hops:

1 3 ms 6 ms 1 ms CODA4582 [192.168.0.1]
2 11 ms 13 ms * 99.228.176.1
3 16 ms 13 ms 10 ms 8079-dgw01.mtnk.rmgt.net.rogers.com [69.63.255.153]
4 12 ms 10 ms 17 ms 3000-dgw02.mtnk.rmgt.net.rogers.com [209.148.232.57]
5 10 ms 10 ms 12 ms 209.148.229.85
6 28 ms 30 ms 26 ms 209.148.233.102
7 35 ms 29 ms 31 ms eqix1.cr1.iad1.twttr.com [206.126.236.97]
8 * * * Request timed out.
9 57 ms 60 ms 51 ms 104.244.42.1

Trace complete.

c:\Users\mpcra\Documents>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=15ms TTL=118
Reply from 8.8.8.8: bytes=32 time=8ms TTL=118
Reply from 8.8.8.8: bytes=32 time=14ms TTL=118
Reply from 8.8.8.8: bytes=32 time=10ms TTL=118

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 15ms, Average = 11ms

c:\Users\mpcra\Documents>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 * 1 ms 1 ms CODA4582 [192.168.0.1]
2 57 ms * 13 ms 99.228.176.1
3 12 ms 15 ms 9 ms 8079-dgw02.mtnk.rmgt.net.rogers.com [69.63.255.157]
4 18 ms 12 ms 13 ms 69.63.249.66
5 19 ms 23 ms 16 ms 209.148.235.34
6 14 ms 15 ms 16 ms 72.14.222.87
7 14 ms 11 ms 19 ms 108.170.250.241
8 22 ms 21 ms 25 ms 108.170.226.217
9 14 ms 12 ms 16 ms dns.google [8.8.8.8]

Trace complete.

c:\Users\mpcra\Documents>ping www.rogers.com

Pinging e14237.e12.akamaiedge.net [104.68.231.176] with 32 bytes of data:
Reply from 104.68.231.176: bytes=32 time=13ms TTL=56
Reply from 104.68.231.176: bytes=32 time=13ms TTL=56
Reply from 104.68.231.176: bytes=32 time=7ms TTL=56
Reply from 104.68.231.176: bytes=32 time=14ms TTL=56

Ping statistics for 104.68.231.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 14ms, Average = 11ms

c:\Users\mpcra\Documents>tracert www.rogers.com

Tracing route to e14237.e12.akamaiedge.net [104.68.231.176]
over a maximum of 30 hops:

1 * 1 ms 1 ms CODA4582 [192.168.0.1]
2 15 ms * 19 ms 99.228.176.1
3 17 ms 15 ms 14 ms 8079-dgw01.mtnk.rmgt.net.rogers.com [69.63.255.153]
4 18 ms 12 ms 13 ms 0-5-0-9-cgw01.mtnk.asr9k.rmgt.net.rogers.com [209.148.233.193]
5 16 ms 17 ms 27 ms 209.148.235.222
6 * * * Request timed out.
7 14 ms 24 ms 19 ms ae2.torix-yto.netarch.akamai.com [23.203.148.129]
8 10 ms 16 ms 7 ms a104-68-231-176.deploy.static.akamaitechnologies.com [104.68.231.176]

Trace complete.

c:\Users\mpcra\Documents>tracert www.rogers.com

Tracing route to e14237.e12.akamaiedge.net [23.15.218.126]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms CODA4582 [192.168.0.1]
2 12 ms * * 99.228.176.1
3 15 ms 19 ms 16 ms 8079-dgw02.mtnk.rmgt.net.rogers.com [69.63.255.157]
4 16 ms 14 ms 17 ms 3000-dgw01.mtnk.rmgt.net.rogers.com [209.148.232.58]
5 13 ms 12 ms 14 ms 3021-cgw01.mtnk.asr9k.rmgt.net.rogers.com [209.148.232.49]
6 13 ms 7 ms 12 ms 209.148.237.58
7 14 ms 19 ms 9 ms a23-15-218-126.deploy.static.akamaitechnologies.com [23.15.218.126]

Trace complete.
c:\Users\mpcra\Documents>tracert 99.228.176.1

Tracing route to 99.228.176.1 over a maximum of 30 hops

1 * * * Request timed out.
2 15 ms 12 ms 13 ms 99.228.176.1

Trace complete.

c:\Users\mpcra\Documents>tracert 99.228.176.1

Tracing route to 99.228.176.1 over a maximum of 30 hops

1 * * * Request timed out.
2 14 ms 8 ms 9 ms 99.228.176.1

Trace complete.

c:\Users\mpcra\Documents>tracert 192.168.0.1

Tracing route to CODA4582 [192.168.0.1]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms CODA4582 [192.168.0.1]

Trace complete.

c:\Users\mpcra\Documents>tracert 192.168.0.1

Tracing route to CODA4582 [192.168.0.1]
over a maximum of 30 hops:

1 1 ms 2 ms 2 ms CODA4582 [192.168.0.1]

Trace complete.

c:\Users\mpcra\Documents>tracert 192.168.0.1

Tracing route to CODA4582 [192.168.0.1]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms CODA4582 [192.168.0.1]

Trace complete.

c:\Users\mpcra\Documents>

 

Mike

Highlighted
Resident Expert
Resident Expert
Posts: 6,944

Re: Suffering Packet loss

@thecommunicator stop any intensive testing.  What you're seeing is normal for the 4582 modem.  I don't have time at the moment, but I'll try to get back to this tonight.  I've posted comments in the forum regarding pingplotters behaviour and the 4582, so, that info is around.  I'll see if I can find them easily and direct your attention to them.  

 

Your traces did show something rather interesting, which is that a trace to rogers.com goes to and thru akami, which is really odd.  If thats correct, and permanent, that might pose some problems for assessing latency and packet loss in the Rogers network.  I'll have to take a closer look at this, but, don't have time at the moment. 



Highlighted
I've Been Around
Posts: 1

Re: Suffering Packet loss

It's not just you guys, I have ignite 1gb and having the same exact issues. Rogers will not admit any wrong doing or do anything other then read from their manual when you talk to them. My suggestion is take your business elsewhere, that's what I'm doing. I'm paying over $200 a month and getting dialup speeds at some points.

Highlighted
Moderator
Moderator
Posts: 569

Re: Suffering Packet loss

Hello @Ozeo,

 

Thank you for joining us in the community and congrats on your first post here! 🙂

 

I understand that packet loss can make for a pretty poor online experience! I don't blame you for being upset. We'd hate to lose you as our valued customer. If possible, we'd love to hear more about your situation so we as a community can provide some help and support for your issue!

 

May I ask, are you connected via WiFi or Ethernet when the issues transpire? Are you using any third party equipment? Is this issue happening on multiple different devices? If possible, please post your current signal levels beginning from the Downstream Overview line, all the way to the bottom right hand corner of the OFDM/OFDMA section which is at the bottom of the table. 

 

If you prefer to have us review your account notes from past interactions and run a few tests at our end, we'll be more than happy to help! You may send us a private message to @CommunityHelps to get started. For more information on how our Private Messaging system works, please check out our blog.

 

Thank you!

RogersLaura

Highlighted
I Plan to Stick Around
Posts: 15

Re: Suffering Packet loss

For some reason after 2am my latency in games are stable at 60-80.  Anytime before that I am getting 90-120.  Can anyone explain why after exactly 2am my latency magically goes down?

Highlighted
Resident Expert
Resident Expert
Posts: 6,944

Re: Suffering Packet loss

Are you or any one in the house running an online backup that is finished around 2 am?