Unifi AP-AC Terrible performance

[KingCollins]

Hey guys, I'll keep it short. Managed to get an older style Unifi AP-AC from work a few months back (The older square style). I have no special setting enabled, the AP is running all default settings. When I ping google.com I get terrible response times. As you can see below, when I switched from the Unifi AP to a different Asus AP, the ping times are dramatically different. I also frequently experience ping timeouts & dropped packets. This is resulting in stuttering when streaming video and overall brutal performance. Have also confirmed is it not a switch, cable or router issue.

 

My question is, can an AP just die like this? Is there any Ubiquiti gurus out there that can give me pointers?

 

➜  Work ping google.com
PING google.com (xx.xx.xx.xx): 56 data bytes
64 bytes from xx.xx.xx.xx: icmp_seq=0 ttl=44 time=490.496 ms
64 bytes from xx.xx.xx.xx: icmp_seq=1 ttl=44 time=490.760 ms
64 bytes from xx.xx.xx.xx: icmp_seq=2 ttl=44 time=147.841 ms
64 bytes from xx.xx.xx.xx: icmp_seq=3 ttl=44 time=63.657 ms
64 bytes from xx.xx.xx.xx: icmp_seq=4 ttl=44 time=292.242 ms
64 bytes from xx.xx.xx.xx: icmp_seq=5 ttl=44 time=483.247 ms
64 bytes from xx.xx.xx.xx: icmp_seq=6 ttl=44 time=129.359 ms
^C
--- google.com ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 63.657/299.657/490.760/175.029 ms
➜  Work ping google.com
PING google.com (xx.xx.xx.xx): 56 data bytes
64 bytes from xx.xx.xx.xx: icmp_seq=0 ttl=44 time=18.879 ms
64 bytes from xx.xx.xx.xx: icmp_seq=1 ttl=44 time=16.945 ms
64 bytes from xx.xx.xx.xx: icmp_seq=2 ttl=44 time=19.457 ms
64 bytes from xx.xx.xx.xx: icmp_seq=3 ttl=44 time=22.274 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 16.945/19.389/22.274/1.908 ms

 

[Dujith]

The square AP-AC's are not so great to start with. Bad 5Ghz and they can overheat.

Having said that, how did you set it up? With controller software? (older version as the newest cant adopt it)

[KingCollins]

Yeah, it's just so strange, I've never seen an AP that is so consistent with having bad performance. It's impressive actually how bad it is 

 

I set it up with a locally running controller software on Windows (at the time I didn't have any idea how Ubiquity hardware works so go easy on me).

Now I know that you can have a controller software running on a server I'll probably get that set up. That would hardly make a difference though would it?

[Dujith]

You only need to set it once, it does not require a controller to run in basic AP mode.

In all honesty that AP is just crap and nothing you can really do about it