@cristianvdr, might be caused by wrong settings. Are you really connecting to a WISP?

AP Client Router mode uses a wireless client connection as the WAN and turns on routing from LAN to WAN.

This means you have to carefully set up two networks, especially the LAN network:

@cristianvdr, ok. I have only CPE V1 hardware in the field running firmware version 2.2.1, but not V3 hardware. Maybe the new model or the firmware v2.2.2 has a bug. I recommend to open a ticket with your local TP-Link support (see your country's TP-Link website for contact info of the support department).

cristianvdr wrote

The firmware has few problems and this is just one of them.

Maybe the firmware v2.2.2 has issues which causes freezes (I never experienced this and we have several installations at customer sites running flawlessly since years). But spikes in latency is definitively not a bug. It is pretty normal over every WiFi link, which is a half-duplex shared medium where only one device can send at the same time, especially if you serve standard consumer devices with omnidirectional antennas using a CPE with directional antennas which can easily lead to re-transmissions. In fact, CPEs are not designed to serve standard wireless clients and they don't perform well doing so.

If you want an Ethernet-like latency < 1ms over the air, then you must use specially designed full-duplex systems like AirFiber AF24 which uses a proprietary RF protocol and two simultaneous links between two APs. But those devices are a bit more expensive compared to CPEs.

BTW, the software is called Pharos, it is named after the first lighthouse in history which was Pharos of Alexandria. Yes, I know that even the TP-Link document department writing Pharos user guides isn't aware of this fact.