Ubiquiti end-of-life: the vendor that won't commit to a date

The two support stages that exist

• Long Term Support (LTS) — the device still gets critical bug fixes and security updates and stays compatible with stable controller releases. New features arrive only case-by-case. This is the “winding down” phase; plan the replacement here.
• End of Life (EOL) — updates stop. The device keeps running on its current config, but in any UniFi controller released after its EOL date it becomes visible but not configurable — you can see it and forget it, not manage it.

That EOL behaviour is the sting in the tail: an EOL access point doesn't die, but it quietly forces you to freeze your controller version or replace the hardware to keep managing your network. Running an old controller to keep one AP alive is its own security liability.

Why Ubiquiti is uniquely hard to track

Enterprise vendors like Cisco and Aruba publish a product's key dates years ahead. Ubiquiti deliberately doesn't: it commits to no fixed number of years, and EOL is often triggered reactively when a chip vendor stops supporting the silicon. That keeps hardware cheap, but it means you cannot look up “when does my UniFi AP go EOL” in advance — the announcement lands in a firmware release note, and if you miss it, the first sign is a controller update that won't manage your device.

How to actually stay ahead of it

1. Watch firmware status per device. Ubiquiti signals LTS and EOL through firmware release notes and its community/help site, not a single formal index. Note which of your models have slipped to LTS.

2. Treat “LTS” as your warning. The moment a device is in LTS, put it on the replacement plan — that's the only lead time Ubiquiti gives you.

3. Record it somewhere that watches. Since there's no published date to rely on, log each device's status the day you learn it and set your own review reminder — because Ubiquiti won't send you one.