Macbook Pro WiFi long ping time

Hello. I've got an issue that's come up on this discussion category before with the late 2016 MBP w/touchbar (model MBP 13,3): long WiFi pings. Another user posted a short/long oscillating ping time to his WiFi router. I'm having the same problem, and the previous thread was closed before a solution was reached.

Recap of the problem... You'll see 50 pings from my MBP to my Netgear Nighthawk R7000 router, followed by 50 from my iPhone 7.

Macbook Pro:

64 bytes from 192.168.11.1: icmp_seq=0 ttl=64 time=0.985 ms

64 bytes from 192.168.11.1: icmp_seq=1 ttl=64 time=183.609 ms

64 bytes from 192.168.11.1: icmp_seq=2 ttl=64 time=301.731 ms

64 bytes from 192.168.11.1: icmp_seq=3 ttl=64 time=764.977 ms

64 bytes from 192.168.11.1: icmp_seq=4 ttl=64 time=532.749 ms

64 bytes from 192.168.11.1: icmp_seq=5 ttl=64 time=423.662 ms

64 bytes from 192.168.11.1: icmp_seq=6 ttl=64 time=109.228 ms

64 bytes from 192.168.11.1: icmp_seq=7 ttl=64 time=647.522 ms

64 bytes from 192.168.11.1: icmp_seq=8 ttl=64 time=0.957 ms

64 bytes from 192.168.11.1: icmp_seq=9 ttl=64 time=1.473 ms

64 bytes from 192.168.11.1: icmp_seq=10 ttl=64 time=1.925 ms

64 bytes from 192.168.11.1: icmp_seq=11 ttl=64 time=2.346 ms

64 bytes from 192.168.11.1: icmp_seq=12 ttl=64 time=2.694 ms

64 bytes from 192.168.11.1: icmp_seq=13 ttl=64 time=2.498 ms

64 bytes from 192.168.11.1: icmp_seq=14 ttl=64 time=162.144 ms

64 bytes from 192.168.11.1: icmp_seq=15 ttl=64 time=291.535 ms

64 bytes from 192.168.11.1: icmp_seq=16 ttl=64 time=139.565 ms

64 bytes from 192.168.11.1: icmp_seq=17 ttl=64 time=114.130 ms

64 bytes from 192.168.11.1: icmp_seq=18 ttl=64 time=193.848 ms

64 bytes from 192.168.11.1: icmp_seq=19 ttl=64 time=356.472 ms

64 bytes from 192.168.11.1: icmp_seq=20 ttl=64 time=15.614 ms

64 bytes from 192.168.11.1: icmp_seq=21 ttl=64 time=377.467 ms

64 bytes from 192.168.11.1: icmp_seq=22 ttl=64 time=323.144 ms

64 bytes from 192.168.11.1: icmp_seq=23 ttl=64 time=11.042 ms

64 bytes from 192.168.11.1: icmp_seq=24 ttl=64 time=53.428 ms

64 bytes from 192.168.11.1: icmp_seq=25 ttl=64 time=90.603 ms

64 bytes from 192.168.11.1: icmp_seq=26 ttl=64 time=2.809 ms

64 bytes from 192.168.11.1: icmp_seq=27 ttl=64 time=2.028 ms

64 bytes from 192.168.11.1: icmp_seq=28 ttl=64 time=19.199 ms

64 bytes from 192.168.11.1: icmp_seq=29 ttl=64 time=2.303 ms

64 bytes from 192.168.11.1: icmp_seq=30 ttl=64 time=2.118 ms

64 bytes from 192.168.11.1: icmp_seq=31 ttl=64 time=142.155 ms

64 bytes from 192.168.11.1: icmp_seq=32 ttl=64 time=267.978 ms

64 bytes from 192.168.11.1: icmp_seq=33 ttl=64 time=730.390 ms

64 bytes from 192.168.11.1: icmp_seq=34 ttl=64 time=496.511 ms

64 bytes from 192.168.11.1: icmp_seq=35 ttl=64 time=377.961 ms

64 bytes from 192.168.11.1: icmp_seq=36 ttl=64 time=0.967 ms

64 bytes from 192.168.11.1: icmp_seq=37 ttl=64 time=397.723 ms

64 bytes from 192.168.11.1: icmp_seq=38 ttl=64 time=166.925 ms

64 bytes from 192.168.11.1: icmp_seq=39 ttl=64 time=1.047 ms

64 bytes from 192.168.11.1: icmp_seq=40 ttl=64 time=1.977 ms

64 bytes from 192.168.11.1: icmp_seq=41 ttl=64 time=2.157 ms

64 bytes from 192.168.11.1: icmp_seq=42 ttl=64 time=2.821 ms

64 bytes from 192.168.11.1: icmp_seq=43 ttl=64 time=1.022 ms

64 bytes from 192.168.11.1: icmp_seq=44 ttl=64 time=1.047 ms

64 bytes from 192.168.11.1: icmp_seq=45 ttl=64 time=107.489 ms

64 bytes from 192.168.11.1: icmp_seq=46 ttl=64 time=359.644 ms

64 bytes from 192.168.11.1: icmp_seq=47 ttl=64 time=128.508 ms

64 bytes from 192.168.11.1: icmp_seq=48 ttl=64 time=173.255 ms

64 bytes from 192.168.11.1: icmp_seq=49 ttl=64 time=354.999 ms

64 bytes from 192.168.11.1: icmp_seq=50 ttl=64 time=47.964 ms

You can see the back and forth. Some pings over 1/2 a second, some pings under 1 millisecond... really inconsistent performance... and you can see the fruits of that especially when I'm coping files on my LAN.

and now 50 pings from my iPhone 7, connected to the same WiFi router:

64 bytes from 192.168.11.1: icmp_seq=0 ttl=64 time=37.430 ms

64 bytes from 192.168.11.1: icmp_seq=1 ttl=64 time=11.955 ms

64 bytes from 192.168.11.1: icmp_seq=2 ttl=64 time=6.737 ms

64 bytes from 192.168.11.1: icmp_seq=3 ttl=64 time=8.101 ms

64 bytes from 192.168.11.1: icmp_seq=4 ttl=64 time=14.486 ms

64 bytes from 192.168.11.1: icmp_seq=5 ttl=64 time=13.315 ms

64 bytes from 192.168.11.1: icmp_seq=6 ttl=64 time=15.315 ms

64 bytes from 192.168.11.1: icmp_seq=7 ttl=64 time=14.153 ms

64 bytes from 192.168.11.1: icmp_seq=8 ttl=64 time=16.863 ms

64 bytes from 192.168.11.1: icmp_seq=9 ttl=64 time=16.113 ms

64 bytes from 192.168.11.1: icmp_seq=10 ttl=64 time=2.665 ms

64 bytes from 192.168.11.1: icmp_seq=11 ttl=64 time=13.714 ms

64 bytes from 192.168.11.1: icmp_seq=12 ttl=64 time=4.598 ms

64 bytes from 192.168.11.1: icmp_seq=13 ttl=64 time=7.731 ms

64 bytes from 192.168.11.1: icmp_seq=14 ttl=64 time=17.913 ms

64 bytes from 192.168.11.1: icmp_seq=15 ttl=64 time=16.114 ms

64 bytes from 192.168.11.1: icmp_seq=16 ttl=64 time=17.863 ms

64 bytes from 192.168.11.1: icmp_seq=17 ttl=64 time=16.181 ms

64 bytes from 192.168.11.1: icmp_seq=18 ttl=64 time=17.803 ms

64 bytes from 192.168.11.1: icmp_seq=19 ttl=64 time=17.603 ms

64 bytes from 192.168.11.1: icmp_seq=20 ttl=64 time=18.353 ms

64 bytes from 192.168.11.1: icmp_seq=21 ttl=64 time=4.654 ms

64 bytes from 192.168.11.1: icmp_seq=22 ttl=64 time=6.708 ms

64 bytes from 192.168.11.1: icmp_seq=23 ttl=64 time=18.336 ms

64 bytes from 192.168.11.1: icmp_seq=24 ttl=64 time=17.424 ms

64 bytes from 192.168.11.1: icmp_seq=25 ttl=64 time=7.046 ms

64 bytes from 192.168.11.1: icmp_seq=26 ttl=64 time=17.466 ms

64 bytes from 192.168.11.1: icmp_seq=27 ttl=64 time=7.403 ms

64 bytes from 192.168.11.1: icmp_seq=28 ttl=64 time=17.738 ms

64 bytes from 192.168.11.1: icmp_seq=29 ttl=64 time=6.952 ms

64 bytes from 192.168.11.1: icmp_seq=30 ttl=64 time=18.160 ms

64 bytes from 192.168.11.1: icmp_seq=31 ttl=64 time=19.429 ms

64 bytes from 192.168.11.1: icmp_seq=32 ttl=64 time=7.184 ms

64 bytes from 192.168.11.1: icmp_seq=33 ttl=64 time=4.413 ms

64 bytes from 192.168.11.1: icmp_seq=34 ttl=64 time=18.027 ms

64 bytes from 192.168.11.1: icmp_seq=35 ttl=64 time=19.121 ms

64 bytes from 192.168.11.1: icmp_seq=36 ttl=64 time=18.408 ms

64 bytes from 192.168.11.1: icmp_seq=37 ttl=64 time=19.173 ms

64 bytes from 192.168.11.1: icmp_seq=38 ttl=64 time=18.664 ms

64 bytes from 192.168.11.1: icmp_seq=39 ttl=64 time=19.574 ms

64 bytes from 192.168.11.1: icmp_seq=40 ttl=64 time=7.911 ms

64 bytes from 192.168.11.1: icmp_seq=41 ttl=64 time=7.958 ms

64 bytes from 192.168.11.1: icmp_seq=42 ttl=64 time=5.647 ms

64 bytes from 192.168.11.1: icmp_seq=43 ttl=64 time=8.011 ms

64 bytes from 192.168.11.1: icmp_seq=44 ttl=64 time=7.967 ms

64 bytes from 192.168.11.1: icmp_seq=45 ttl=64 time=7.963 ms

64 bytes from 192.168.11.1: icmp_seq=46 ttl=64 time=7.913 ms

64 bytes from 192.168.11.1: icmp_seq=47 ttl=64 time=7.980 ms

64 bytes from 192.168.11.1: icmp_seq=48 ttl=64 time=7.992 ms

64 bytes from 192.168.11.1: icmp_seq=49 ttl=64 time=7.961 ms

64 bytes from 192.168.11.1: icmp_seq=50 ttl=64 time=7.959 ms

As you can see, the performance of the MBP beats iPhone 7 at shortest ping time, but iPhone 7 *destroys* my MBP in terms of consistency. The previous post suggested that the user take his MBP to the Apple Store and ask that they physically open the machine to check if the antennas were broken, or their wires damaged or some other hardware issue.

I've also tested using a hardwire connection. Obviously, this solution offers the best performance, with pings almost always under 1 millisecond. So it's seems the problem is the WiFi on the MBP.

I'm thumping this problem again to see if anyone else has experienced it and solved it.

Thanks, y'all!

MacBook Pro TouchBar and Touch ID, macOS Sierra (10.12.6)

Posted on Feb 22, 2018 12:00 PM

Top-ranking reply

Ian Whitworth Author

Level 1

29 points

Posted on Feb 28, 2018 9:25 AM

Thanks, everyone, for their help here. I think I figured it out. Turns out to be a software issue.

The culprit was Avid Application Manager. This is a software update utility that Avid installs with any of its professional A/V packages: Media Composer, Pro Tools, etc. Turns out, it's a little network piggie.

The thing is a little purple icon in your menu bar. Run a ping to your router, then click on that purple icon and select "Quit". Watch your ping times plummet & your internet connection increase in speed by at least 50%.

Thanks, Avid. As usual, you (sort of) deliver on the high-level stuff, but serve up a steaming piece of garbage to run the simplest background task. It will one day be your undoing.

View in context

Similar questions

28 replies

Feb 25, 2018 8:45 PM in response to Grant Bennet-Alder

I don't see any smoking guns here...

EtreCheck version: 4.0.4 (4A150)

Report generated: 2018-02-25 20:39:30

Download EtreCheck from https://etrecheck.com

Runtime: 3:18

Performance: Good

Problem: Computer is too slow

Major Issues:

Anything that appears on this list needs immediate attention.

No Time Machine backup - Time Machine backup not found.

Gatekeeper disabled - Gatekeeper security protection is disabled. This computer is at risk of malware infection.

System Integrity Protection disabled - System Integrity Protection is disabled. This computer is at risk of malware infection.

Minor Issues:

These issues do not need immediate attention but they may indicate future problems.

Clean up - There are orphan files that could be removed.

Unsigned files - There is unsigned software installed. It appears to be legitimate but should be reviewed.

Hardware Information:

MacBook Pro (15-inch, 2016)

MacBook Pro Model: MacBookPro13,3

1 2.7 GHz Intel Core i7 (i7-6820HQ) CPU: 4-core

16 RAM Not upgradeable

BANK 0/DIMM0

8 GB LPDDR3 2133 ok

BANK 1/DIMM0

8 GB LPDDR3 2133 ok

Battery: Health = Normal - Cycle count = 69

Video Information:

Intel HD Graphics 530 - VRAM: 1536 MB

Color LCD 3360 x 2100

AMD Radeon Pro 455 - VRAM: 2048 MB

Drives:

disk0 - APPLE SSD SM0512L 500.28 GB (Solid State - TRIM: Yes)

Internal PCI-Express 8.0 GT/s x4 NVM Express

disk0s1 - EFI [EFI] 315 MB

disk0s2 [Core Storage Container] 420.05 GB

disk1 - Macintosh HD (Journaled HFS+) 419.70 GB

disk0s3 - Recovery HD [Recovery] 650 MB

disk0s4 - P******p (Journaled HFS+) 79.13 GB

Mounted Volumes:

disk0s4 - P******p 79.13 GB (11.53 GB free)

Journaled HFS+

Mount point: /Volumes/P******p

disk1 - Macintosh HD 419.70 GB (105.99 GB free)

Journaled HFS+

Mount point: /

Network:

Interface en7: USB 10/100/1000 LAN

Interface en9: USB 10/100/1000 LAN 2

Interface lpss-serial1: LPSS Serial Adapter (1)

Interface lpss-serial2: LPSS Serial Adapter (2)

Interface en6: iBridge

One IPv6 address

Interface en0: Wi-Fi

802.11 a/b/g/n/ac

One IPv4 address

Interface en8: iPhone

Interface en5: Bluetooth PAN

Interface bridge0: Thunderbolt Bridge

iCloud Quota: 1.04 GB available

System Software:

macOS Sierra 10.12.6 (16G1212)

Time since boot: About 14 days

System Load: 2.10 (1 min ago) 2.56 (5 min ago) 2.36 (15 min ago)

Security:

System	Status
Gatekeeper	Anywhere
System Integrity Protection	disabled

Unsigned Files:

Launchd: ~/Library/LaunchAgents/com.valvesoftware.steamclean.plist

Executable: ~/Library/Application Support/Steam/SteamApps/steamclean

Details: Exact match found in the whitelist - probably OK

Launchd: ~/Library/LaunchAgents/org.virtualbox.vboxwebsrv.plist

Executable: /Applications/VirtualBox.app/Contents/MacOS/vboxwebsrv

Details: Exact match found in the whitelist - probably OK

Launchd: /Library/LaunchDaemons/org.virtualbox.startup.plist

Executable: /Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart

Details: Exact match found in the whitelist - probably OK

Kernel Extensions:

/Applications/InsomniaX.app

[Not Loaded] Insomnia_r11.kext (2.1.7 - SDK 10.9)

/Applications/Tunnelblick.app

[Not Loaded] tap.kext (20141104 (Tunnelblick build 4921))

[Not Loaded] tun.kext (20141104 (Tunnelblick build 4921))

/Library/Application Support/VirtualBox

[Loaded] VBoxDrv.kext (5.1.26)

[Loaded] VBoxNetAdp.kext (5.1.26)

[Loaded] VBoxNetFlt.kext (5.1.26)

[Loaded] VBoxUSB.kext (5.1.26)

/Library/Application Support/org.pqrs/Karabiner-VirtualHIDDevice/Extensions

[Loaded] org.pqrs.driver.Karabiner.VirtualHIDDevice.v041100.kext (4.11.0 - SDK 10.13)

/Library/Extensions

[Loaded] EnergyDriver.kext (2.0 - SDK 10.12)

[Not Loaded] RDUSB0009Dev.kext (1.0.0 - SDK 10.9)

/System/Library/Extensions

[Not Loaded] EyeTVAfaTechHidBlock.kext (1.1)

[Not Loaded] EyeTVCinergy450AudioBlock.kext (1.1)

[Not Loaded] EyeTVCinergyXSAudioBlock.kext (1.1)

[Not Loaded] EyeTVEmpiaAudioBlock.kext (1.1)

[Not Loaded] EyeTVVoyagerAudioBlock.kext (1.1)

System Launch Agents:

[Not Loaded]	8 Apple tasks
[Loaded]	159 Apple tasks
[Running]	118 Apple tasks

System Launch Daemons:

[Not Loaded]	39 Apple tasks
[Loaded]	151 Apple tasks
[Running]	127 Apple tasks
[Other]	2 Apple tasks

Launch Agents:

[Not Loaded]	org.pqrs.karabiner.karabiner_console_user_server.plist (Fumihiko Takayama - installed 2017-12-29)
[Not Loaded]	com.realvnc.vncserver.prelogin.plist (RealVNC Limited - installed 2017-08-03)
[Running]	com.realvnc.vncserver.peruser.plist (RealVNC Limited - installed 2017-08-03)
[Loaded]	org.macosforge.xquartz.startx.plist (Apple Inc. - XQuartz - installed 2016-10-26)
[Loaded]	com.google.keystone.agent.plist (Google, Inc. - installed 2017-10-17)
[Running]	com.avid.ApplicationManager.plist (Avid Technology Inc - installed 2017-09-25)

Launch Daemons:

[Running]	com.realvnc.vncserver.plist (RealVNC Limited - installed 2017-08-03)
[Loaded]	com.avid.bsd.shoetoolv120.plist (Avid Technology Inc - installed 2017-08-29)
[Loaded]	com.bombich.ccchelper.plist (Bombich Software, Inc. - installed 2017-11-17)
[Not Loaded]	org.virtualbox.startup.plist (? 700b9385 - installed 2017-08-23)
[Running]	com.paceap.eden.licensed.plist (PACE Anti-Piracy, Inc. - installed 2017-06-09)
[Loaded]	com.avid.bsd.shoe.plist (Avid Technology Inc - installed 2017-08-30)
[Loaded]	com.adobe.fpsaud.plist (Adobe Systems, Inc. - installed 2017-12-14)
[Loaded]	org.macosforge.xquartz.privileged_startx.plist (Apple Inc. - XQuartz - installed 2016-10-26)
[Running]	com.avid.transport.client.plist (Avid Technology Inc - installed 2017-05-23)
[Running]	org.pqrs.karabiner.karabiner_grabber.plist (Fumihiko Takayama - installed 2017-12-29)
[Running]	com.avid.hub.service.plist (Avid Technology Inc - installed 2017-05-23)
[Loaded]	com.google.keystone.daemon.plist (Google, Inc. - installed 2017-10-17)
[Loaded]	com.renewedvision.InstallHelper.plist (Renewed Vision LLC - installed 2017-12-17)
[Loaded]	com.feingeist.shimo.helper.plist (Fabian Jaeger - installed 2017-09-30)
[Loaded]	com.rogueamoeba.instanton-agent.plist (Rogue Amoeba Software, LLC - installed 2017-08-14)
[Loaded]	net.tunnelblick.tunnelblick.tunnelblickd.plist (Jonathan Bullard - installed 2017-12-08)

User Launch Agents:

[Loaded]	com.dropbox.DropboxMacUpdate.agent.plist (Dropbox, Inc. - installed 2017-09-14)
[Loaded]	com.valvesoftware.steamclean.plist (? 0 - installed 2017-12-20)
[Not Loaded]	org.virtualbox.vboxwebsrv.plist (? 0 - installed 2017-07-27)
[Loaded]	com.skype.skype.shareagent.plist (? 0 - installed )
[Loaded]	net.tunnelblick.tunnelblick.LaunchAtLogin.plist (Jonathan Bullard - installed 2017-12-07)

User Login Items:

iTunesHelper Application (Apple, Inc. - installed 2018-01-25)

(/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)

Dropbox Application (Dropbox, Inc.

(/Applications/Dropbox.app)

Karabiner-Elements Application (Fumihiko Takayama

(/Applications/Karabiner-Elements.app)

Jumpcut Application

(/Applications/Jumpcut.app)

EyeTV Helper Application (SHENZHEN GENIATECH INC.,LTD

(/Library/Application Support/EyeTV/EyeTV Helper.app)

Internet Plug-ins:

googletalkbrowserplugin: 5.41.3.0 (installed 2015-12-11)

FlashPlayer-10.6: 28.0.0.137 (installed 2018-01-23)

QuickTime Plugin: 7.7.3 (installed 2018-01-31)

Flash Player: 28.0.0.137 (installed 2018-01-23)

o1dbrowserplugin: 5.41.3.0 (installed 2017-10-18)

User Internet Plug-ins:

Aspera Web 3.7.4.147728: 3.7.4 (installed 2017-09-05)

WebEx64: 1.1.0 (installed 2018-01-24)

3rd Party Preference Panes:

Flash Player (installed 2017-12-14)

Time Machine:

Time Machine Not Configured!

Top Processes by CPU:

Process (count)	Source	% of CPU
QtWebEngineProcess (5)	Avid Technology Inc	24
WindowServer	Apple	8
kernel_task	Apple	6
Google Chrome Helper (17)	Google, Inc.	6
mds	Apple	5

Top Processes by Memory:

Process (count)	Source	RAM usage
kernel_task	Apple	1.58 GB
Google Chrome Helper (17)	Google, Inc.	1.34 GB
QtWebEngineProcess (5)	Avid Technology Inc	356 MB
mdworker (10)	Apple	301 MB
Google Chrome	Google, Inc.	296 MB

Top Processes by Network Use:

Process	Source	Input	Output
mDNSResponder	Apple	8 MB	3 MB
biometrickitd	Apple	6 MB	594 KB
Dropbox	Dropbox, Inc.	2 MB	2 MB
netbiosd	Apple	613 KB	215 KB
apsd	Apple	74 KB	68 KB

Top Processes by Energy Use:

Process (count)	Source	Energy usage (0-100)
QtWebEngineProcess (5)	Avid Technology Inc	15
WindowServer	Apple	3
Google Chrome Helper (17)	Google, Inc.	3
Google Chrome	Google, Inc.	1
airportd	Apple	1

Virtual Memory Information:

Available RAM	7.62 GB
Free RAM	4.82 GB
Used RAM	8.38 GB
Cached files	2.80 GB
Swap Used	1.17 GB

Clean up:

~/Library/LaunchAgents/com.skype.skype.shareagent.plist

/Applications/Skype.app/Contents/Library/LaunchServices/com.skype.skype.shareage nt.bundle/Contents/MacOS/com.skype.skype.shareagent

Executable not found

Diagnostics Information (past 7 days):

2018-02-23 02:32:13 fud Crash

objc_msgSend selector name: respondsToSelector:

End of report

Feb 22, 2018 4:26 PM in response to Grant Bennet-Alder

Here's a screen cap I took earlier today. Lots of other networks, but it doesn't explain why my iPhone performs so much better...

My router has recommended a higher channel, but I've tried all the options for channels with the nearly the same result.

EDITS: This channel (44) has provided the highest throughput (1053 Mbps). The other channels all negotiated connections less than 1000 Mbps. Additionally, I know my iPhone is connected using a 5 Ghz network, because the SSID they're both connected to only broadcasts 5 Ghz and not 2.4. Distance from router at test is less than 10 feet but through a single sheet of drywall.

Thanks for your quick engagement.

Feb 28, 2018 10:21 AM in response to Ian Whitworth

this guy, from your etrecheck report?

Launch Agents:

[...]

[Running] com.avid.ApplicationManager.plist (Avid Technology Inc - installed 2017-09-25)

Feb 23, 2018 1:17 PM in response to Grant Bennet-Alder

I think you're missing the most important piece of info: my iPhone doesn't have this problem on this network. I just checked, and my wife's MBP (albeit from 2011) doesn't have the same problem. Neither does my daughter's Chromebook.

I'm forced to conclude this is some sort of localized issue with my specific MBP... Agree?

DeltaHF

Level 1

14 points

Feb 24, 2018 11:27 AM in response to Ian Whitworth

I have EXACTLY the same issue with my late 15-inch 2017 MacBook Pro w/TouchBar. I'm a networking geek and I keep an eye on these sorts of things, and I definitely wasn't having these problems a few weeks ago... I am starting to get suspicious of 10.13.3.

I have performed tests in different rooms, with three different routers from different brands, all with the same results. I have tried different channels and different frequencies (2.4 & 5Ghz) and performed tests at different times of day. It looks like at least one other user in these forums is reporting a similar problem as well.

Just like you, my iPhone X has a consistent ping to my router of around 10ms (1 ft. away from my MacBook). Here's what things look like from my MacBook, sitting across the room (about 10 ft.) from my Linksys WRT3200ACM, with no obstructions between them...

Something is up...

64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=153.414 ms

64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=230.823 ms

64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=22.406 ms

64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=1.919 ms

64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=3.949 ms

64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=2.287 ms

64 bytes from 10.0.0.1: icmp_seq=6 ttl=64 time=3.067 ms

64 bytes from 10.0.0.1: icmp_seq=7 ttl=64 time=2.313 ms

64 bytes from 10.0.0.1: icmp_seq=8 ttl=64 time=1.986 ms

64 bytes from 10.0.0.1: icmp_seq=9 ttl=64 time=8.105 ms

64 bytes from 10.0.0.1: icmp_seq=10 ttl=64 time=5.985 ms

64 bytes from 10.0.0.1: icmp_seq=11 ttl=64 time=15.179 ms

64 bytes from 10.0.0.1: icmp_seq=12 ttl=64 time=59.619 ms

64 bytes from 10.0.0.1: icmp_seq=13 ttl=64 time=1.989 ms

64 bytes from 10.0.0.1: icmp_seq=14 ttl=64 time=2.093 ms

64 bytes from 10.0.0.1: icmp_seq=15 ttl=64 time=49.055 ms

64 bytes from 10.0.0.1: icmp_seq=16 ttl=64 time=39.062 ms

64 bytes from 10.0.0.1: icmp_seq=17 ttl=64 time=190.554 ms

64 bytes from 10.0.0.1: icmp_seq=18 ttl=64 time=130.238 ms

64 bytes from 10.0.0.1: icmp_seq=19 ttl=64 time=176.424 ms

64 bytes from 10.0.0.1: icmp_seq=20 ttl=64 time=169.710 ms

64 bytes from 10.0.0.1: icmp_seq=21 ttl=64 time=218.879 ms

64 bytes from 10.0.0.1: icmp_seq=22 ttl=64 time=131.110 ms

64 bytes from 10.0.0.1: icmp_seq=23 ttl=64 time=175.909 ms

64 bytes from 10.0.0.1: icmp_seq=24 ttl=64 time=219.552 ms

64 bytes from 10.0.0.1: icmp_seq=25 ttl=64 time=1.973 ms

64 bytes from 10.0.0.1: icmp_seq=26 ttl=64 time=2.797 ms

64 bytes from 10.0.0.1: icmp_seq=27 ttl=64 time=2.480 ms

64 bytes from 10.0.0.1: icmp_seq=28 ttl=64 time=2.623 ms

64 bytes from 10.0.0.1: icmp_seq=29 ttl=64 time=2.341 ms

64 bytes from 10.0.0.1: icmp_seq=30 ttl=64 time=2.821 ms

64 bytes from 10.0.0.1: icmp_seq=31 ttl=64 time=2.051 ms

64 bytes from 10.0.0.1: icmp_seq=32 ttl=64 time=2.868 ms

64 bytes from 10.0.0.1: icmp_seq=33 ttl=64 time=26.123 ms

64 bytes from 10.0.0.1: icmp_seq=34 ttl=64 time=24.872 ms

64 bytes from 10.0.0.1: icmp_seq=35 ttl=64 time=71.140 ms

64 bytes from 10.0.0.1: icmp_seq=36 ttl=64 time=2.296 ms

64 bytes from 10.0.0.1: icmp_seq=37 ttl=64 time=1.898 ms

64 bytes from 10.0.0.1: icmp_seq=38 ttl=64 time=1.916 ms

64 bytes from 10.0.0.1: icmp_seq=39 ttl=64 time=2.200 ms

64 bytes from 10.0.0.1: icmp_seq=40 ttl=64 time=25.774 ms

64 bytes from 10.0.0.1: icmp_seq=41 ttl=64 time=2.070 ms

64 bytes from 10.0.0.1: icmp_seq=42 ttl=64 time=4.313 ms

64 bytes from 10.0.0.1: icmp_seq=43 ttl=64 time=51.017 ms

64 bytes from 10.0.0.1: icmp_seq=44 ttl=64 time=101.293 ms

64 bytes from 10.0.0.1: icmp_seq=45 ttl=64 time=149.462 ms

64 bytes from 10.0.0.1: icmp_seq=46 ttl=64 time=222.465 ms

64 bytes from 10.0.0.1: icmp_seq=47 ttl=64 time=13.037 ms

64 bytes from 10.0.0.1: icmp_seq=48 ttl=64 time=1.937 ms

64 bytes from 10.0.0.1: icmp_seq=49 ttl=64 time=2.135 ms

64 bytes from 10.0.0.1: icmp_seq=50 ttl=64 time=14.311 ms

DeltaHF

Level 1

14 points

Feb 23, 2018 8:01 PM in response to Grant Bennet-Alder

The spectrum is clear. Here's Wi-Fi Explorer. As you can see, my "Faster" network spread is well clear of all the others in the 5Ghz band:

That did nothing to help my latency:

PING 10.0.0.1 (10.0.0.1): 56 data bytes

64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=146.846 ms

64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=3.401 ms

64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=566.452 ms

64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=2.256 ms

64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=6.883 ms

64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=51.089 ms

64 bytes from 10.0.0.1: icmp_seq=6 ttl=64 time=2.329 ms

64 bytes from 10.0.0.1: icmp_seq=7 ttl=64 time=3.527 ms

64 bytes from 10.0.0.1: icmp_seq=8 ttl=64 time=2.995 ms

64 bytes from 10.0.0.1: icmp_seq=9 ttl=64 time=2.188 ms

64 bytes from 10.0.0.1: icmp_seq=10 ttl=64 time=138.442 ms

64 bytes from 10.0.0.1: icmp_seq=11 ttl=64 time=54.515 ms

64 bytes from 10.0.0.1: icmp_seq=12 ttl=64 time=162.044 ms

64 bytes from 10.0.0.1: icmp_seq=13 ttl=64 time=150.850 ms

64 bytes from 10.0.0.1: icmp_seq=14 ttl=64 time=198.049 ms

64 bytes from 10.0.0.1: icmp_seq=15 ttl=64 time=240.640 ms

64 bytes from 10.0.0.1: icmp_seq=16 ttl=64 time=289.025 ms

64 bytes from 10.0.0.1: icmp_seq=17 ttl=64 time=231.027 ms

64 bytes from 10.0.0.1: icmp_seq=18 ttl=64 time=21.792 ms

64 bytes from 10.0.0.1: icmp_seq=19 ttl=64 time=2.062 ms

64 bytes from 10.0.0.1: icmp_seq=20 ttl=64 time=3.117 ms

64 bytes from 10.0.0.1: icmp_seq=21 ttl=64 time=1.881 ms

64 bytes from 10.0.0.1: icmp_seq=22 ttl=64 time=2.122 ms

64 bytes from 10.0.0.1: icmp_seq=23 ttl=64 time=1.997 ms

64 bytes from 10.0.0.1: icmp_seq=24 ttl=64 time=61.443 ms

64 bytes from 10.0.0.1: icmp_seq=25 ttl=64 time=248.052 ms

64 bytes from 10.0.0.1: icmp_seq=26 ttl=64 time=343.722 ms

64 bytes from 10.0.0.1: icmp_seq=27 ttl=64 time=142.273 ms

64 bytes from 10.0.0.1: icmp_seq=28 ttl=64 time=191.563 ms

64 bytes from 10.0.0.1: icmp_seq=29 ttl=64 time=2.038 ms

64 bytes from 10.0.0.1: icmp_seq=30 ttl=64 time=3.093 ms

64 bytes from 10.0.0.1: icmp_seq=31 ttl=64 time=2.017 ms

64 bytes from 10.0.0.1: icmp_seq=32 ttl=64 time=2.246 ms

64 bytes from 10.0.0.1: icmp_seq=33 ttl=64 time=2.094 ms

64 bytes from 10.0.0.1: icmp_seq=34 ttl=64 time=2.319 ms

64 bytes from 10.0.0.1: icmp_seq=35 ttl=64 time=23.132 ms

64 bytes from 10.0.0.1: icmp_seq=36 ttl=64 time=36.311 ms

64 bytes from 10.0.0.1: icmp_seq=37 ttl=64 time=198.694 ms

64 bytes from 10.0.0.1: icmp_seq=38 ttl=64 time=175.203 ms

64 bytes from 10.0.0.1: icmp_seq=39 ttl=64 time=306.300 ms

64 bytes from 10.0.0.1: icmp_seq=40 ttl=64 time=353.589 ms

64 bytes from 10.0.0.1: icmp_seq=41 ttl=64 time=402.543 ms

64 bytes from 10.0.0.1: icmp_seq=42 ttl=64 time=449.449 ms

64 bytes from 10.0.0.1: icmp_seq=43 ttl=64 time=5.465 ms

64 bytes from 10.0.0.1: icmp_seq=44 ttl=64 time=11.894 ms

64 bytes from 10.0.0.1: icmp_seq=45 ttl=64 time=16.097 ms

64 bytes from 10.0.0.1: icmp_seq=46 ttl=64 time=2.034 ms

64 bytes from 10.0.0.1: icmp_seq=47 ttl=64 time=1.911 ms

64 bytes from 10.0.0.1: icmp_seq=48 ttl=64 time=24.571 ms

64 bytes from 10.0.0.1: icmp_seq=49 ttl=64 time=2.157 ms

64 bytes from 10.0.0.1: icmp_seq=50 ttl=64 time=213.233 ms

The ICMP packets from both devices are the same size. I'm using Net Analyzer on my iPhone X with a default payload size of 56 bytes, the same default used with MacOS's ping tool. Here's what it shows in a test taken just seconds after the one I pasted above, with the iPhone sitting 8 inches away from the MacBook at my desk:

I should note, once again, that everything was working very well until the last few weeks. This has nothing to do with the MacBook or iPhone antennas. Something is up.

DeltaHF

Level 1

14 points

Feb 24, 2018 1:49 PM in response to Grant Bennet-Alder

My network is called "Faster". I manually set my router to use Ch. 112 for testing; it made no difference with the intermittent latency. As I said in my original post, I've tried many different channels, but nothing helps.

I am not suggesting there is a hardware or antenna problem, I am suspicious of a software/driver problem with the recent MacOS update.

I'm not going to run etrecheck. This is a top-of-the-line, three-month-old MacBook Pro which has worked wonderfully in this location, with this router, since I got it. CPU usage stays between 0.8% and 2.5%, there's plenty of free memory, no network usage during these tests, and the problem persists between multiple restarts.

DeltaHF

Level 1

14 points

Feb 26, 2018 1:25 PM in response to Ian Whitworth

Have you tried connecting to different routers, Ian?

As I mentioned in my own post on the issue, I'm having the same results with four different routers and access points. I even connected to my own iPhone X's WiFi hotspot and tried pinging the iPhone's local address... the problem still existed.

I will be visiting a local university tomorrow; I'm going to take my MacBook and will see if it plays nicely with their WiFi network...

DeltaHF

Level 1

14 points

Feb 26, 2018 7:27 PM in response to Ian Whitworth

Please share your experience at the Apple Store. It looks like I'm going to have to try that as well.

I visited a local university today and was in a brand-new building on campus with a strong, modern wifi network. Pinging their router saw the same inconsistent behavior, and it even dropped a packet. My iPhone X was, as usual, much more stable.

64 bytes from 10.46.0.1: icmp_seq=0 ttl=255 time=2.218 ms

64 bytes from 10.46.0.1: icmp_seq=1 ttl=255 time=2.285 ms

64 bytes from 10.46.0.1: icmp_seq=2 ttl=255 time=2.271 ms

64 bytes from 10.46.0.1: icmp_seq=3 ttl=255 time=11.591 ms

64 bytes from 10.46.0.1: icmp_seq=4 ttl=255 time=57.292 ms

64 bytes from 10.46.0.1: icmp_seq=5 ttl=255 time=22.803 ms

64 bytes from 10.46.0.1: icmp_seq=6 ttl=255 time=1.780 ms

64 bytes from 10.46.0.1: icmp_seq=7 ttl=255 time=20.809 ms

64 bytes from 10.46.0.1: icmp_seq=8 ttl=255 time=1.395 ms

64 bytes from 10.46.0.1: icmp_seq=9 ttl=255 time=42.321 ms

64 bytes from 10.46.0.1: icmp_seq=10 ttl=255 time=3.065 ms

64 bytes from 10.46.0.1: icmp_seq=11 ttl=255 time=1.400 ms

64 bytes from 10.46.0.1: icmp_seq=12 ttl=255 time=8.027 ms

64 bytes from 10.46.0.1: icmp_seq=13 ttl=255 time=6.494 ms

64 bytes from 10.46.0.1: icmp_seq=14 ttl=255 time=1.439 ms

64 bytes from 10.46.0.1: icmp_seq=15 ttl=255 time=19.494 ms

64 bytes from 10.46.0.1: icmp_seq=16 ttl=255 time=1.920 ms

64 bytes from 10.46.0.1: icmp_seq=17 ttl=255 time=40.870 ms

64 bytes from 10.46.0.1: icmp_seq=18 ttl=255 time=107.016 ms

64 bytes from 10.46.0.1: icmp_seq=19 ttl=255 time=1.366 ms

64 bytes from 10.46.0.1: icmp_seq=20 ttl=255 time=6.652 ms

64 bytes from 10.46.0.1: icmp_seq=21 ttl=255 time=3.910 ms

64 bytes from 10.46.0.1: icmp_seq=22 ttl=255 time=4.808 ms

64 bytes from 10.46.0.1: icmp_seq=23 ttl=255 time=2.573 ms

64 bytes from 10.46.0.1: icmp_seq=24 ttl=255 time=1.474 ms

64 bytes from 10.46.0.1: icmp_seq=25 ttl=255 time=1.852 ms

64 bytes from 10.46.0.1: icmp_seq=26 ttl=255 time=1.382 ms

64 bytes from 10.46.0.1: icmp_seq=27 ttl=255 time=1.790 ms

64 bytes from 10.46.0.1: icmp_seq=28 ttl=255 time=1.638 ms

64 bytes from 10.46.0.1: icmp_seq=29 ttl=255 time=14.273 ms

64 bytes from 10.46.0.1: icmp_seq=30 ttl=255 time=1.578 ms

64 bytes from 10.46.0.1: icmp_seq=31 ttl=255 time=9.739 ms

64 bytes from 10.46.0.1: icmp_seq=32 ttl=255 time=31.021 ms

64 bytes from 10.46.0.1: icmp_seq=33 ttl=255 time=3.745 ms

64 bytes from 10.46.0.1: icmp_seq=34 ttl=255 time=2.809 ms

64 bytes from 10.46.0.1: icmp_seq=35 ttl=255 time=2.922 ms

64 bytes from 10.46.0.1: icmp_seq=36 ttl=255 time=1.759 ms

64 bytes from 10.46.0.1: icmp_seq=37 ttl=255 time=2.300 ms

64 bytes from 10.46.0.1: icmp_seq=38 ttl=255 time=1.912 ms

64 bytes from 10.46.0.1: icmp_seq=39 ttl=255 time=45.644 ms

64 bytes from 10.46.0.1: icmp_seq=40 ttl=255 time=92.520 ms

Request timeout for icmp_seq 41

64 bytes from 10.46.0.1: icmp_seq=42 ttl=255 time=1.228 ms

64 bytes from 10.46.0.1: icmp_seq=43 ttl=255 time=2.440 ms

64 bytes from 10.46.0.1: icmp_seq=44 ttl=255 time=1.882 ms

64 bytes from 10.46.0.1: icmp_seq=45 ttl=255 time=1.841 ms

64 bytes from 10.46.0.1: icmp_seq=46 ttl=255 time=1.658 ms

64 bytes from 10.46.0.1: icmp_seq=47 ttl=255 time=11.251 ms

64 bytes from 10.46.0.1: icmp_seq=48 ttl=255 time=1.299 ms

64 bytes from 10.46.0.1: icmp_seq=49 ttl=255 time=1.397 ms

64 bytes from 10.46.0.1: icmp_seq=50 ttl=255 time=21.670 ms

Feb 28, 2018 8:58 AM in response to agranados

That's a good question... but no. I do have a few menu tricks, but none of them have to do with networking. Closest thing is VNC Server, but I'm assuming that remains dormant until it's asked for a connection.

I've tried to run my ping tests as clean as possible - even made a new user & tried safe mode. I'd actually be interested in whether or not I can run them from single-user mode. I don't know how to cast the right bash spells to cast to fire up the WiFi under single-user.

Feb 24, 2018 8:23 AM in response to Grant Bennet-Alder

sorry - I have messed up which network we are studying and whose pictures are whose. So some of my comments above make no sense.

Feb 22, 2018 6:46 PM in response to Grant Bennet-Alder

if you want that and also want to look at the spectrum, WiFi Explorer is cheap and has a three day free trial in the Mac App store:

drag and drop on Preview, then stretch and scroll the window for larger.

See how, in this example, G7HS7_15 in orange, spreads up and down the spectrum, overlapping MANY other networks.

Feb 24, 2018 7:36 AM in response to DeltaHF

Something is up.

your neighbors are busily moving their Routers to different channels, to get better reception. The network named Faster (80 MHz wide) is now down at 112 instead of up in the 160's.

Where is the one with the hidden-name network?

what it TWCWiFiPasspoint? it has a similar, but not identical numbers to others, which I presume are yours.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Macbook Pro WiFi long ping time

[...]
[Running]	com.avid.ApplicationManager.plist (Avid Technology Inc - installed 2017-09-25)