My download and upload speeds are pretty good, and my ping is mostly at around 17(tested on about 10 sites), but I will frequently have spikes of up to 150ms or even 250ms! (Wifi)
On Ethernet, it is even worse! My average ping (tested on multiple sites), is 67ms, with spikes of 670ms
Thanks,
Jeet
Hey jeet,
Thanks for reaching out! There may be several reasons why you are noticing issues such as poor signal to your modem or a setup issue involving 3rd party routers/switches. What troubleshooting steps have you tried so far? Can you provide the WinMTR or Traceroutes reports with the normal ping and spikes?
Cheers,
Tony | Community Mod.
Hi Tony, I don't think a poor signal is an issue, as I pinged my router, and it only showed a 3ms delay. I didn't use cmd prompt to test it, (I used a website with servers very close by), so I will attach a picture of a test I just performed.
I don't believe a setup issue is a problem, as I am using the router/modem, provided by Shaw; it has been replaced recently, so that shouldn't be a problem. I have enabled throughput booster in the adapter settings, which appears to have reduced the frequency of the lag spikes.
Thanks,
Jeet
Are you using any of your own networking equipment in the home, like a 3rd-party router or wifi extender? Do the results seem to replicate on other devices, or does it mostly just seem to happen on one particular device?
We are not using any 3rd party equipment, only the modem/router provided by Shaw.
The problem is happening a little on another laptop, but more severely on this one.
This problem occurs with DNS settings and without.
Thanks,
Jeet
I'm having a similar issue... Check this out: Note the bolded one below
Last login: Mon Sep 7 10:39:42 on console
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
Waynes-Air-5:~ wrambow$ ping google.ca
PING google.ca (172.217.3.163): 56 data bytes
64 bytes from 172.217.3.163: icmp_seq=0 ttl=118 time=23.125 ms
64 bytes from 172.217.3.163: icmp_seq=1 ttl=118 time=27.110 ms
64 bytes from 172.217.3.163: icmp_seq=2 ttl=118 time=29.274 ms
64 bytes from 172.217.3.163: icmp_seq=3 ttl=118 time=23.261 ms
64 bytes from 172.217.3.163: icmp_seq=4 ttl=118 time=28.876 ms
64 bytes from 172.217.3.163: icmp_seq=5 ttl=118 time=29.016 ms
64 bytes from 172.217.3.163: icmp_seq=6 ttl=118 time=499.900 ms
64 bytes from 172.217.3.163: icmp_seq=7 ttl=118 time=28.825 ms
64 bytes from 172.217.3.163: icmp_seq=8 ttl=118 time=29.202 ms
64 bytes from 172.217.3.163: icmp_seq=9 ttl=118 time=45.424 ms
64 bytes from 172.217.3.163: icmp_seq=10 ttl=118 time=30.666 ms
64 bytes from 172.217.3.163: icmp_seq=11 ttl=118 time=23.654 ms
64 bytes from 172.217.3.163: icmp_seq=12 ttl=118 time=28.518 ms
64 bytes from 172.217.3.163: icmp_seq=13 ttl=118 time=23.408 ms
64 bytes from 172.217.3.163: icmp_seq=14 ttl=118 time=28.377 ms
64 bytes from 172.217.3.163: icmp_seq=15 ttl=118 time=28.907 ms
64 bytes from 172.217.3.163: icmp_seq=16 ttl=118 time=28.625 ms
64 bytes from 172.217.3.163: icmp_seq=17 ttl=118 time=34.523 ms
64 bytes from 172.217.3.163: icmp_seq=18 ttl=118 time=24.032 ms
64 bytes from 172.217.3.163: icmp_seq=19 ttl=118 time=22.852 ms
64 bytes from 172.217.3.163: icmp_seq=20 ttl=118 time=27.536 ms
64 bytes from 172.217.3.163: icmp_seq=21 ttl=118 time=27.338 ms
@Rambolious -- one "slow" response (out of many) to the PING command does not make it a "problem".
Some routers on the Internet "path" between your computer and Google's server are configured to treat PING traffic as "low priority".
Does your operating system have a TRACEROUTE (or TRACERT or TRACETE) command? Seeing the output from that command might identify which of those routers occasionally takes longer than normal to pass the PING packet through it.
Also, the output from TRACEROUTE may show that the "bad" router is outside of Shaw's network, leaving Shaw with no possibly remedy.
Tracing route to www.google.ca [216.58.217.35]
... (first 4 routers on Shaw network have been omitted -- not relevant here)
5 11 ms 17 ms 12 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
6 11 ms 12 ms 26 ms 72.14.221.102
7 11 ms 14 ms 11 ms 108.170.245.113
8 10 ms 12 ms 15 ms 74.125.253.67
9 12 ms 11 ms 10 ms sea15s08-in-f3.1e100.net [216.58.217.35]
Note: That "WA" router is Shaw's router connecting to "Washington State".
That "72.14.221.102" router is on Google's network.
These are perfectly normal response-times.
Repeating:
5 19 ms 11 ms 13 ms rc1wt-be40.wa.shawcable.net [66.163.68.18]
6 11 ms 11 ms 15 ms 72.14.221.102
7 10 ms 10 ms 11 ms 108.170.245.113
8 19 ms 10 ms 10 ms 74.125.253.67
9 19 ms 12 ms 10 ms sea15s08-in-f3.1e100.net [216.58.217.35]
shows some variability, but nothing like "499.9" milliseconds.