cancel
Showing results for 
Search instead for 
Did you mean: 

Suffering Packet loss

pandemic
I've Been Around

Hello, I have contacted tech support a few times and techs have come out to check my cables. The techs say that the signal strength is good and I do receive the advertised speeds 100/10, but I suffer packet loss. I also get dropped from Skype calls at the same times I am lagging on League.... I am not sure what the issue maybe, any advice?

 

Stats from the modem, it is in gateway mode and I am on a desktop connect through ethernet.
 
Ping statistics for 104.160.131.1:
Packets: Sent = 1000, Received = 870, Lost = 130 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 146ms, Average = 31ms
 
Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 651000000 256QAM -8.700 10 37.356
2 591000000 256QAM -6.100 1 38.605
3 597000000 256QAM -7.000 2 38.605
4 603000000 256QAM -6.400 3 38.983
5 609000000 256QAM -6.800 4 38.605
6 615000000 256QAM -6.900 5 38.983
7 621000000 256QAM -7.400 6 38.605
8 633000000 256QAM -8.200 7 37.636
9 639000000 256QAM -7.600 8 37.636
10 645000000 256QAM -8.900 9 37.636
11 657000000 256QAM -9.300 11 37.356
12 663000000 256QAM -9.400 12 37.356
13 669000000 256QAM -9.400 13 35.084
14 675000000 256QAM -9.400 14 36.387
15 681000000 256QAM -9.600 15 37.356
16 687000000 256QAM -9.800 16 36.610
17 693000000 256QAM -9.800 17 36.610
18 699000000 256QAM -10.900 18 36.387
19 705000000 256QAM -10.200 19 36.610
20 711000000 256QAM -10.600 20 36.610
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID BandWidth
1 23700000 ATDMA - 64QAM 40.250 7 6400000
2 30596000 ATDMA - 64QAM 40.250 6 6400000
3 38596000 ATDMA - 64QAM 40.250 5 3200000
201 REPLIES 201

Re: Suffering Packet loss

1 - Living in a brand new apartment building, the problem just suddenly came out of nowhere.

3 - running a ping test with google should take well over a hour to finish ill post the results after its done if needed but fingers crossed it fixes itself today.

Re: Suffering Packet loss

Don't bother with a test to google.  Run the test to the CMTS or in your case to the Multiple Dwelling Unit (MDU) which the apartment might have instead of a CMTS.  That depends on how large the apartment building is. 

 

Running a ping test to the CMTS or MDU avoids any type of network issue that might be at hand.  This type of testing should be run in stages with the following targets:

 

1.  Modem or router

2.  CMTS or MDU

3.  Rogers DNS

4.  External target.  

 

Each stage should be run for a considerable amount of time and should prove that there is no packet loss to the target in that stage, before moving on to the next stage.  

 

Running any test to a target such as google, prior to running the tests that I'm suggesting runs the risk of combining local packet loss issues with network issues.  Separating the two potential issues can't be done by a contractor tech.  So, its important to determine where the packet loss is occurring in order to adequately address the issue. 

 

In your particular case, if the building has one or more MDU's, its possible that the port or MDU that you're connected to has a technical problem.  An easy resolution might be to switch you to a different MDU, if that is possible.  If there is an MDU issue, then a qualified tech will be required to address it.  I suspect that contractor techs aren't qualified to replace MDU's. 

 

Edit:  are you running the ping test via ethernet or wifi?   This type of testing should always be run via ethernet.  Having said that, running a wifi ping test to the modem or router is a good test to determine just how lousy a wifi connection can actually be.  But, a wifi ping test shouldn't be run beyond the modem or router due to losses incurred between the test platform and the modem or router. 



Re: Suffering Packet loss

So it seems to have fixed itself while i was sleeping.

Re: Suffering Packet loss

NHTZ2
I've Been Here Awhile

Serious Packet Loss Issues

 

Edit: This was made as a seperate post and was merged into here.

Hello,

I am posting here because I have nowhere else to go. I am suffering from ridiculous packet loss with my home internet.

I have spoken with Rogers livechat, over the phone with technicians and managers, and have had numerous technicians come to my house. They are all claiming that nothing is wrong.

A few weeks ago, I randomly started experiencing a lot of packet loss. My online meetings were constantly disconnecting, whether they were voice or with webcam, my video games are all lagging an excessive amount, and anything I stream constantly drops in quality or freezes. It doesn't matter if its wired or wireless, I am getting the same errors.  All the applications I use are giving me packet loss errors. 

I used a few online tools to test packet loss, and the results show sometimes I have 0% packet loss, or 15% to 100% packet loss. This makes sense to me because my streams, meetings, and games go from normal to disastrous within the same minute.

Now for information regarding my setup. I use a TP Link C4000 router with a CODA modem. I am on a gigabit plan. I tried putting the modem in bridge mode, no luck. Took it off bridge mode, no luck. I unplugged and put away my router all together and only used the Roger's modem. No luck. I disconnected EVERYTHING off my network and only connected my laptop with an ethernet cable directly into the modem. No luck. I got sent a new modem. No luck. Technicians have spent up to 4.5 hours at my house trying to identify the issue, and they couldnt. When I speak with technicians on livechat or over the phone, they say I should bring a PC technician to my house to investigate my computer... when in reality I am getting this issue with my phone, work laptop, personal laptop. and PS4. If I was to run a speed test on my network, I'll get anywhere between 200 to 500 mbps. My speed is amazing, but the packet loss makes my internet feel choppy.

This issue came out of nowhere about a month or so ago and its seriously affecting my work. I even got an unlimtied data Telus plan so I can hotspot my work laptop, and even my video game console... and guess what... no more packet loss. The Rogers manager told me super generic information when I requested to be transferred to him, like "how far your devices are affect the speed. How many devices you have connected can affect performence." He completely ignored me saying I tried the test with my laptop connected directly to the modem.

Im at a point where Im shopping for other ISPs. I'm considering calling CRTC or CCTS at this point because I am paying for a service but am not getting proper internet. I'd rather avoid the drama and the hassle and get this resolved.

The issue is, I am being told by frustrated agents that this issue is my fault or the fault of the devices I am currently using... if this is somehow related to the sudden surge of people using the internet it would be one thing, but to be told many times rudely that the issue is on my end when its obviously not, thats another issue.

Any help would be very appreciated.

Re: Suffering Packet loss

AnnoyingRegistr
I've Been Here Awhile
Ping Spikes - Packet loss and Calls dropping
 
Hello,
Lately I've been having a bunch of issues with my internet where I would get alot of ping spikes, packet loss and when talking to people online, I would stop hearing people talk for 1 to 5 sec.

Pinging google dns 8.8.8.8 100 times would bring about 5% packet loss. 

I've tried having my modem directly connected to my PC or console but it would still be present.
In my patch panel I saw that I have a 9db attenuator, would removing it change anything?

Here is a review of my Coda signal parameters. I believe I might have an upstream issue, anything I can do myself? 
 
 
Thanks
 
Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 693000000 256QAM 11.300 23 35.780
2 849000000 256QAM 11.000 2 35.595
3 855000000 256QAM 11.400 3 36.387
4 861000000 256QAM 11.400 4 36.387
5 579000000 256QAM 11.300 5 36.387
6 585000000 256QAM 11.500 6 36.387
7 591000000 256QAM 11.600 7 36.387
8 597000000 256QAM 11.500 8 36.610
9 603000000 256QAM 11.200 9 36.387
10 609000000 256QAM 11.600 10 36.387
11 615000000 256QAM 11.500 11 36.387
12 621000000 256QAM 11.100 12 36.387
13 633000000 256QAM 11.200 13 36.387
14 639000000 256QAM 11.300 14 35.780
15 645000000 256QAM 11.700 15 36.387
16 651000000 256QAM 11.700 16 36.610
17 657000000 256QAM 11.500 17 35.780
18 663000000 256QAM 11.400 18 35.595
19 669000000 256QAM 11.600 19 35.595
20 675000000 256QAM 11.700 20 35.780
21 681000000 256QAM 11.300 21 35.595
22 687000000 256QAM 11.300 22 35.780
23 279000000 256QAM 8.700 1 35.595
24 699000000 256QAM 11.200 24 35.595
25 705000000 256QAM 11.300 25 35.780
26 711000000 256QAM 11.300 26 36.387
27 717000000 256QAM 10.800 27 35.780
28 723000000 256QAM 11.000 28 36.387
29 825000000 256QAM 11.500 29 35.780
30 831000000 256QAM 11.400 30 35.780
31 837000000 256QAM 10.900 31 35.780
32 843000000 256QAM 11.000 32 35.595
OFDM Downstream Overview
Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv)
0 NA NA NO NO NO NA
1 4K 275600000 YES YES YES 9.300003
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 23700000 ATDMA - 64QAM 22.250 6 6400000
2 36996000 ATDMA - 64QAM 21.500 8 6400000
3 30596000 ATDMA - 64QAM 22.500 7 6400000
4 13696000 ATDMA - 64QAM 21.000 5 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: Suffering Packet loss

NHTZ2
I've Been Here Awhile
Looks like we're having the exact same issue. Hopefully someone can help us!

Re: Suffering Packet loss

Hello, @NHTZ2 & @AnnoyingRegistr

 

Welcome to the Rogers Community Forums!

 

Dealing with packet loss issues can become a major frustration. We definitely want to help you find a solution to this matter. 

 

@AnnoyingRegistr, thanks so much for posting your signal levels. The downstream & upstream channels appear to be out of the specified range. This is most likely the root cause of the packet loss issues you are experiencing. Has there been any modification to your lines such as the addition of splitters or a signal booster/attenuator that was not installed by a Rogers technician? Is the modem installed in the same location or has it been moved recently?

 

@NHTZ2, to ensure we have covered all of our bases and are not missing any troubleshooting steps, we'd like to review the notes on your file to determine what steps to take to resolve this for you. Please send a Private message to @CommunityHelps so we can pull up your info and get started.

 

Not familiar with our Private messaging system? No worries, Click Here.

 

We look forward to your response.

 

RogersTony

Re: Suffering Packet loss

mikeplumridge
I Plan to Stick Around

As Per Phone call with Rep 'Owen'  - re: #C154345719

 

As reported Last week, and Again today ..

I am once again experiencing intermittent Packet loss; Rogers Rep detects no signal strength problems or issues.

 

When this has happened in the past, typically (after explaining to them 4 times what 'packet loss' is) they forward this the the 'Maintenance Team' ... and they roll out a Rogers truck, and usually report 'Repairs completed to the problematic Node around the corner from me. 

 ... However this time, our Hero Owen, refuses to do that and has insisted that i waste more time by posting here... I highly suspect this is because he simply does not understand what 'packet loss' is.

 

Don't be an Owen, please only reply if you are an Official Rogers Rep and are in a position to Actionably do something. My phone number is on file, i am available 24/7 - call anytime.   

 

 

*NOTES:  Wired Ethernet - Directly to the Rogers Modem; No 3rd party routers/switches; Issue persists on multiple computers, operating systems, Multiple ping locations; Issue is Random totally random (day/evening/night); This is NOT and internal issue.  When present It effects gaming, streaming and surfing.
 (i am Not a novice user, don't waste my time).      ...  and YES, i rebooted the modem.  

 

 PING RESULTS:  (unable to capture screenshot;  copy/paste will have to do) 

 

1)  Example of Ping to External site; (google.ca/bbc.ca/cnn.com all yield similar loss result) 

# Ping statistics for ***withheld*** 
# Packets: Sent = 618, Received = 597, Lost = 21 (3% loss),
# Approximate round trip times in milli-seconds:
# Minimum = 5ms, Maximum = 27ms, Average = 11ms

 

3)  Ping to Modem; zero loss. 

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

 

4) TraceRoutes show no issues, latency, or suspect information. Withheld for privacy.

 

 

 

I look forward to reading your knowledgeable replies 

 

 

Re: Suffering Packet loss

Shahin6470
I Plan to Stick Around

Thank you, this is the exact same problem I been having. 

 

Rogers tech guys do a simple ping test, and see everything is fine. And just move on. 

 

Ping spikes has been happening at RANDOM times. Just because it doesn't happen at that moment when you did a ping test, it doesn't mean everything is fine. Monitor the ping for a week, then come back to me with the result. We live in world that is connected through network, if we don't have consistent internet, then we're done. 

I could write a book about all the excuses I heard over the past 6-8 months from the tech guys. And trust me, I learned so much over these 6-8 months. 

Re: Suffering Packet loss

super_robot
I Plan to Stick Around

Just did a ping test while I was reading... it's not in peak hours and look.. high latency and dropped packet. Just know that you're not crazy nor alone ..

 

Reply from 172.217.0.227: bytes=32 time=141ms TTL=55
Reply from 172.217.0.227: bytes=32 time=25ms TTL=55
Reply from 172.217.0.227: bytes=32 time=34ms TTL=55
Reply from 172.217.0.227: bytes=32 time=52ms TTL=55
Reply from 172.217.0.227: bytes=32 time=17ms TTL=55
Reply from 172.217.0.227: bytes=32 time=55ms TTL=55
Reply from 172.217.0.227: bytes=32 time=40ms TTL=55
Reply from 172.217.0.227: bytes=32 time=64ms TTL=55
Reply from 172.217.0.227: bytes=32 time=59ms TTL=55
Reply from 172.217.0.227: bytes=32 time=86ms TTL=55
Reply from 172.217.0.227: bytes=32 time=64ms TTL=55

Ping statistics for 172.217.0.227:
Packets: Sent = 122, Received = 121, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 141ms, Average = 41ms

 

 

Trace route also displays the latency between the Rogers hops

 

1 1 ms 1 ms 1 ms INTEL_CE_LINUX [192.168.0.1]
2 26 ms 38 ms 26 ms 
3 49 ms 50 ms 49 ms 8082-dgw02.etob.rmgt.net.rogers.com [67.231.220.37]
4 130 ms 42 ms 29 ms 3009-cgw01.bloor.rmgt.net.rogers.com [69.63.248.185]
5 103 ms 43 ms 103 ms 209.148.230.14
6 * * * Request timed out.
7 18 ms 66 ms 36 ms 108.170.250.241
8 17 ms 23 ms 32 ms 108.170.226.217
9 15 ms 16 ms 13 ms dfw06s38-in-f3.1e100.net [172.217.0.227]

Re: Suffering Packet loss

NHTZ2
I've Been Here Awhile
Hey guys,

Im talking to Rogers support through private messages through the forums and its not helping me at all.

As the comments above me are mentioning, there is an issue. You guys keep asking me to run tests, theres tests being done on your end, and youre sending some people to my house over and over. The issue persists and Im sick of it.

My games are lagging a stupid amount. My shows are freezing a stupid amount. My meetings are being dropped a stupid amount. Ive downloaded applications that monitor this internet, and theyre able to identity my sudden packet loss and ping spikes. The issues shown in the screenehots were appearing the exact same time everything was freezing, but the Rogers support doesnt even look at them because they can only look at their own results... which are useless. They arent finding the problem.

These screenshots show the random cut in service and packet loss. Again, I ran the application as soon as everything in the house started freezing, and I always run to my laptop to run the tests Rogers requested, but it goes back to normal by then.
http://imgur.com/gallery/8ZiuTQx
http://imgur.com/gallery/HsKLPSQ

The house next door is even having the EXACT same issues. Rogers has a problem they are not capable of finding, let alone fixing. If you refer to my previous comment on this thread, Ive tried everything and Ive been talking to a bunch of Rogers support since then.

Me having to buy an unlimited Data plan from Telus to hotspot my game consoles and work computer is UNACCEPTABLE.

I think I will complain to CRTC or CCTS. I cant handle this anymore.

Re: Suffering Packet loss

rpi
I've Been Around

Hello,

 

I have been experiencing packet loss (lag) while trying to play games from my xbox/pc (both wired). I contacted rogers support and they said everything is "fine" judging from the "graphs" they use. I don't know what the issue could be so I'm posting my router's stats here. It would be a huge help if someone could spot the problem! Thanks

 

Upstream Overview

Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 36996000 ATDMA - 64QAM 35.000 4 6400000
2 22100000 ATDMA - 64QAM 38.250 1 3200000
3 30596000 ATDMA - 64QAM 34.750 3 6400000
4 25300000 ATDMA - 64QAM 38.250 2 3200000

 

Downstream Overview

Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 591000000 256QAM 5.600 7 40.366
2 855000000 256QAM 2.400 3 38.983
3 861000000 256QAM 2.100 4 40.366
4 579000000 256QAM 5.900 5 40.366
5 585000000 256QAM 5.600 6 40.366
6 849000000 256QAM 2.500 2 38.983
7 597000000 256QAM 5.100 8 40.366
8 603000000 256QAM 5.100 9 40.366
9 609000000 256QAM 4.700 10 40.946
10 615000000 256QAM 5.100 11 40.366
11 621000000 256QAM 5.100 12 40.366
12 633000000 256QAM 5.200 13 40.366
13 639000000 256QAM 5.100 14 40.366
14 645000000 256QAM 5.300 15 40.366
15 651000000 256QAM 5.300 16 40.366
16 657000000 256QAM 5.600 17 40.946
17 663000000 256QAM 5.300 18 40.366
18 669000000 256QAM 5.300 19 40.366
19 675000000 256QAM 5.000 20 40.366
20 681000000 256QAM 5.200 21 40.366
21 687000000 256QAM 5.200 22 40.366
22 693000000 256QAM 5.500 23 40.366
23 699000000 256QAM 5.300 24 40.366
24 705000000 256QAM 5.200 25 40.946
25 711000000 256QAM 5.400 26 40.366
26 717000000 256QAM 5.400 27 40.946
27 723000000 256QAM 5.800 28 40.366
28 825000000 256QAM 3.600 29 40.366
29 831000000 256QAM 3.600 30 40.366
30 837000000 256QAM 3.300 31 40.366
31 843000000 256QAM 3.100 32 38.983
32 279000000 256QAM 8.500 1

38.983

Re: Suffering Packet loss

super_robot
I Plan to Stick Around

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

 

 

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

Re: Suffering Packet loss

RogersMoin
Moderator

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

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

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

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. 



Re: Suffering Packet loss

Ozeo
I've Been Around

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.

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

Re: Suffering Packet loss

raymond111
I Plan to Stick Around

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?