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

xe4

Level 1

0 points

Apr 21, 2014 12:01 AM in response to xe4

64 bytes from 61.88.88.88: icmp_seq=202 ttl=244 time=10.844 ms

64 bytes from 61.88.88.88: icmp_seq=203 ttl=244 time=10.698 ms

64 bytes from 61.88.88.88: icmp_seq=204 ttl=244 time=10.401 ms

64 bytes from 61.88.88.88: icmp_seq=205 ttl=244 time=10.622 ms

64 bytes from 61.88.88.88: icmp_seq=206 ttl=244 time=19.705 ms

Request timeout for icmp_seq 207

Request timeout for icmp_seq 208

Request timeout for icmp_seq 209

Request timeout for icmp_seq 210

Request timeout for icmp_seq 211

Request timeout for icmp_seq 212

Request timeout for icmp_seq 213

Request timeout for icmp_seq 214

Request timeout for icmp_seq 215

Request timeout for icmp_seq 216

Request timeout for icmp_seq 217

Request timeout for icmp_seq 218

Request timeout for icmp_seq 219

Request timeout for icmp_seq 220

64 bytes from 61.88.88.88: icmp_seq=207 ttl=244 time=2943.168 ms

64 bytes from 61.88.88.88: icmp_seq=208 ttl=244 time=2743.007 ms

64 bytes from 61.88.88.88: icmp_seq=209 ttl=244 time=2543.037 ms

64 bytes from 61.88.88.88: icmp_seq=210 ttl=244 time=2342.177 ms

64 bytes from 61.88.88.88: icmp_seq=211 ttl=244 time=2145.218 ms

64 bytes from 61.88.88.88: icmp_seq=212 ttl=244 time=1945.794 ms

64 bytes from 61.88.88.88: icmp_seq=213 ttl=244 time=1746.521 ms

64 bytes from 61.88.88.88: icmp_seq=214 ttl=244 time=1545.931 ms

64 bytes from 61.88.88.88: icmp_seq=215 ttl=244 time=1345.379 ms

64 bytes from 61.88.88.88: icmp_seq=216 ttl=244 time=1148.822 ms

64 bytes from 61.88.88.88: icmp_seq=218 ttl=244 time=747.786 ms

64 bytes from 61.88.88.88: icmp_seq=217 ttl=244 time=949.654 ms

64 bytes from 61.88.88.88: icmp_seq=219 ttl=244 time=548.851 ms

64 bytes from 61.88.88.88: icmp_seq=220 ttl=244 time=348.464 ms

64 bytes from 61.88.88.88: icmp_seq=221 ttl=244 time=147.951 ms

64 bytes from 61.88.88.88: icmp_seq=222 ttl=244 time=11.337 ms

64 bytes from 61.88.88.88: icmp_seq=223 ttl=244 time=14.366 ms

64 bytes from 61.88.88.88: icmp_seq=224 ttl=244 time=11.587 ms

64 bytes from 61.88.88.88: icmp_seq=225 ttl=244 time=10.460 ms

64 bytes from 61.88.88.88: icmp_seq=226 ttl=244 time=14.967 ms

64 bytes from 61.88.88.88: icmp_seq=227 ttl=244 time=13.303 ms

Apr 22, 2014 11:37 PM in response to sawan02

Try the new firmware that came out today. It seems to have resolved my issues.

xe4

Level 1

0 points

Apr 23, 2014 1:09 AM in response to Steven W. Riggins

Nope, did not fix my issues.

Have you tried FPS gaming on it?? thats how i noticed it initially.

This was taken straight after the firmware update (7.7.3)

64 bytes from 61.88.88.88: icmp_seq=137 ttl=244 time=11.488 ms

64 bytes from 61.88.88.88: icmp_seq=138 ttl=244 time=12.289 ms

64 bytes from 61.88.88.88: icmp_seq=139 ttl=244 time=9.974 ms

64 bytes from 61.88.88.88: icmp_seq=140 ttl=244 time=14.052 ms

64 bytes from 61.88.88.88: icmp_seq=141 ttl=244 time=11.707 ms

Request timeout for icmp_seq 142

Request timeout for icmp_seq 143

Request timeout for icmp_seq 144

Request timeout for icmp_seq 145

Request timeout for icmp_seq 146

Request timeout for icmp_seq 147

Request timeout for icmp_seq 148

Request timeout for icmp_seq 149

Request timeout for icmp_seq 150

64 bytes from 61.88.88.88: icmp_seq=142 ttl=244 time=1990.509 ms

64 bytes from 61.88.88.88: icmp_seq=143 ttl=244 time=1789.642 ms

64 bytes from 61.88.88.88: icmp_seq=144 ttl=244 time=1589.543 ms

64 bytes from 61.88.88.88: icmp_seq=145 ttl=244 time=1389.358 ms

64 bytes from 61.88.88.88: icmp_seq=146 ttl=244 time=1189.255 ms

64 bytes from 61.88.88.88: icmp_seq=148 ttl=244 time=790.990 ms

64 bytes from 61.88.88.88: icmp_seq=147 ttl=244 time=991.440 ms

64 bytes from 61.88.88.88: icmp_seq=149 ttl=244 time=591.675 ms

64 bytes from 61.88.88.88: icmp_seq=150 ttl=244 time=391.502 ms

64 bytes from 61.88.88.88: icmp_seq=151 ttl=244 time=191.913 ms

64 bytes from 61.88.88.88: icmp_seq=152 ttl=244 time=11.518 ms

64 bytes from 61.88.88.88: icmp_seq=153 ttl=244 time=10.030 ms

64 bytes from 61.88.88.88: icmp_seq=154 ttl=244 time=16.774 ms

64 bytes from 61.88.88.88: icmp_seq=155 ttl=244 time=14.225 ms

64 bytes from 61.88.88.88: icmp_seq=156 ttl=244 time=23.780 ms

Apr 23, 2014 1:34 AM in response to sawan02

Hi,

1st test: Could you try the same test but by ping your router gateway, not the final destination.

2nd test: Coult you get closer to the Airport to reach the max 802.11ac speed: 1.3Gb/s, if it's the problem i described here, you will se a perfect latency.

Thanks.

xe4

Level 1

0 points

Apr 23, 2014 1:44 AM in response to Silvain24

1st test.

Pinging via wireless to the airport extreme (No problem)

Pinging via Wireless through airport extreme to internet gateway. (problem)

64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=1.393 ms

64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=1.254 ms

64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=2.229 ms

64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=2.185 ms

Request timeout for icmp_seq 49

Request timeout for icmp_seq 50

Request timeout for icmp_seq 51

64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=807.938 ms

64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=606.932 ms

64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=406.222 ms

64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=205.725 ms

64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=5.467 ms

64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=1.856 ms

I already very close as it is. Its nothing to do with distance.

xe4

Level 1

0 points

Apr 23, 2014 2:00 AM in response to xe4

Initial tests were done using my iMac.

Now, using my Macbook.

Standing next to the Airport Extreme.

Pinging the cable modem via Airport Extreme. Same result.

64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=2.343 ms

64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=1.663 ms

Request timeout for icmp_seq 49

Request timeout for icmp_seq 50

64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=2532.162 ms

64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=1530.738 ms

64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=529.805 ms

64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=2.646 ms

Apr 23, 2014 2:05 AM in response to sawan02

All your devices (MacBook and IMac) are on 802.11ac or 802.11an only?

xe4

Level 1

0 points

Apr 23, 2014 2:07 AM in response to Silvain24

Ive used several different devices.

Macbook.

Macbook Pro.

iMac.

Dell Windows 7 (Notebook)

The iMac uses 802.11ac.

The others are a combination.

Apr 23, 2014 2:11 AM in response to sawan02

If you make the test directly behind your router you don't have any latency issue? And what about with a cable behind the Airport?

xe4

Level 1

0 points

Apr 23, 2014 2:19 AM in response to Silvain24

If I directly connect to the cable modem/router via its wireless. No problems.

It's the AirPort Extreme 100%.

I have don't countless tests.

Directly hard wired into the apple AirPort Extreme. No problems.

It's the wifi on the airport.

Also. This is my second unit. I purchased it on Sunday. Took it back and got a replacement yesterday.

Same thing.

Apr 23, 2014 2:21 AM in response to sawan02

Could you try by disabling the 5Ghz, keep only 2.4 band.

xe4

Level 1

0 points

Apr 23, 2014 2:23 AM in response to Silvain24

Tried both. I have spent hours trying different things. But I appreciate any further suggestions.

Tried using 2.4 and 5ghz.

Apr 23, 2014 2:34 AM in response to sawan02

Ok, so i suppose you already try to move your Airport in an other place, it seem there is en environment issue with you radio channels.

Try to disable the N too on your unique test device (in the Network card parameters in Windows, it's more easy). Allow only 802.11bg, not bgn. N use many channels, and if many are used by neighbors or perturbation, it will degrade all the signal.

xe4

Level 1

0 points

Apr 23, 2014 2:42 AM in response to Silvain24

Do you really think it's an environment issue?

My cable modem does not suffer the same issue when I connect directly to its wifi.

I disable the wifi on the modem. Enable the airport. That's the issue.

I highly doubt its environment. I will try however. I just don't agree with that my friend.

I feel like I should just purchase another device.

If you do a simple google search.

Apple AirPort Extreme ping spikes

Apple AirPort Extreme lag spikes.

It's a wide spread issue. Tons of people are having this problem.

Apr 23, 2014 2:53 AM in response to sawan02

I'm agree, but all experiences here are different, all people don't have the same behaviors.

Mine have the same behaviors than yours, but only on 802.11ac, and not at full speed. I lost many pings when the Macbook (Retina 13" last gen) is at 860Mb/s for example, but when i get very close to airport to reach the max rate (1.3Mb/s), the problem disappear.

Sometimes there is very strange behaviors with Wifi, especially with high speed and the new 802.11ac band. More channels are aggregates, more troubles you will have.

i'm network project manager and make a lot of Wifi on professional products, i just want to help and you can't imagine all the problem with this technology.

New Apple Airport Extreme Latency