Late 2013 Macbook Pro Retina 13'' Wifi Issues

Would be great if Apple stopped wasting their customers time with useless replacements.. but they don't even read their own support forums.

I was turned off the Apple Magic Mouse and my problems with slow wifi connection will be solved %( MBPro13 late 2013

Apple please, do it something with it!

same big problems with 13" MBPr late 2013 here :-(

Heres my ping:

Ping has started…

PING 192.168.2.1 (192.168.2.1): 56 data bytes

64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=58.553 ms

64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=34.357 ms

64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=52.297 ms

64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=45.963 ms

64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=7.712 ms

64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=3.931 ms

64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=42.719 ms

64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=219.384 ms

64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=194.585 ms

64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=110.721 ms

--- 192.168.2.1 ping statistics ---

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

round-trip min/avg/max/stddev = 3.931/77.022/219.384/70.911 ms

Actually i have already returned an Airport Extreme Router, which was probably perfectly good. I did not suspect the MacBook being the culprit, especially since i have never had wifi issues with any other notebook or router. A bit disappointing apple..

should try using a HD HomeRun streaming live TV on Late 2013 MacBook Pro, stream keeps stalling every few minutes when the latency spikes kick in

even just loading websites, the throughput is great but simple network activites like ssh and just initial page loading seem to incur huge latencies using both official AirPort Extreme 802.11ac and other 802.11n routers

ok, i just read the complete thread and figured out that a normal ping is not representative on the MBPr models. The -i 0.2 ping gets me good results. Also i am not seeing any lost packets so far.

However, loading websites is slow. I have never had such slow WiFi with any other notebook, sometimes it takes several seconds until a page loads.

now i left the ping -i 0.2 running in the background, turns out i am getting lots of "request timeouts" in between the successful pings. Here is an example:

64 bytes from 192.168.2.1: icmp_seq=9622 ttl=64 time=4.081 ms

64 bytes from 192.168.2.1: icmp_seq=9623 ttl=64 time=4.845 ms

Request timeout for icmp_seq 9624

Request timeout for icmp_seq 9625

64 bytes from 192.168.2.1: icmp_seq=9626 ttl=64 time=4.525 ms

64 bytes from 192.168.2.1: icmp_seq=9627 ttl=64 time=4.915 ms

Request timeout for icmp_seq 9628

64 bytes from 192.168.2.1: icmp_seq=9629 ttl=64 time=4.137 ms

64 bytes from 192.168.2.1: icmp_seq=9630 ttl=64 time=4.050 ms

64 bytes from 192.168.2.1: icmp_seq=9631 ttl=64 time=4.383 ms

64 bytes from 192.168.2.1: icmp_seq=9632 ttl=64 time=5.648 ms

64 bytes from 192.168.2.1: icmp_seq=9633 ttl=64 time=5.222 ms

Request timeout for icmp_seq 9634

Request timeout for icmp_seq 9635

Request timeout for icmp_seq 9636

Request timeout for icmp_seq 9637

64 bytes from 192.168.2.1: icmp_seq=9638 ttl=64 time=4.450 ms

Request timeout for icmp_seq 9639

Request timeout for icmp_seq 9640

Request timeout for icmp_seq 9641

Request timeout for icmp_seq 9642

Request timeout for icmp_seq 9643

Request timeout for icmp_seq 9644

Request timeout for icmp_seq 9645

Request timeout for icmp_seq 9646

64 bytes from 192.168.2.1: icmp_seq=9647 ttl=64 time=12.563 ms

Request timeout for icmp_seq 9648

64 bytes from 192.168.2.1: icmp_seq=9649 ttl=64 time=3.607 ms

64 bytes from 192.168.2.1: icmp_seq=9650 ttl=64 time=5.348 ms

64 bytes from 192.168.2.1: icmp_seq=9651 ttl=64 time=3.895 ms

Eventualy it completely looses the connection, which can only be re-established by turning off wifi and then reconnecting :-(

Problem still exists with the latest 10.9.1 special release for the new retina MBPs.

My problem is, that i can't connect to fritzbox 7330 sl and a few other APs after resuming from sleep.

Only a reboot helps.

reboot, really? Have you tried to turn off / turn back on the WiFi? This works for me.

Also I have been using VPN a lot lately, I got a lot less problems there. Probably keeps the line busy somehow.

Anyway I still believe its not a hardware issue and hope that apple will fix this eventually.

Never Mind. All the best to you and Happy New Year.

johnniecache wrote:

Anyway I still believe its not a hardware issue and hope that apple will fix this eventually.

Because it is fixed in 10.9.2 on my Macbook Pro.

Well there goes that NDA you signed.

If I were to take my MacBook (13 inch, Haswell) back to Apple because of this issue, what would happen? Would I get a replacement or a refund (Bought mine about a month ago)? Is there any chance, that a replacement MacBook wouldn`t also have the same Wi-Fi problem?

In the last months I had two MacBooks (13" Air & 13" MBPRO Retina, both late 2013 version) with Wi-Fi problems. Both had pings ranging from 1ms to 800ms. The Air's Wifi issue was especially hard, I couldn't make a Skype call for more than 15min. - of course I returned that one. Three and a half months later I decided to give the new MacBook Pro Retina a shot. Also that one had a Wi-Fi issue, but not as dramatic as the Air. Pings were also quite unstable (in comparison my MacBook Pro 2009 had pings ranging from 1ms - 3ms in the same network and in the same room at the same time), but long Skype calls and big downloads were no problem. After reading through some posts, I accepted the fact that the Wi-Fi issue was just a "feature", which was not well executed.

Last monday I went to an Apple Store in Germany and tested all the MacBooks in the store. Somehow pinging the router was not possible, but I pinged www.google.com via Terminal and the result was "calming" in a sense that I now know that every MacBook has dramatic pings and dropped packages. The only model, which is not effected is the old MacBook Pro non-retina.

In the end unfortunately I also had to return my MacBook Pro Retina because of the burn-in problem with the retina display (also known as "ghosting").

After two returned MacBooks the Apple support gave me a 100€ discount. This is nice, but I'd rather prefer a perfectly working machine without having to worry about what will happen with the wifi in the future than a discount. I don't buy Apple because it's cheap, I buy it because it (should) work. I have the feeling that Apple currently has a big problem with their quality control. The products are not as good as they were a couple of years ago. Fortunately they have a good after sales service, otherwise they would lose many customers.

So one advice for everyone buying a newer Macbook: Test it throroughly, make long Skype calls, download huge files >1GB, test the display. If there is anything not working well, don't hesitate to make use of the 14 days return policy. Return your MacBook until you have the perfect one. You will probably even get a discount for doing it. But don't accept the fact that you pay tons of money to get product which is not working perfectly (in the case of Wi-Fi and the display it's not even about perfection, but basic functions which should work...).

But did you eventually end up with the mbpr that wasn't affected by this issue? To my knowledge, it still isn't clear whether all late 2013 macbooks are affected.

I'm also having this issue... Wifi becomes incredibly slow then fails altogether. Late 2013 13" MacBook Pro Retina. After several support calls to Apple, they couldn't figure out what was wrong with it so I'm sending it back. After doing some searching, I'm afriad to order another one for fear that it might have the same problems.

Should I go back to 13" MacBook Air until this gets sorted out?