Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

0 points

New Apple Airport Extreme Latency

Hello

I am having great difficulty with the New Airport Extremes, I have been installing wireless networks using the previous generation Airport Extremes.

The problem is - the old ones have latency less than 1ms. The new ones are erratic, I have tried 8 Diff Routers at diff sites and all have the same issue, to add to the problem, the moment a Network Device Like sonos is connect to the New Extreme the whole network chokes. The Software is all updated and the version on airport is 7.7.1

All the routers are extend via a gigabit switch using CAT 6 Cables, all new network. This is happening at 3 Diff sites, and also all the channels have been set manually using Frequency Scanner by Fluke, and also softares like inSSIDer. All my other projects have the older Extremes with no latency at all.

There is no Co Channel Interferences and I have also taken them to a diff site, Restored them to factory setting and then tried, results are the same!

Please Help

Here are the Ping Examples ..

PING Via Wifi :

PING 10.0.1.4 (10.0.1.4): 56 data bytes

64 bytes from 10.0.1.4: icmp_seq=0 ttl=255 time=4.206 ms

64 bytes from 10.0.1.4: icmp_seq=1 ttl=255 time=4.275 ms

64 bytes from 10.0.1.4: icmp_seq=2 ttl=255 time=4.195 ms

64 bytes from 10.0.1.4: icmp_seq=3 ttl=255 time=4.138 ms

64 bytes from 10.0.1.4: icmp_seq=4 ttl=255 time=4.695 ms

64 bytes from 10.0.1.4: icmp_seq=5 ttl=255 time=4.984 ms

64 bytes from 10.0.1.4: icmp_seq=6 ttl=255 time=7.062 ms

64 bytes from 10.0.1.4: icmp_seq=7 ttl=255 time=4.560 ms

64 bytes from 10.0.1.4: icmp_seq=8 ttl=255 time=4.201 ms

64 bytes from 10.0.1.4: icmp_seq=9 ttl=255 time=23.285 ms

64 bytes from 10.0.1.4: icmp_seq=10 ttl=255 time=6.059 ms

64 bytes from 10.0.1.4: icmp_seq=11 ttl=255 time=108.979 ms

Request timeout for icmp_seq 12

64 bytes from 10.0.1.4: icmp_seq=12 ttl=255 time=1283.157 ms

64 bytes from 10.0.1.4: icmp_seq=13 ttl=255 time=982.065 ms

64 bytes from 10.0.1.4: icmp_seq=14 ttl=255 time=205.354 ms

64 bytes from 10.0.1.4: icmp_seq=15 ttl=255 time=74.677 ms

64 bytes from 10.0.1.4: icmp_seq=16 ttl=255 time=12.894 ms

64 bytes from 10.0.1.4: icmp_seq=17 ttl=255 time=1.701 ms

64 bytes from 10.0.1.4: icmp_seq=18 ttl=255 time=3.416 ms

64 bytes from 10.0.1.4: icmp_seq=19 ttl=255 time=9.891 ms

64 bytes from 10.0.1.4: icmp_seq=20 ttl=255 time=19.909 ms

64 bytes from 10.0.1.4: icmp_seq=21 ttl=64 time=306.461 ms

64 bytes from 10.0.1.4: icmp_seq=22 ttl=64 time=2.334 ms

64 bytes from 10.0.1.4: icmp_seq=23 ttl=64 time=1.648 ms

64 bytes from 10.0.1.4: icmp_seq=24 ttl=64 time=2.137 ms

64 bytes from 10.0.1.4: icmp_seq=25 ttl=64 time=4.431 ms

64 bytes from 10.0.1.4: icmp_seq=26 ttl=64 time=4.522 ms

64 bytes from 10.0.1.4: icmp_seq=27 ttl=64 time=4.246 ms

64 bytes from 10.0.1.4: icmp_seq=28 ttl=64 time=3.968 ms

64 bytes from 10.0.1.4: icmp_seq=29 ttl=64 time=4.631 ms

64 bytes from 10.0.1.4: icmp_seq=30 ttl=64 time=4.120 ms

64 bytes from 10.0.1.4: icmp_seq=31 ttl=64 time=18.521 ms

64 bytes from 10.0.1.4: icmp_seq=32 ttl=64 time=29.760 ms

64 bytes from 10.0.1.4: icmp_seq=33 ttl=64 time=4.307 ms

PING via Direct LAN

PING 10.0.1.4 (10.0.1.4): 56 data bytes

64 bytes from 10.0.1.4: icmp_seq=0 ttl=255 time=0.410 ms

64 bytes from 10.0.1.4: icmp_seq=1 ttl=255 time=1.929 ms

64 bytes from 10.0.1.4: icmp_seq=2 ttl=255 time=1.829 ms

64 bytes from 10.0.1.4: icmp_seq=3 ttl=255 time=1.244 ms

64 bytes from 10.0.1.4: icmp_seq=4 ttl=64 time=0.571 ms

64 bytes from 10.0.1.4: icmp_seq=5 ttl=64 time=0.615 ms

64 bytes from 10.0.1.4: icmp_seq=6 ttl=64 time=0.379 ms

64 bytes from 10.0.1.4: icmp_seq=7 ttl=255 time=1.513 ms

64 bytes from 10.0.1.4: icmp_seq=8 ttl=255 time=1.764 ms

64 bytes from 10.0.1.4: icmp_seq=9 ttl=255 time=0.861 ms

64 bytes from 10.0.1.4: icmp_seq=10 ttl=255 time=0.938 ms

64 bytes from 10.0.1.4: icmp_seq=11 ttl=255 time=1.295 ms

64 bytes from 10.0.1.4: icmp_seq=12 ttl=255 time=1.294 ms

64 bytes from 10.0.1.4: icmp_seq=13 ttl=255 time=0.663 ms

64 bytes from 10.0.1.4: icmp_seq=14 ttl=255 time=1.780 ms

64 bytes from 10.0.1.4: icmp_seq=15 ttl=255 time=0.577 ms

64 bytes from 10.0.1.4: icmp_seq=16 ttl=255 time=1.885 ms

64 bytes from 10.0.1.4: icmp_seq=17 ttl=255 time=1.927 ms

64 bytes from 10.0.1.4: icmp_seq=18 ttl=255 time=1.573 ms

64 bytes from 10.0.1.4: icmp_seq=19 ttl=255 time=1.822 ms

64 bytes from 10.0.1.4: icmp_seq=20 ttl=255 time=1.728 ms

64 bytes from 10.0.1.4: icmp_seq=21 ttl=255 time=1.624 ms

64 bytes from 10.0.1.4: icmp_seq=22 ttl=255 time=1.453 ms

64 bytes from 10.0.1.4: icmp_seq=23 ttl=255 time=1.614 ms

PING to MAIN Router Via LAN

64 bytes from 10.0.1.1: icmp_seq=0 ttl=255 time=0.440 ms

64 bytes from 10.0.1.1: icmp_seq=1 ttl=255 time=0.344 ms

64 bytes from 10.0.1.1: icmp_seq=2 ttl=255 time=0.392 ms

64 bytes from 10.0.1.1: icmp_seq=3 ttl=255 time=0.495 ms

64 bytes from 10.0.1.1: icmp_seq=4 ttl=255 time=0.447 ms

64 bytes from 10.0.1.1: icmp_seq=5 ttl=255 time=0.338 ms

64 bytes from 10.0.1.1: icmp_seq=6 ttl=255 time=0.372 ms

64 bytes from 10.0.1.1: icmp_seq=7 ttl=255 time=0.452 ms

64 bytes from 10.0.1.1: icmp_seq=8 ttl=255 time=0.330 ms

64 bytes from 10.0.1.1: icmp_seq=9 ttl=255 time=0.454 ms

64 bytes from 10.0.1.1: icmp_seq=10 ttl=255 time=0.438 ms

64 bytes from 10.0.1.1: icmp_seq=11 ttl=255 time=0.434 ms

64 bytes from 10.0.1.1: icmp_seq=12 ttl=255 time=0.421 ms

64 bytes from 10.0.1.1: icmp_seq=13 ttl=255 time=0.456 ms

64 bytes from 10.0.1.1: icmp_seq=14 ttl=255 time=0.329 ms

64 bytes from 10.0.1.1: icmp_seq=15 ttl=255 time=0.454 ms

64 bytes from 10.0.1.1: icmp_seq=16 ttl=255 time=0.407 ms

64 bytes from 10.0.1.1: icmp_seq=17 ttl=255 time=0.450 ms

64 bytes from 10.0.1.1: icmp_seq=18 ttl=255 time=0.387 ms

64 bytes from 10.0.1.1: icmp_seq=19 ttl=255 time=0.344 ms

64 bytes from 10.0.1.1: icmp_seq=20 ttl=255 time=0.354 ms

64 bytes from 10.0.1.1: icmp_seq=21 ttl=255 time=0.390 ms

64 bytes from 10.0.1.1: icmp_seq=22 ttl=255 time=0.330 ms

64 bytes from 10.0.1.1: icmp_seq=23 ttl=255 time=0.346 ms

64 bytes from 10.0.1.1: icmp_seq=24 ttl=255 time=0.275 ms

64 bytes from 10.0.1.1: icmp_seq=25 ttl=255 time=0.323 ms

64 bytes from 10.0.1.1: icmp_seq=26 ttl=255 time=0.316 ms

64 bytes from 10.0.1.1: icmp_seq=27 ttl=255 time=0.377 ms

64 bytes from 10.0.1.1: icmp_seq=28 ttl=255 time=0.454 ms

Posted on Sep 15, 2013 4:56 AM

48 replies

Apr 30, 2016 10:43 AM in response to Mark S Gallagher

So, while the IPv6 changes helped, ultimately I had to:

Choose Link-Local only

Using namebench, I selected DNS servers from the report and overwrote the the ghost servers with the two fastest servers.

I turned off my 5Ghz option.

Lastly, I upgraded to a SB6190 from a SB6141

I'm now pinging around 18-30mls and with 120mbps down from comcast and NO packet loss.

2 weeks, all is still well, and our FaceTime recipients are telling us our image quality is razor sharp and my AT&T Wifi isn't breaking up where previously it was so badly pixelated that voice communications were garbage and AppleTV isn't grinding rocks and pausing trying to download movies.

"Tommy Like-y"

I have 2-A1470 time capsules and one A1355.

Apr 30, 2016 11:29 AM in response to xe4

I assume you're still having problems with this?

Your problem, like mine, is not erratic ping times +- 100ms, but rather, long sequences of dropped packets.

I bought my laptop in mid 2015 and it's the only one in my house failing to get THROUGH my airport router to the cable modem reliably.

I am taking it in to Apple on Monday. I am not sure whether they will put a new wifi in my laptop or not, but I doubt that's the issue. In my opinion it seems more like the airport extreme base station.

Yet, a software reset resolves the problem entirely for usually a few days (although admittedly, the time it continues to work seems to be getting shorter and shorter).

Wondering if you have any new information. Did you have to give up on your airport extreme? All other routers work fine for me but they are not as fast.

Apr 30, 2016 11:32 AM in response to Mark S Gallagher

Your problem is different. Your concern was that of the original post: latency. Mine is of entirely dropped packets like xe4 was seeing.

New Apple Airport Extreme Latency