As a 25 year Apple customer, this all remains so disappointing. MBAs allegedly being "captured," kept overnight for analysis, yet new WiFi posts daily. MBAs still rolling off the assembly line with the problem. Only some MBAs have the problem = most frustrating. Are the 'engineers' literaly unable to collate serial #'s to defective WiFi radios to manufacturing source/batch/lot - still?
Why can't they do this simple analysis? Why can't they at least source the problem?
They all roll off the assembly line with the same OS and firmware, yet some are working and some are not. How can we even pretend this isn't a hardware issue? It's been 2 months, still no public ackowledgement from Apple there is a problem. Every day, more defective MBAs roll of the assembly line. I've been waiting since last November to buy a new Apple laptop, and still can't make a purchase with confidence.
For those of you who've been told to upgrade to a retina pro, you might want to read the thread about the fan anomoly on MBPr's. I have a 2008 MB that has the fan anomoly, never was addressed or fixed correctly, Apple was unable to help me after much effort, and I just got used to it overheating and revving up for no reason. It is still working, just noisy and hot sometimes. But no WiFi issues.
I will not buy into another Apple laptop until I am sure it actually works. This is just shameful.
I agree. However, my Air works great with a Time capsule 802.11AC and it didn't work at all with my old Linksys wireless router, so it may be hardware, but the problem requires the laptop plus a given set of routers running some set of configuration parameters. That's a lot of permutations. Don't get me wrong, I agree with you, but it's believable that the Apple test labs use mostly Apple modern routers. They SHOULD have had more of the other guys's routers but I don't have any trouble believing that they didn't have enough of them.
I'd like Apple to come clean here, I think it would be to their benefit to do so because not doing that erodes trust just when Android is gaining on IOS and flashy new Windows 7 laptops are gaining on the Air. It's stupid for them to do these things, but I could tell you stories about MY corporation. Corporations often don't make rational decisions. Back when Apple was two guys in a garage, it was different and counterculture, but now they're a big corporation just like all the others, with all the pointless and counterproductive secrecy and aversion to admitting blame.
I've read that a few people on here and other forums have gone through 3 MBA replacements all having Wi-Fi issues and I always thought they were maybe exaggerating to get Apple's attention, but now that I have gone through 3 replacements myself I'm starting to lose all hope. I'm going to have to return it if Apple doesn't come up with a solution soon.
keep working support and don`t let them off the hook-there are almost 150,000 views here and 400,000 on another wi-fi drop post. Apple knows about this and I believe there is a solution coming soon. Great machine otherwise, or I would be posting from a chromebook.I am on #3 myself and still dropping.
Don't hold your breath. Maybe when the thread will reach 1mil views, Apple will issue a statement saying that it's the customer's fault for not buying only Apple ac routers. They will also offer a solution for when you travel: call in advance every airport, hotel and coffee shop you plan on visiting and ask them if they have an Apple ac router. If not, then you should change your vacation plans accordingly.
How is that for a fix? :)
PS: My new 13" MBA works perfectly, so I will not change my vacation plans. At least not yet.
Ping values are all over the place (update installed), but download speeds are great (between 60-90 Mb/s on a theoretical 120 Mb/s network, about 20-25 feet from the Technicolor wifi router, with 1 wall and some doors in between, on a 2.4Ghz, n network). Also, I have no problems using Skype, Facetime, etc.
The latest apple routers don't fix the issue before people read and think that's the solution. I have the latest 11ac router from apple and the problem it's still there.
Carbon dragon, you say you don't have the problem. Have you got the latest software update and tried the ping test to your router over 30 seconds or so?
Just bought a brand new maxed-out 13" Air. Turned it on and did the basic setup and tried to start using it. WIFI would not report an issue but internet connectivity was lost after 1-2 minutes.
Found this forum and was able to keep it up long enough to install only the wifi SW update. So far this has solved the initial issue but very disappointed also that this computer shipped from China 3 days ago still showing the initial issue...
Thanks andyman2 and a few others for the observations about the wireless latency issues on these 2013 MacBook Airs, which is different from disconnects, per se. I work at Cisco, and I was not happy to see that my relatively new MacBook Air BTO was experieincing occassionally slow issues when browsing and streaming video, etc... and yes, I too applied Apple's recent wifi patch without really needing it, and I probably wish I didn't install it now.
An example on how this can vary based on your setup: I'm finding that when connecting my MBA to the currently best-in-class ASUS RT-AC66U wireless router running the latest firmware from ASUS, my MacBook Air often exhibits ping times in excess of 200 - 1800ms with occassional dropped packets, whereas when I connect my MacBook Air to a Linksys EA6500, the ping times are more consistent with zero dropped packets, but the ping times still average around 15-30ms even when the router is located within just a few feet of the laptop (which isn't stellar).
Btw, a suggestion for those of you who are trying to determine if your 2013 MacBook Air has this wireless latency issue now: DON'T test it by browsing the Internet, etc. The issue is with your LAN, and not your WAN.
In other words, the poor latency issue on these MacBook Airs has to do with the connection between your Mac and your wireless device (wireless router or access point). It has NOTHING to do with the Internet, per se... and trying to use the Internet as the basis for your test only confuses the matter at hand.
The only reliable way to determine if you have this issue, is to do what andyman2 and others have recommended:
1) locate the IP address of your router / access point that you are connected to. If you don't know how to do that, its most likely the device listed in Settings --> Network Preferences --> Advanced --> TCP/IP --> Router
2) go to Applications --> Utilities --> Network Utility --> Ping and type in the IP address listed from #1 (e.g. "192.168.0.1")
3) share your results here
Most likely you have this latency issue if your ping times exceed 30ms. Hopefully Apple releases another driver update sooner vs. later, as I'm too lazy to roll back my Mac prior to when I installed the WiFi update.
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=23.115 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.034 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=46.989 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.211 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=11.620 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=34.858 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=57.692 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=2.137 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=50.761 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=22.496 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=3.469 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=69.283 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=91.180 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=11.585 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=33.308 ms
--- 192.168.0.1 ping statistics ---
15 packets transmitted, 15 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.034/30.849/91.180/26.598 ms
So you're thinking this isn't a hardware issue and could be fixed with another update?
64 bytes from 192.168.11.1: icmp_seq=3 ttl=64 time=24.325 ms
64 bytes from 192.168.11.1: icmp_seq=4 ttl=64 time=49.427 ms
64 bytes from 192.168.11.1: icmp_seq=5 ttl=64 time=47.795 ms
64 bytes from 192.168.11.1: icmp_seq=6 ttl=64 time=1.988 ms
64 bytes from 192.168.11.1: icmp_seq=7 ttl=64 time=13.118 ms
64 bytes from 192.168.11.1: icmp_seq=8 ttl=64 time=38.068 ms
64 bytes from 192.168.11.1: icmp_seq=9 ttl=64 time=46.348 ms
64 bytes from 192.168.11.1: icmp_seq=10 ttl=64 time=46.332 ms
64 bytes from 192.168.11.1: icmp_seq=11 ttl=64 time=1.984 ms
64 bytes from 192.168.11.1: icmp_seq=12 ttl=64 time=27.099 ms
64 bytes from 192.168.11.1: icmp_seq=13 ttl=64 time=0.857 ms
64 bytes from 192.168.11.1: icmp_seq=14 ttl=64 time=44.750 ms
64 bytes from 192.168.11.1: icmp_seq=15 ttl=64 time=45.092 ms
64 bytes from 192.168.11.1: icmp_seq=16 ttl=64 time=15.997 ms
64 bytes from 192.168.11.1: icmp_seq=17 ttl=64 time=36.370 ms
64 bytes from 192.168.11.1: icmp_seq=18 ttl=64 time=43.619 ms
64 bytes from 192.168.11.1: icmp_seq=19 ttl=64 time=44.112 ms
64 bytes from 192.168.11.1: icmp_seq=20 ttl=64 time=4.815 ms
64 bytes from 192.168.11.1: icmp_seq=21 ttl=64 time=4.881 ms
64 bytes from 192.168.11.1: icmp_seq=22 ttl=64 time=22.589 ms
64 bytes from 192.168.11.1: icmp_seq=23 ttl=64 time=40.573 ms
--- 192.168.11.1 ping statistics ---
24 packets transmitted, 24 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.857/29.125/49.427/18.350 ms
It seems that this issue also happens to me. I have been using my MBA2013 (i7) for a month without noticing the problem (just surfing internet). How can I do with this defect? I have to wait for a new patch? Am I eligible to exchange it after more than a month used (and i7 model is not in the stores)?