Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

13 points

2016 MBP Touch Bar - TERRIBLE Wifi speeds

New 13" 2016 MBP w/Touchbar here. Experiencing bad wifi issues (extreme latency, packet loss, general slow speeds) on 5ghz radio bands. I have several laptops that do NOT have this issue, so I've isolated it down to definitely being something on the new Mac.

Couple things off the bat:

It's not my wifi; tested on multiple machines
Issue happens on 5ghz radio (802.11ac) but haven't checked (don't care for) on 2.4 ghz
Removing the recommended .plist files (see below) from this article worked, but eventually went back to slow speeds (article: http://osxdaily.com/2016/09/22/fix-wi-fi-problems-macos-sierra/)

com.apple.airport.preferences.plist

com.apple.network.eapolclient.configuration.plist

com.apple.wifi.message-tracer.plist

NetworkInterfaces.plist

preferences.plist

Ping Examples:

64 bytes from 172.217.5.228: icmp_seq=896 ttl=54 time=16.924 ms

64 bytes from 172.217.5.228: icmp_seq=897 ttl=54 time=18.253 ms

64 bytes from 172.217.5.228: icmp_seq=898 ttl=54 time=18.136 ms

Request timeout for icmp_seq 900

64 bytes from 172.217.5.228: icmp_seq=899 ttl=54 time=2483.505 ms

64 bytes from 172.217.5.228: icmp_seq=900 ttl=54 time=1482.324 ms

64 bytes from 172.217.5.228: icmp_seq=901 ttl=54 time=499.586 ms

64 bytes from 172.217.5.228: icmp_seq=902 ttl=54 time=19.220 ms

64 bytes from 172.217.5.228: icmp_seq=903 ttl=54 time=18.348 ms

64 bytes from 172.217.5.228: icmp_seq=904 ttl=54 time=20.390 ms

64 bytes from 172.217.5.228: icmp_seq=905 ttl=54 time=19.897 ms

PINGs go fine for a while but eventually get lost or otherwise high latency.

MacBook Pro with Retina display, macOS Sierra (10.12.3)

Posted on Feb 9, 2017 8:17 AM

Best reply

JRadek

Level 1

9 points

Posted on Jul 5, 2017 11:50 PM

Hi AndyH28,

I experienced the same problems like you: High latency spikes, when I am on Wifi. As I work quite a time via SSH on remote machines, a constant latency is crucial. Otherwise typing is horrible.

I googled around and found the same answers like you got:

- This 5GHz thing

- Distance to router

- Hardware issues

However I couldn't believe those answers and none of them applied to my problem. The only thin that worked was using a wired connection.

During the last weeks I spend many hours investigating the problem. My start always was a "ping session" like this:

64 bytes from 216.58.205.227: icmp_seq=53 ttl=56 time=32.462 ms

64 bytes from 216.58.205.227: icmp_seq=54 ttl=56 time=98.429 ms

64 bytes from 216.58.205.227: icmp_seq=55 ttl=56 time=149.815 ms

64 bytes from 216.58.205.227: icmp_seq=56 ttl=56 time=32.795 ms

64 bytes from 216.58.205.227: icmp_seq=57 ttl=56 time=12.920 ms

64 bytes from 216.58.205.227: icmp_seq=58 ttl=56 time=12.892 ms

64 bytes from 216.58.205.227: icmp_seq=59 ttl=56 time=12.899 ms

64 bytes from 216.58.205.227: icmp_seq=60 ttl=56 time=12.902 ms

64 bytes from 216.58.205.227: icmp_seq=61 ttl=56 time=12.851 ms

64 bytes from 216.58.205.227: icmp_seq=62 ttl=56 time=223.226 ms

64 bytes from 216.58.205.227: icmp_seq=63 ttl=56 time=148.654 ms

64 bytes from 216.58.205.227: icmp_seq=64 ttl=56 time=206.037 ms

64 bytes from 216.58.205.227: icmp_seq=65 ttl=56 time=268.655 ms

64 bytes from 216.58.205.227: icmp_seq=66 ttl=56 time=17.800 ms

64 bytes from 216.58.205.227: icmp_seq=67 ttl=56 time=47.629 ms

64 bytes from 216.58.205.227: icmp_seq=68 ttl=56 time=143.621 ms

64 bytes from 216.58.205.227: icmp_seq=69 ttl=56 time=29.277 ms

64 bytes from 216.58.205.227: icmp_seq=70 ttl=56 time=88.440 ms

64 bytes from 216.58.205.227: icmp_seq=71 ttl=56 time=139.968 ms

64 bytes from 216.58.205.227: icmp_seq=72 ttl=56 time=12.865 ms

64 bytes from 216.58.205.227: icmp_seq=73 ttl=56 time=12.303 ms

64 bytes from 216.58.205.227: icmp_seq=74 ttl=56 time=12.941 ms

64 bytes from 216.58.205.227: icmp_seq=75 ttl=56 time=12.903 ms

64 bytes from 216.58.205.227: icmp_seq=76 ttl=56 time=12.924 ms

64 bytes from 216.58.205.227: icmp_seq=77 ttl=56 time=182.978 ms

64 bytes from 216.58.205.227: icmp_seq=78 ttl=56 time=104.746 ms

64 bytes from 216.58.205.227: icmp_seq=79 ttl=56 time=154.806 ms

64 bytes from 216.58.205.227: icmp_seq=80 ttl=56 time=217.942 ms

64 bytes from 216.58.205.227: icmp_seq=81 ttl=56 time=275.957 ms

64 bytes from 216.58.205.227: icmp_seq=82 ttl=56 time=12.061 ms

64 bytes from 216.58.205.227: icmp_seq=83 ttl=56 time=95.393 ms

64 bytes from 216.58.205.227: icmp_seq=84 ttl=56 time=140.254 ms

64 bytes from 216.58.205.227: icmp_seq=85 ttl=56 time=25.608 ms

64 bytes from 216.58.205.227: icmp_seq=86 ttl=56 time=81.580 ms

64 bytes from 216.58.205.227: icmp_seq=87 ttl=56 time=12.871 ms

64 bytes from 216.58.205.227: icmp_seq=88 ttl=56 time=12.501 ms

64 bytes from 216.58.205.227: icmp_seq=89 ttl=56 time=13.127 ms

64 bytes from 216.58.205.227: icmp_seq=90 ttl=56 time=12.874 ms

64 bytes from 216.58.205.227: icmp_seq=91 ttl=56 time=12.908 ms

As you might see, there is some pattern (highlighted in both).

After capturing network traffic with Wireshark, and opening/closing the programs I normally used, I identified multiple programs which, when running, trigger this behaviour. Meaning: Once I run the particular program the latency pattern shows and after closing, the latency is gone.

Unfortunately, two of these programs are constantly running on my machine, because I use them a lot:

Now that I knew the trouble causing programs, I scanned their preferences for mysterious settings. Both tools require a network connections for some feature:

The database tool searches for "remote options" (whatever that is)
The TEX tool queries a grammar checker

After disabling this options, the programs can run and don not interfere with the network connection. And I my case, I didn't need the features I disabled.

So, I don't know if this is the ultimate solution, but I'm happy right now. Maybe there is something else, because like I said: there are no issues (independent from program options), when the MAC is connected via ethernet. It is a Wifi only issue.

Hope I could help

View in context

41 replies

epski

Level 1

4 points

Nov 14, 2017 10:27 AM in response to AndyH28

I tried 3 different 2016 Touch Bar MBPs, and each of them had Wi-Fi speeds roughly half of other computers that I would, including a 2013 MacBook Air. I'm on a 2017 now, and I haven't experienced any issues.

Nov 26, 2017 4:13 PM in response to leutholl

Thank you! Uninstalling AVID solved this for me:

64 bytes from 192.168.1.1: icmp_seq=277 ttl=64 time=1.424 ms

64 bytes from 192.168.1.1: icmp_seq=278 ttl=64 time=1.796 ms

64 bytes from 192.168.1.1: icmp_seq=279 ttl=64 time=2.327 ms

64 bytes from 192.168.1.1: icmp_seq=280 ttl=64 time=3.022 ms

64 bytes from 192.168.1.1: icmp_seq=281 ttl=64 time=2.314 ms

64 bytes from 192.168.1.1: icmp_seq=282 ttl=64 time=1.388 ms

64 bytes from 192.168.1.1: icmp_seq=283 ttl=64 time=450.727 ms

64 bytes from 192.168.1.1: icmp_seq=284 ttl=64 time=15.325 ms

64 bytes from 192.168.1.1: icmp_seq=285 ttl=64 time=494.222 ms

64 bytes from 192.168.1.1: icmp_seq=286 ttl=64 time=266.329 ms

64 bytes from 192.168.1.1: icmp_seq=287 ttl=64 time=1.797 ms

64 bytes from 192.168.1.1: icmp_seq=288 ttl=64 time=2.197 ms

64 bytes from 192.168.1.1: icmp_seq=289 ttl=64 time=415.711 ms

64 bytes from 192.168.1.1: icmp_seq=290 ttl=64 time=675.186 ms

64 bytes from 192.168.1.1: icmp_seq=291 ttl=64 time=442.377 ms

64 bytes from 192.168.1.1: icmp_seq=292 ttl=64 time=207.616 ms

64 bytes from 192.168.1.1: icmp_seq=293 ttl=64 time=1.313 ms

64 bytes from 192.168.1.1: icmp_seq=294 ttl=64 time=0.826 ms

64 bytes from 192.168.1.1: icmp_seq=295 ttl=64 time=0.947 ms

64 bytes from 192.168.1.1: icmp_seq=296 ttl=64 time=2.339 ms

64 bytes from 192.168.1.1: icmp_seq=297 ttl=64 time=1.123 ms

64 bytes from 192.168.1.1: icmp_seq=298 ttl=64 time=1.089 ms

Request timeout for icmp_seq 299

64 bytes from 192.168.1.1: icmp_seq=300 ttl=64 time=679.680 ms

64 bytes from 192.168.1.1: icmp_seq=301 ttl=64 time=447.439 ms

Request timeout for icmp_seq 302

64 bytes from 192.168.1.1: icmp_seq=303 ttl=64 time=1.381 ms

64 bytes from 192.168.1.1: icmp_seq=304 ttl=64 time=1.638 ms

64 bytes from 192.168.1.1: icmp_seq=305 ttl=64 time=360.234 ms

Request timeout for icmp_seq 306

Request timeout for icmp_seq 307

64 bytes from 192.168.1.1: icmp_seq=308 ttl=64 time=474.117 ms

64 bytes from 192.168.1.1: icmp_seq=309 ttl=64 time=29.008 ms

Request timeout for icmp_seq 310

Request timeout for icmp_seq 311

64 bytes from 192.168.1.1: icmp_seq=312 ttl=64 time=316.510 ms

64 bytes from 192.168.1.1: icmp_seq=313 ttl=64 time=12.644 ms

64 bytes from 192.168.1.1: icmp_seq=314 ttl=64 time=1.414 ms

64 bytes from 192.168.1.1: icmp_seq=315 ttl=64 time=381.384 ms

64 bytes from 192.168.1.1: icmp_seq=316 ttl=64 time=643.340 ms

64 bytes from 192.168.1.1: icmp_seq=317 ttl=64 time=414.385 ms

64 bytes from 192.168.1.1: icmp_seq=318 ttl=64 time=185.574 ms

64 bytes from 192.168.1.1: icmp_seq=319 ttl=64 time=1.645 ms

64 bytes from 192.168.1.1: icmp_seq=320 ttl=64 time=2.223 ms

64 bytes from 192.168.1.1: icmp_seq=321 ttl=64 time=145.228 ms

64 bytes from 192.168.1.1: icmp_seq=322 ttl=64 time=404.183 ms

64 bytes from 192.168.1.1: icmp_seq=323 ttl=64 time=169.934 ms

Request timeout for icmp_seq 324

64 bytes from 192.168.1.1: icmp_seq=325 ttl=64 time=3.207 ms

64 bytes from 192.168.1.1: icmp_seq=326 ttl=64 time=2.261 ms

---- killed avid here

64 bytes from 192.168.1.1: icmp_seq=327 ttl=64 time=0.933 ms

64 bytes from 192.168.1.1: icmp_seq=328 ttl=64 time=0.878 ms

64 bytes from 192.168.1.1: icmp_seq=329 ttl=64 time=0.990 ms

64 bytes from 192.168.1.1: icmp_seq=330 ttl=64 time=3.417 ms

64 bytes from 192.168.1.1: icmp_seq=331 ttl=64 time=1.770 ms

64 bytes from 192.168.1.1: icmp_seq=332 ttl=64 time=1.594 ms

64 bytes from 192.168.1.1: icmp_seq=333 ttl=64 time=2.552 ms

64 bytes from 192.168.1.1: icmp_seq=334 ttl=64 time=5.076 ms

64 bytes from 192.168.1.1: icmp_seq=335 ttl=64 time=3.029 ms

64 bytes from 192.168.1.1: icmp_seq=336 ttl=64 time=1.433 ms

64 bytes from 192.168.1.1: icmp_seq=337 ttl=64 time=2.525 ms

64 bytes from 192.168.1.1: icmp_seq=338 ttl=64 time=0.891 ms

64 bytes from 192.168.1.1: icmp_seq=339 ttl=64 time=1.932 ms

64 bytes from 192.168.1.1: icmp_seq=340 ttl=64 time=2.414 ms

64 bytes from 192.168.1.1: icmp_seq=341 ttl=64 time=1.875 ms

64 bytes from 192.168.1.1: icmp_seq=342 ttl=64 time=1.698 ms

64 bytes from 192.168.1.1: icmp_seq=343 ttl=64 time=1.851 ms

64 bytes from 192.168.1.1: icmp_seq=344 ttl=64 time=2.201 ms

64 bytes from 192.168.1.1: icmp_seq=345 ttl=64 time=1.091 ms

64 bytes from 192.168.1.1: icmp_seq=346 ttl=64 time=2.569 ms

64 bytes from 192.168.1.1: icmp_seq=347 ttl=64 time=2.333 ms

64 bytes from 192.168.1.1: icmp_seq=348 ttl=64 time=2.353 ms

64 bytes from 192.168.1.1: icmp_seq=349 ttl=64 time=1.110 ms

64 bytes from 192.168.1.1: icmp_seq=350 ttl=64 time=3.515 ms

64 bytes from 192.168.1.1: icmp_seq=351 ttl=64 time=1.228 ms

64 bytes from 192.168.1.1: icmp_seq=352 ttl=64 time=2.427 ms

64 bytes from 192.168.1.1: icmp_seq=353 ttl=64 time=0.849 ms

64 bytes from 192.168.1.1: icmp_seq=354 ttl=64 time=8.336 ms

64 bytes from 192.168.1.1: icmp_seq=355 ttl=64 time=2.412 ms

64 bytes from 192.168.1.1: icmp_seq=356 ttl=64 time=1.968 ms

64 bytes from 192.168.1.1: icmp_seq=357 ttl=64 time=3.028 ms

64 bytes from 192.168.1.1: icmp_seq=358 ttl=64 time=5.026 ms

64 bytes from 192.168.1.1: icmp_seq=359 ttl=64 time=2.469 ms

64 bytes from 192.168.1.1: icmp_seq=360 ttl=64 time=0.893 ms

64 bytes from 192.168.1.1: icmp_seq=361 ttl=64 time=1.004 ms

64 bytes from 192.168.1.1: icmp_seq=362 ttl=64 time=2.009 ms

64 bytes from 192.168.1.1: icmp_seq=363 ttl=64 time=2.118 ms

64 bytes from 192.168.1.1: icmp_seq=364 ttl=64 time=1.792 ms

64 bytes from 192.168.1.1: icmp_seq=365 ttl=64 time=2.448 ms

64 bytes from 192.168.1.1: icmp_seq=366 ttl=64 time=1.304 ms

64 bytes from 192.168.1.1: icmp_seq=367 ttl=64 time=2.464 ms

64 bytes from 192.168.1.1: icmp_seq=368 ttl=64 time=2.226 ms

64 bytes from 192.168.1.1: icmp_seq=369 ttl=64 time=0.895 ms

64 bytes from 192.168.1.1: icmp_seq=370 ttl=64 time=1.450 ms

64 bytes from 192.168.1.1: icmp_seq=371 ttl=64 time=1.812 ms

64 bytes from 192.168.1.1: icmp_seq=372 ttl=64 time=0.794 ms

64 bytes from 192.168.1.1: icmp_seq=373 ttl=64 time=2.818 ms

64 bytes from 192.168.1.1: icmp_seq=374 ttl=64 time=2.766 ms

64 bytes from 192.168.1.1: icmp_seq=375 ttl=64 time=1.509 ms

64 bytes from 192.168.1.1: icmp_seq=376 ttl=64 time=1.167 ms

Apr 11, 2017 6:56 AM in response to Grant Bennet-Alder

Here's what I've got. I'm having the same issue.

aero.108

Level 1

25 points

Apr 6, 2017 2:51 AM in response to Grant Bennet-Alder

I have same issue with Tp-link archer C2600.

Horrible latencies, ping spikes even when I'm just in front of router,

tested with different routers, issue always same.

Apr 6, 2017 6:34 AM in response to aero.108

Post the information I asked about, and Readers may be able to tell more about what is happening to you and why.

kiles01

Level 1

14 points

Jun 13, 2017 12:26 PM in response to AndyH28

Hi,

I'm experiencing the same issue, but in my case the problem goes away while the bluetooth is off. Has anyone tried this?

Jul 7, 2017 1:56 PM in response to JRadek

@jradek:

Confirmed. I got exactly the same issues with SQL Lite. After disabling it is ok

Jul 16, 2017 8:35 AM in response to AndyH28

Apparently bluetooth & wireless 2.4ghz share the same spectrum. Swapping to 5ghz wireless mitigated the issue sufficiently for me, you might try the same thing if available.