Late 2013 Macbook Pro Retina 13'' Wifi Issues

You are right about the IP... 😉

This is what I get with the correct router IP address first time I started pinging.

ping -c 30 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=64.516 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=87.530 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=8.164 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=30.740 ms

64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=53.740 ms

64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=77.440 ms

64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=99.456 ms

64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=19.829 ms

64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=41.124 ms

64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=65.038 ms

64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=89.077 ms

64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=8.474 ms

64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1.703 ms

64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=54.688 ms

64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=77.093 ms

64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=100.112 ms

64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=0.949 ms

64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=44.718 ms

64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=66.943 ms

64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=89.735 ms

64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=9.556 ms

64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=32.082 ms

64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=53.762 ms

64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=77.477 ms

64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=100.529 ms

64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=20.883 ms

64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=44.564 ms

64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=66.592 ms

64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=89.287 ms

64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=9.601 ms

--- 192.168.0.1 ping statistics ---

30 packets transmitted, 30 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.949/52.847/100.529/31.981 ms

Strange thing is that after this ping series I continually get these (you can understand I am pinging my pants off right now):

ping -c 10 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.851 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.836 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.838 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.887 ms

64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.695 ms

64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.769 ms

64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.818 ms

64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=1.819 ms

64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.873 ms

64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=0.863 ms

--- 192.168.0.1 ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.769/1.125/2.695/0.600 ms

And at this moment I am doing nothing but pinging, so no internet, no downloads (no updates that I am aware of). So that looks reasonable, although there is some fluctuation.

But this is 5 minutes later

ping -c 10 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=18.720 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.890 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=64.764 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=87.223 ms

64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.857 ms

64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=30.356 ms

64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=53.137 ms

64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=76.255 ms

64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=99.090 ms

64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=19.414 ms

--- 192.168.0.1 ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 0.857/45.071/99.090/34.053 ms

I checked my download and uploadspeeds, but they are ok too.

I checked it on 2,4 GHz n.

Tomorrow I will test the connections at work where I will be moving a lot with my laptop.

At this moment I do not experience any severe influence of this latency.

I can play my speedchess games on a chess server (ICC) without any serious lag, internetbrowsing is ok, download speeds are fine. But I come from an awfully old and slow laptop, so my judgement is off ;-)

Sorry for flooding this post with ping times.

I wouldn't worry too much about the ping times if there are no other issues like packet drops, page load issues etc. I too have low pings but do not face any other problem unlike many others here. Test with other networks and if it is fine, keep it. The ping problem is a driver issue and will be fixed for sure by Apple.

Having similar issues on my 13" 8GB/256GB. The 5ghz band is not reliable at all. Moving files to my NAS is slow and generally causes the Mac to disconnect from the network. I also get the issues waking up from sleep. However, the 2.4ghz band appears to be fine. Files move to my NAS at about 9-11MB/s and speed is consistent. The connection hasn't dropped as far as I know.

For now I'm just using the 2.4ghz band. It's fast enough and actually works. Disappointed though as my desktop on 5ghz is able to push files to my NAS at 20-30MB/s. Since I do photo work on my Mac it would be useful to transfer files 2-3x faster.

UPDATE:

I am 0,5m away from a 802.11n AP here at my workplace. I started a FTP (server is in my LAN) transfer and enabled/disabled bluetooth while the download is going. Look at the drop down - the download speed drops immediately if I enable bluetooth and goes up after i disable it:

I have quite a strange issue as well regarding WiFi.

I used to work with a MacBook Pro Mid 2010 - two weeks ago I order a new one, MacBook Pro Retina 13.

I have a router from TP-Link, Dual Band, Archer C7.

After a few days I recognized that even surfing is very slow, using 5GHz, AC mode - first I had the suspicion of some problems of my ISP, but other devices had normal speed and access.

Next I tested 5 GHz AC Mode with my smartphone (LG G2) and got connection bandwidth of approx. 450 MBits.

With my MacBook Pro for the first seconds I approx get the same bandwidth and then it drops to 7 MBit (if I can trust the informaton from MacOS, using the WiFi Icon and ALT). I already tried the latest beta firmware for my router - no change... even if I am next to the router.

At the moment I am not really sure, if it is the router or the MacBook Pro - on the other hand - if am using n-mode or 2,4 GHz network I do not have any problems...

Here some before and after screenshots to clarify what I mean, it's the same location, with a duration of about 15 secs between the screenshots:

Any hint will be highly appreciated - my 5GHz network is the only one in the area... all others are 2,4GHz.

Best regards,

Michael

Guys, today I gave up on this issue and sent my Macbook Pro 13" Retina back. I wish all of you good luck on further investigation. I'm very disappointed, but I'm still hoping for you apple will fix that.

I will reuse my old Macbook pro.

I understand you.

I was contacted by Apple and agreed to to test a beta version of a future OS version, it's worth a try.

One thing i don't understand: If its a driver problem, why are so few people complaining here. I mean, Apple is selling tons of these machines. Is it really possible that people don't realize that something is wrong with the WiFi? I mean, on mine it was quite obvious?

Yep, I have the same problem on my Retina 13inch, December 2013 build.

Upgraded from a 2009 Macbook Pro.

Latency spikes go from sub 1ms-350ms and every step in between.

Setup is a state of the art Asus wireless AC router.

Both laptops are pinging my local router at the same time.

Macbook Pro Retina

Macbook Pro

I then bootcamp into Windows 8.1 from my Macbook 13 retina laptop and the latency spikes are gone (screenshot below). Basic assumption based on this evidence is that it is Mavericks OS software and/or driver related as implied by earlier posters.

For all those who are unsure about keeping or returning the device within 14days, please call up Apples Sales and explain the problems/difficulties. They just extended my return duration to 30days (also offered a small cashback for the "pain" I am going through). They are friendly 🙂

I am not sure if this policy applies worldwide, but I realized that you could bargain with Apple sales.

just connect it to the ethernet cable

are you advising everyone with Wifi problems to use Ethernet cable? 😮

I think the response was tongue in cheek as there is no ethernet port on the Macbook anymore 😉

I have also confirmed this morning that the latency and quality problems also apply to IPad Air and IPhone 5S hotspots when running OSX and connecting from my Macbook Retina.

If I bootcamp into to Windows 8.1, the connection problems and latency issues to the Apple devices dissapear. I am also seeing slow pickup of the hotspots in Mavericks whereas in Windows, the Hotspots are seen almost instantly.

So, the current 'workaround' for these problems is to use Windows 8.1 on the Macbook Retina rather than, OS X Mavericks.

Good job Apple.