cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
chillinflute
Beginner
502 Views
Message 1 of 5

OS X experiencing ping spikes but Windows partition fine?

Hi all

 

We've recently upgraded to infinity and got the BT Hub5A, and all the windows computers in the house appear to have no problem with the broadband, however, my Macbook pro is getting serious ping spikes (ms changing from 23 to >240 in a matter of seconds then going back down, the cycle occuring at pretty regular intervals).

(Using Terminal, Windows command prompt returned a solid 23.3/23.4 ms to google.)

When pinging Google, this was the result:

ChristohersMBP2:~ Chill$ ping www.google.com
PING www.google.com (216.58.211.164): 56 data bytes
64 bytes from 216.58.211.164: icmp_seq=0 ttl=49 time=22.894 ms
64 bytes from 216.58.211.164: icmp_seq=1 ttl=49 time=70.030 ms
64 bytes from 216.58.211.164: icmp_seq=2 ttl=49 time=94.813 ms
64 bytes from 216.58.211.164: icmp_seq=3 ttl=49 time=171.159 ms
64 bytes from 216.58.211.164: icmp_seq=4 ttl=49 time=189.854 ms
64 bytes from 216.58.211.164: icmp_seq=5 ttl=49 time=252.267 ms
64 bytes from 216.58.211.164: icmp_seq=6 ttl=49 time=23.006 ms
64 bytes from 216.58.211.164: icmp_seq=7 ttl=49 time=23.261 ms
64 bytes from 216.58.211.164: icmp_seq=8 ttl=49 time=23.008 ms
64 bytes from 216.58.211.164: icmp_seq=9 ttl=49 time=23.094 ms
64 bytes from 216.58.211.164: icmp_seq=10 ttl=49 time=22.717 ms
64 bytes from 216.58.211.164: icmp_seq=11 ttl=49 time=23.216 ms
64 bytes from 216.58.211.164: icmp_seq=12 ttl=49 time=29.079 ms
64 bytes from 216.58.211.164: icmp_seq=13 ttl=49 time=77.256 ms
64 bytes from 216.58.211.164: icmp_seq=14 ttl=49 time=126.274 ms
64 bytes from 216.58.211.164: icmp_seq=15 ttl=49 time=168.643 ms
64 bytes from 216.58.211.164: icmp_seq=16 ttl=49 time=215.384 ms
64 bytes from 216.58.211.164: icmp_seq=17 ttl=49 time=239.831 ms
64 bytes from 216.58.211.164: icmp_seq=18 ttl=49 time=23.038 ms
64 bytes from 216.58.211.164: icmp_seq=19 ttl=49 time=48.960 ms
64 bytes from 216.58.211.164: icmp_seq=20 ttl=49 time=22.684 ms
64 bytes from 216.58.211.164: icmp_seq=21 ttl=49 time=22.788 ms
64 bytes from 216.58.211.164: icmp_seq=22 ttl=49 time=43.337 ms
64 bytes from 216.58.211.164: icmp_seq=23 ttl=49 time=25.426 ms
64 bytes from 216.58.211.164: icmp_seq=24 ttl=49 time=60.251 ms
64 bytes from 216.58.211.164: icmp_seq=25 ttl=49 time=103.746 ms
64 bytes from 216.58.211.164: icmp_seq=26 ttl=49 time=147.716 ms
64 bytes from 216.58.211.164: icmp_seq=27 ttl=49 time=191.991 ms
64 bytes from 216.58.211.164: icmp_seq=28 ttl=49 time=234.577 ms
64 bytes from 216.58.211.164: icmp_seq=29 ttl=49 time=23.484 ms
64 bytes from 216.58.211.164: icmp_seq=30 ttl=49 time=27.477 ms
64 bytes from 216.58.211.164: icmp_seq=31 ttl=49 time=23.225 ms
64 bytes from 216.58.211.164: icmp_seq=32 ttl=49 time=31.088 ms
64 bytes from 216.58.211.164: icmp_seq=33 ttl=49 time=23.267 ms
64 bytes from 216.58.211.164: icmp_seq=34 ttl=49 time=23.375 ms
64 bytes from 216.58.211.164: icmp_seq=35 ttl=49 time=35.235 ms
64 bytes from 216.58.211.164: icmp_seq=36 ttl=49 time=84.549 ms
64 bytes from 216.58.211.164: icmp_seq=37 ttl=49 time=126.088 ms
^C
--- www.google.com ping statistics ---
38 packets transmitted, 38 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.684/82.055/252.267/74.093 ms
ChristohersMBP2:~ Chill$ 

Pinging the hub itself:

ChristohersMBP2:~ Chill$ ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=212.496 ms
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=1.850 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=30.377 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=1.828 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=1.777 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=20.832 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=1.815 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=1.792 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=40.330 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=88.401 ms
64 bytes from 192.168.1.254: icmp_seq=10 ttl=64 time=133.878 ms
64 bytes from 192.168.1.254: icmp_seq=11 ttl=64 time=180.428 ms
64 bytes from 192.168.1.254: icmp_seq=12 ttl=64 time=1.858 ms
64 bytes from 192.168.1.254: icmp_seq=13 ttl=64 time=5.608 ms
64 bytes from 192.168.1.254: icmp_seq=14 ttl=64 time=13.985 ms
64 bytes from 192.168.1.254: icmp_seq=15 ttl=64 time=1.832 ms
64 bytes from 192.168.1.254: icmp_seq=16 ttl=64 time=3.203 ms
64 bytes from 192.168.1.254: icmp_seq=17 ttl=64 time=14.555 ms
64 bytes from 192.168.1.254: icmp_seq=18 ttl=64 time=10.956 ms
64 bytes from 192.168.1.254: icmp_seq=19 ttl=64 time=30.578 ms
64 bytes from 192.168.1.254: icmp_seq=20 ttl=64 time=75.118 ms
64 bytes from 192.168.1.254: icmp_seq=21 ttl=64 time=123.044 ms
^C
--- 192.168.1.254 ping statistics ---
22 packets transmitted, 22 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.777/45.297/212.496/61.644 ms
ChristohersMBP2:~ Chill$ 

And a traceroute to Google:

ChristohersMBP2:~ Chill$ traceroute www.google.com
traceroute to www.google.com (216.58.211.164), 64 hops max, 52 byte packets
 1  api (192.168.1.254)  2.113 ms  10.377 ms  1.820 ms
 2  * * *
 3  * * *
 4  213.120.158.141 (213.120.158.141)  5.490 ms  9.235 ms  6.586 ms
 5  213.120.181.206 (213.120.181.206)  8.602 ms  239.723 ms  8.838 ms
 6  217.41.169.199 (217.41.169.199)  8.308 ms  8.367 ms  25.268 ms
 7  213.120.179.83 (213.120.179.83)  12.510 ms  8.634 ms  8.316 ms
 8  acc2-xe-0-3-0.sf.21cn-ipp.bt.net (109.159.251.201)  7.822 ms
    acc2-xe-10-2-0.sf.21cn-ipp.bt.net (109.159.251.197)  8.319 ms
    acc2-xe-0-2-1.sf.21cn-ipp.bt.net (109.159.251.213)  8.291 ms
 9  acc1-10gige-5-2-1.sf.21cn-ipp.bt.net (109.159.251.187)  16.501 ms
    core1-te-0-3-0-3.ilford.ukcore.bt.net (109.159.251.163)  23.025 ms
    core1-te0-13-0-2.ealing.ukcore.bt.net (109.159.251.9)  13.787 ms
10  peer3-te0-1-0-5.telehouse.ukcore.bt.net (109.159.254.249)  15.089 ms
    peer4-te0-1-0-4.telehouse.ukcore.bt.net (109.159.255.93)  17.092 ms  16.185 ms
11  109.159.253.67 (109.159.253.67)  25.907 ms  14.814 ms  17.010 ms
12  209.85.244.182 (209.85.244.182)  230.965 ms
    209.85.244.184 (209.85.244.184)  17.611 ms
    209.85.244.182 (209.85.244.182)  13.315 ms
13  proxy.google.com (216.239.51.5)  16.201 ms
    209.85.245.2 (209.85.245.2)  15.143 ms  45.681 ms
14  209.85.250.216 (209.85.250.216)  22.968 ms  38.548 ms  22.788 ms
15  209.85.241.139 (209.85.241.139)  27.301 ms  24.123 ms  26.855 ms
16  dub08s01-in-f4.1e100.net (216.58.211.164)  24.552 ms  23.186 ms  25.854 ms
ChristohersMBP2:~ Chill$ 

The strangest thing is the problem is only occuring on the OS X operating system: my Windows partition has a steady 23.3ish ping. I have no idea why this could be happening (can't be hardware because that would affect the Windows partition, can't be interference or the other computers would get it too and moving the laptop would affect the results which it doesn't). Spoke to support although the guy said that my results when pinging Google were not important and that I should rely on Speedtest.net, but did not mention the traceroute. 

I know a thing or two about computers, but broadband and Wifi are not my area; layman's terms would be appreciated Smiley Wink.

 

EDIT: We are also having issues with our Panasonic smart TV when connecting to internet: the TV will connect to the router, but not the internet. Saying "IP address not acquired". Could this be a related issue?

0 Ratings
Reply
4 REPLIES 4
Distinguished Sage
Distinguished Sage
483 Views
Message 2 of 5

Re: OS X experiencing ping spikes but Windows partition fine?

Welcome to this user forum.

 

Were these figures taken usind a wireless connection. or using a direct Ethernet cable?

 

Apple devices have problems with wireless connections when both 2.4 and 5 GHz SSIDs have the same name, so try renaming the 5GHz SSID.

 

Also make sure that smart setup is disabled.

 

0 Ratings
Reply
chillinflute
Beginner
460 Views
Message 3 of 5

Re: OS X experiencing ping spikes but Windows partition fine?

Wireless.

Changed the SSID and then pinged Google again. Once connected to 5GHz and then with 2.4GHz:

Last login: Sat Feb 28 22:35:11 on ttys001
ChristohersMBP2:~ Chill$ ping www.google.com
PING www.google.com (216.58.211.164): 56 data bytes
64 bytes from 216.58.211.164: icmp_seq=0 ttl=49 time=22.793 ms
64 bytes from 216.58.211.164: icmp_seq=1 ttl=49 time=22.672 ms
64 bytes from 216.58.211.164: icmp_seq=2 ttl=49 time=331.747 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 216.58.211.164: icmp_seq=5 ttl=49 time=149.959 ms
64 bytes from 216.58.211.164: icmp_seq=6 ttl=49 time=330.347 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
64 bytes from 216.58.211.164: icmp_seq=10 ttl=49 time=310.050 ms
Request timeout for icmp_seq 11
64 bytes from 216.58.211.164: icmp_seq=12 ttl=49 time=328.110 ms
64 bytes from 216.58.211.164: icmp_seq=13 ttl=49 time=22.647 ms
64 bytes from 216.58.211.164: icmp_seq=14 ttl=49 time=29.046 ms
64 bytes from 216.58.211.164: icmp_seq=15 ttl=49 time=24.396 ms
64 bytes from 216.58.211.164: icmp_seq=16 ttl=49 time=34.540 ms
64 bytes from 216.58.211.164: icmp_seq=17 ttl=49 time=22.866 ms
64 bytes from 216.58.211.164: icmp_seq=18 ttl=49 time=39.457 ms
64 bytes from 216.58.211.164: icmp_seq=19 ttl=49 time=84.409 ms
64 bytes from 216.58.211.164: icmp_seq=20 ttl=49 time=130.144 ms
64 bytes from 216.58.211.164: icmp_seq=21 ttl=49 time=177.449 ms
64 bytes from 216.58.211.164: icmp_seq=22 ttl=49 time=221.424 ms
64 bytes from 216.58.211.164: icmp_seq=23 ttl=49 time=246.443 ms
64 bytes from 216.58.211.164: icmp_seq=24 ttl=49 time=22.723 ms
^C
--- www.google.com ping statistics ---
25 packets transmitted, 19 packets received, 24.0% packet loss
round-trip min/avg/max/stddev = 22.647/134.275/331.747/120.303 ms
ChristohersMBP2:~ Chill$ ping www.google.com
PING www.google.com (216.58.211.164): 56 data bytes
64 bytes from 216.58.211.164: icmp_seq=0 ttl=49 time=51.110 ms
64 bytes from 216.58.211.164: icmp_seq=1 ttl=49 time=26.455 ms
64 bytes from 216.58.211.164: icmp_seq=2 ttl=49 time=26.006 ms
64 bytes from 216.58.211.164: icmp_seq=3 ttl=49 time=62.662 ms
64 bytes from 216.58.211.164: icmp_seq=4 ttl=49 time=110.530 ms
64 bytes from 216.58.211.164: icmp_seq=5 ttl=49 time=148.919 ms
64 bytes from 216.58.211.164: icmp_seq=6 ttl=49 time=204.998 ms
64 bytes from 216.58.211.164: icmp_seq=7 ttl=49 time=284.683 ms
64 bytes from 216.58.211.164: icmp_seq=8 ttl=49 time=22.831 ms
64 bytes from 216.58.211.164: icmp_seq=9 ttl=49 time=36.711 ms
64 bytes from 216.58.211.164: icmp_seq=10 ttl=49 time=32.989 ms
64 bytes from 216.58.211.164: icmp_seq=11 ttl=49 time=48.994 ms
64 bytes from 216.58.211.164: icmp_seq=12 ttl=49 time=231.237 ms
64 bytes from 216.58.211.164: icmp_seq=13 ttl=49 time=270.455 ms
64 bytes from 216.58.211.164: icmp_seq=14 ttl=49 time=160.460 ms
64 bytes from 216.58.211.164: icmp_seq=15 ttl=49 time=344.179 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
64 bytes from 216.58.211.164: icmp_seq=16 ttl=49 time=2382.025 ms
Request timeout for icmp_seq 19
64 bytes from 216.58.211.164: icmp_seq=17 ttl=49 time=3841.393 ms
64 bytes from 216.58.211.164: icmp_seq=18 ttl=49 time=2926.199 ms
64 bytes from 216.58.211.164: icmp_seq=19 ttl=49 time=3394.520 ms
64 bytes from 216.58.211.164: icmp_seq=20 ttl=49 time=2674.620 ms
64 bytes from 216.58.211.164: icmp_seq=21 ttl=49 time=1947.679 ms
64 bytes from 216.58.211.164: icmp_seq=22 ttl=49 time=944.662 ms
64 bytes from 216.58.211.164: icmp_seq=23 ttl=49 time=122.565 ms
64 bytes from 216.58.211.164: icmp_seq=24 ttl=49 time=37.572 ms
64 bytes from 216.58.211.164: icmp_seq=25 ttl=49 time=37.325 ms
64 bytes from 216.58.211.164: icmp_seq=26 ttl=49 time=95.831 ms
^C
--- www.google.com ping statistics ---
27 packets transmitted, 27 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.831/758.060/3841.393/1175.492 ms
ChristohersMBP2:~ Chill$ 

 So I've still got the same issues: large ping spikes at pretty regular intervals.

Any ideas?

0 Ratings
Reply
davidramsay
Aspiring Expert
449 Views
Message 4 of 5

Re: OS X experiencing ping spikes but Windows partition fine?

What is your OS version on OS X and what is your Mac model number?
0 Ratings
Reply
chillinflute
Beginner
438 Views
Message 5 of 5

Re: OS X experiencing ping spikes but Windows partition fine?

OSX Yosemite (10.10.2)
Don't know the number but: 2.3GHz Intel Core i7, Mid 2012, 15"
0 Ratings
Reply