01-30-2020 12:15 AM - last edited on 01-30-2020 08:22 AM by RogersTony
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 ***
01-30-2020 12:23 AM
01-30-2020 12:28 AM
01-30-2020 12:58 AM
01-30-2020 01:22 AM
01-30-2020 01:41 AM
01-30-2020 01:42 AM
01-30-2020 01:44 AM
01-30-2020 01:46 AM
01-30-2020 01:55 AM
01-30-2020 08:27 AM
01-30-2020 03:01 PM - edited 01-30-2020 03:08 PM
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
01-30-2020 07:52 PM - edited 01-30-2020 07:56 PM
@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 184.108.40.206
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?
01-30-2020 08:00 PM
@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.
01-30-2020 08:36 PM
01-30-2020 09:02 PM
01-30-2020 09:23 PM
@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
01-30-2020 09:45 PM
@DatalinkHere are the final results:
Ping statistics for 220.127.116.11:
Packets: Sent = 3600, Received = 3600, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 612ms, Average = 45ms
01-30-2020 09:59 PM
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 18.104.22.168
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 🙂
01-30-2020 10:23 PM
Results to the DNS
Ping statistics for 22.214.171.124:
Packets: Sent = 169, Received = 127, Lost = 42 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 142ms, Average = 43ms
01-30-2020 10:29 PM - edited 01-30-2020 10:34 PM
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
ping -t 126.96.36.199
ping -t 188.8.131.52
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.