Q: Late 2013 Macbook Pro Retina 13'' Wifi Issues

since some posters are claiming that a replament will not fix the wifi-sisue I decided to send one more confirmation that in  my case it did solve the issue.

So my guess is that people with a replacement with the same wifi issues must again have received one from the faultty batch.....

good luck

I get the feeling some people definetly have/had hardware problems, but others experience software/driver issues. My MBP does just fine on 11n at the University, but behaves badly on 11n at home while my other devices are just fine on the home network. When I switch to 11g, everything is fine, apart from the lower speeds that is... I think it's most likely my issues are software related - the MBP communicates fine with some routers, but bably with others.

I think you're right.  It seems like there is definitely a software issue causing latency across the board with the latest driver.  That's easy to prove.  Rolling back to an older drive eliminates the latency, but causes drops.  I saw on mine. 

I did experience a couple of times where wifi would become unresponsive, or some things worked - some things didn't after waking up.  That's probably software. 

As for the hard drops and very sluggish response, that's probably hardware related, of which, some replacements have worked if you're lucky enough to get one from a "good" batch. 

I ended up returning mine and will stick with my 2011 MBP for now.  I do believe I had a good hardware set, but until it's all resolved I cannot live with that ping latency.  Being in network management, I need accuracy and unfortunately, the machine wasn't cutting it. 

I'm sure it will be resolved soon and i cannot wait to get my new one!

New chipset; new OS; bugs and probably some hardware issues.  They'll no doubt resolve it on these flagship devices.  Just annoying that we have to wait. 

WINDOWS

C:\Windows\system32>ping 192.168.1.1 -n 10

Esecuzione di Ping 192.168.1.1 con 32 byte di dati:
Risposta da 192.168.1.1: byte=32 durata=1ms TTL=64
Risposta da 192.168.1.1: byte=32 durata=1ms TTL=64
Risposta da 192.168.1.1: byte=32 durata=1ms TTL=64
Risposta da 192.168.1.1: byte=32 durata=1ms TTL=64
Risposta da 192.168.1.1: byte=32 durata=2ms TTL=64
Risposta da 192.168.1.1: byte=32 durata=2ms TTL=64
Risposta da 192.168.1.1: byte=32 durata=2ms TTL=64
Risposta da 192.168.1.1: byte=32 durata=2ms TTL=64
Risposta da 192.168.1.1: byte=32 durata=1ms TTL=64
Risposta da 192.168.1.1: byte=32 durata=1ms TTL=64

Statistiche Ping per 192.168.1.1:
    Pacchetti: Trasmessi = 10, Ricevuti = 10,
    Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
    Minimo = 1ms, Massimo =  2ms, Medio =  1ms

I THINK THAT THE PROBLEM IS SOFTWARE

*Macbook Retina 15" Basic

Please read the whole Thread, Windows Users have the same Issue. Maybe the issue shows combined with a specific wifi setup only, I don't know.

My New Macbook Pro Retina 13":

C:\>ping 192.168.3.1 -t

Pinging 192.168.3.1 with 32 bytes of data:
Reply from 192.168.3.1: bytes=32 time=9ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=6ms TTL=64
Reply from 192.168.3.1: bytes=32 time=3ms TTL=64
Reply from 192.168.3.1: bytes=32 time=10ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=6ms TTL=64
Reply from 192.168.3.1: bytes=32 time=38ms TTL=64
Reply from 192.168.3.1: bytes=32 time=116ms TTL=64
Reply from 192.168.3.1: bytes=32 time=54ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=4ms TTL=64
Reply from 192.168.3.1: bytes=32 time=33ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=7ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64

Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=16ms TTL=64
Reply from 192.168.3.1: bytes=32 time=88ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=3ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=131ms TTL=64
Reply from 192.168.3.1: bytes=32 time=69ms TTL=64
Reply from 192.168.3.1: bytes=32 time=7ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=47ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=3ms TTL=64
Reply from 192.168.3.1: bytes=32 time=135ms TTL=64
Reply from 192.168.3.1: bytes=32 time=69ms TTL=64
Reply from 192.168.3.1: bytes=32 time=8ms TTL=64

My old Macbook Pro:

Pinging 192.168.3.1 with 32 bytes of data:
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=7ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=3ms TTL=64
Reply from 192.168.3.1: bytes=32 time=7ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=3ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=4ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=4ms TTL=64
Reply from 192.168.3.1: bytes=32 time=4ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=5ms TTL=64
Reply from 192.168.3.1: bytes=32 time=2ms TTL=64
Reply from 192.168.3.1: bytes=32 time=1ms TTL=64
Reply from 192.168.3.1: bytes=32 time=7ms TTL=64
Reply from 192.168.3.1: bytes=32 time=7ms TTL=64

A driver is a software too...

I didn't doubt that.

Let me put my reasons why I feel it needn't necessarily be a hardware issue (by this I mean problems with pings and wifi connectivity after sleep)

1. The driver mostly abstracts the hardware and for such issues which are always reproducible, I would suspect the driver or software on top of it
2. The problem appearing on Windows doesnt necessarily mean a hardware issue, but a windows driver issue (again delivered by Apple)
3. There are reports where older an old wifi driver has corrected the ping problem (but did create other problems)
4. If it was a hardware issue, it would have been more widespread, and it would have probably appeared during reviews/tests.
5. The first Wifi AC driver was extremely buggy which delivered half the AC speed and Apple did fix this later with an update.

I still am not supporting the bad quality delivered by Apple. It is definitely not acceptable. I face the wifi sleep problem too on my iMac 2013.

Hi Jane Snijders,

Could you please give the details on which of the following problems you faced and if all of them were fixed by the replacement? The problems discussed in this thread are

1. Wifi Drops

2. Slow Wifi

3. Ping problem (it is not clear if this is a bug or a feature to save power)

4. No wifi connectivity after sleep

I was in Oberhausen (Germany) Apple store. Every Mac (MBP pro/Air, iMac) has These Problems (i Testes 10 different machines). Apple team says they have Never heard about that wifi issue, and they dont guarantee Ping results!!! Unbelievable!! My MBP has not Been repaired because "there is no issue, all Works Fine". It was Not possible to Test the Ping results in a clean wifi Network without 50 People online to get a constant Good Ping. We Tested My MBP Late 2013 and some Older MBP (2011-2012), and because of this **** wifi Network both had high pings, Not constant. Apple Service!?!?!? There is no Service. Its unbelievable!!

Why don't you ask them to switch on a new router which no one else connects to. I guess you dont even need internet connectivity on the router to demo this. You just need a Wifi point.  Else take your router with you.

@Alex:

I have a very slow wifi on my new macbook pro, loading a standard website needs 10-20 seconds to load, sometimes it doesn't load at all!

I read about the experience of other Users who were at the stores and the genius bar. It is unbelievable! So I don't want to drive the long way to the store and argue with a stupid "genius".

I think the problem is widespread but there aren't "Pro" user's only who working with these devices. No "regular" User makes ping test or knows his gateway at all. My colleague has no problems, he likes his new macbook. He had a old "eepc" before. After I did some ping test's, his device showed the same problems, but he can live with that. "It was worst before". This is what I mean.... 

Some people in this thread wrote "apple is definitely aware of this problem", but I don't believe that.....

@nirmalta

1. I had wifi drops on the first one.

   Solved now it seems....

2. At 2 meters from my router wifi appeared to work fine. 

    But had wifi unreponsive wifi when comp woke up from sleep.

    After a month I discovered the slow wifi at about 5 meters distance.

    Checked with other networks ....slow and sometimes even unresponsive

    Solved now with new one.....

3. Did a ping test alongside an older model at applestore...ping drops on mymbp were higher

     Not tested yet with my new one.

4. Had no wifi after sleep with first

     Second one looks ok now

Apple service went fine with me. Swapping took place after 5 weeks ......

I was just in time......one day later and repair would have been only option.

In store it was Not possible to Test a clean wifi. But today i will go there again with My Own Router. But no I am Really confused!!! I Tested My iPhone 4S Ping (1ms constant), an iPad 3 (27ms constant, sometimes 3ms), iPad Mini Retina (26-120ms NOT constant, sometimes 4ms), iPhone 4 (1ms constant), iPad Mini 1 (27-110 NOT constant, sometimes 4ms). I used the App FREE PING from App Store.

Jane Snijders wrote:

 

@nirmalta

 

1. I had wifi drops on the first one.

   Solved now it seems....

I really want to believe its a driver issue, but it cant be if there are actually people out there without wifi problems. Also a driver issue would have been fixed by now, right?

mid-2013 MacBook Air Users are still waiting.

Btw, I eventually experienced all of the problems in that list, depending on the networks i was connecting to. I tested 802.11 g, n, ac, 2,4 GHz and 5GHz.