New Apple Airport Extreme Latency

This problem can be resolved by running your Airport as a router and not a bridge.

I wont bore you with the details of why this is a problem but just trust me.. Most ISP modems with built in firewalls will have problems with dropped packets coming from the Airports... High Latency etc..

If you have a cable modem or similar you can usually call your ISP to have them set your modem as a "Bridge"

Or you might be able to set it Yourself in the firmware..

You will be disabling any firewall on your modem by doing this, and YES this is what you want to do!

Now Set the Airport as a Router. "DHCP and NAT"

If you are doing any port forwarding you can Google how to set this on the airport..

Unfortunately The "Firewall" settings are disappointingly limited.

Apple should build more features into this device considering the price point.

If you live in an apartment complex you will also have interference issues with all of the other wifi in you area.

in most Cases, leaving your Airport Channels on Auto will work ok, but feel free to try other channels and see if you can get your latency down.

*Holding the option key down and clicking your wifi icon in the top toolbar will give you advanced information about your wifi and surrounding networks.

are you replacing old apple extremes or something else? are you sure you have your new extremes setup exactly the same way? (bridge mode...)

I remember seeing something similar when i replaced my dlink dir-825 with my 5th gen airport exteme. I have a similar setup where my ae is connected via a gigabit switch to my main router. I saw terrible ping times when trying to ping outside my network. if i recall correctly, I either changed my ssid to resolved the issue or i rebooted all my network gear.

I am seeing the same issue! I have a new MacBook Air (Haswell) with the .ac chipset. If I connect to my new Airport Extreme .ac router (in bridge mode), I sometimes see latency spikes over 100ms just to get to my router (and the macbook is only 5 feet away from the airport). If I connect to my prev gen Airport Express (802.11N 2.4 or 5 Ghz), I never see this issue (same config - bridge mode to main switch/gw). I basically don't want to use ac right now since I don't need the bandwidth and care more about latency (especially since I use Citrix to remote into the office).

Hopefully there is a firmware upgrade on the way and it gets here quick.

In case it matters to Apple, I too have the same problem; business user, latest Apple MBP 15", latest firmware (7.7.2) on the latest AE hardware.

PING 192.168.1.1 (192.168.1.1): 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.544 ms

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.242 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.763 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.327 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=118.392 ms

64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=101.265 ms

64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=78.284 ms

64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=58.364 ms

64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.943 ms

64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.973 ms

64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=2.171 ms

64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=1.706 ms

64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=104.771 ms

64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=2.437 ms

64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=95.412 ms

64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=83.603 ms

64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=73.561 ms

64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=60.774 ms

I'm having the same problem - also using bridge mode. My workaround was to enable the 5ghz network (wireless options under the wireless tab in airport utility) with it's own network name and then connect to the original 2.4ghz network. Since 802.11ac doesn't work in the 2.4ghz range, this forces my 2013 MacBook Air to use 802.11n, which is much more responsive, even though the bandwidth is lower, because it doesn't suffer from this high latency issue.

My friend is also seeing the same issue. I have filed a bug report ... hoping someone at Apple picks up on it. Not acceptable for high end hardware like new Macbook's and the new Extreme.

I have recently switched from an AE to a 2TB Time Capsule and I am seeing some fluctuating response time pinging from my Linux server to the TC. The Linux server is connected via a gig port. Has anyone downgraded their firmware to see if it resolved the issues?

I have the same latency with my MBPr 13 late 2013, depsite connected on the 2.4Ghz or 5Ghz SSID.

The bandwith is pretty good, i can transfer files to my NAS at 39Mo/s (when connected at 800mb or 1Gb/s) but the latency is horrible, i work in Networks and i've installed many Aruba systems, i never saw a poor latency like that.

Same deal here, nearly. On Macbook Air 13-inch, Mid 2013 connecting to an Apple Time Capsule 2TB ME177LL/A. Both are up to date with firmware.

64 bytes from 10.0.0.1: icmp_seq=353 ttl=63 time=3.797 ms

64 bytes from 10.0.0.1: icmp_seq=354 ttl=63 time=4.063 ms

64 bytes from 10.0.0.1: icmp_seq=355 ttl=63 time=2.735 ms

64 bytes from 10.0.0.1: icmp_seq=356 ttl=63 time=2.123 ms

64 bytes from 10.0.0.1: icmp_seq=357 ttl=63 time=1.961 ms

64 bytes from 10.0.0.1: icmp_seq=358 ttl=63 time=1.799 ms

64 bytes from 10.0.0.1: icmp_seq=359 ttl=63 time=3.238 ms

64 bytes from 10.0.0.1: icmp_seq=360 ttl=63 time=2.906 ms

64 bytes from 10.0.0.1: icmp_seq=361 ttl=63 time=195.350 ms

64 bytes from 10.0.0.1: icmp_seq=362 ttl=63 time=1202.865 ms

64 bytes from 10.0.0.1: icmp_seq=363 ttl=63 time=201.747 ms

64 bytes from 10.0.0.1: icmp_seq=364 ttl=63 time=1186.507 ms

64 bytes from 10.0.0.1: icmp_seq=365 ttl=63 time=186.310 ms

64 bytes from 10.0.0.1: icmp_seq=366 ttl=63 time=185.911 ms

64 bytes from 10.0.0.1: icmp_seq=367 ttl=63 time=1189.917 ms

64 bytes from 10.0.0.1: icmp_seq=368 ttl=63 time=185.539 ms

64 bytes from 10.0.0.1: icmp_seq=369 ttl=63 time=1186.169 ms

64 bytes from 10.0.0.1: icmp_seq=370 ttl=63 time=186.339 ms

64 bytes from 10.0.0.1: icmp_seq=371 ttl=63 time=1185.758 ms

64 bytes from 10.0.0.1: icmp_seq=372 ttl=63 time=187.125 ms

64 bytes from 10.0.0.1: icmp_seq=373 ttl=63 time=183.102 ms

64 bytes from 10.0.0.1: icmp_seq=374 ttl=63 time=1185.733 ms

64 bytes from 10.0.0.1: icmp_seq=375 ttl=63 time=184.602 ms

64 bytes from 10.0.0.1: icmp_seq=376 ttl=63 time=2.817 ms

64 bytes from 10.0.0.1: icmp_seq=377 ttl=63 time=2.047 ms

64 bytes from 10.0.0.1: icmp_seq=378 ttl=63 time=2.538 ms

10.0.0.1 is the time capsule.

I'm connected to it with 802.11ac.

Sitting next to another macbook air, older one, on 802.11n which is getting ~1ms pings.

I'm noticing this not because I'm constantlly pinging stuff for fun, but because typing on terminal on remote machines is infuriating.

Have about a dozen other devices connected to this thing that work well. Seems like 802.11ac is the culprit.

There's another thread here which discusses the workaround and potential fix. but essentially, you open a terminal and ping the gateway you are on every 0.2sec. The wifi driver is far too aggressive about power saving, so forcing traffic keeps the connection alive. I'm not sure it has anything to do with 802.11ac at all ... but it seems like only the 2013 Macbook's are affected.

Nice, thanks for the heads up. To further put you out, you happen to have a link to the other thread? Looked around, didn't see it.

Thanks again.

I'd like to know also. I have a thread here:

http://us.battle.net/wow/en/forum/topic/11675567657?page=1

for me, I noticed it before the 2013 MBP, and now I am only seeing it on 5ghz side. 2.4 is fine, as is 5ghz to my older time capsule.

In fact, after many tests here at home, it appears that when the connection is established at full speed (1.3Gbit/s), the latency is perfect, close to 1ms.

The latency is high when all the 80Mhz band can't be reach, i think it's a channel selection problem or load balancing mismatch in the ac algorithm.

Anyway, it's very difficult to reach the 1.3Gbit/s or you need to place your MacBook pro just in front the Airport and enough close, 1 meter max.

I hope it's just a firmware problem and Apple will solve the problem, because when you have a pretty speed fiber at home, it's a shame to have this kind of latency.

I am having the same issue.

I purchased a brand new Apple Airport Extreme last night.

I currently have Telstra 100Mbit cable (Netgear CG3100D-2 wireless router).

I play games using the Netgear over wireless no problem. I installed the Airport Extreme (Firmware V 7.7.2), everything working ok.

Fired up some games until I noticed some serious lag spikes during gameplay.

So I began doing some testing, ping tests etc.

64 bytes from 61.88.88.88: icmp_seq=42 ttl=244 time=10.624 ms

64 bytes from 61.88.88.88: icmp_seq=43 ttl=244 time=10.837 ms

64 bytes from 61.88.88.88: icmp_seq=44 ttl=244 time=13.796 ms

64 bytes from 61.88.88.88: icmp_seq=45 ttl=244 time=11.114 ms

Request timeout for icmp_seq 46

Request timeout for icmp_seq 47

64 bytes from 61.88.88.88: icmp_seq=46 ttl=244 time=2003.859 ms

64 bytes from 61.88.88.88: icmp_seq=47 ttl=244 time=1003.229 ms

64 bytes from 61.88.88.88: icmp_seq=48 ttl=244 time=10.979 ms

64 bytes from 61.88.88.88: icmp_seq=49 ttl=244 time=12.247 ms

64 bytes from 61.88.88.88: icmp_seq=50 ttl=244 time=13.644 ms

64 bytes from 61.88.88.88: icmp_seq=51 ttl=244 time=17.425 ms

64 bytes from 61.88.88.88: icmp_seq=52 ttl=244 time=13.416 ms

Re-enabled the wireless on the Netgear, no problems. No spikes.

Started doing some reading, seems like its a common issue.

Now this is very annoying since I payed a premium $250 for a wireless router when you can get alternatives for around $100 (max!)

Has anyone found a solution, is there a firmware update coming?