Setup: AmpliFi Alien (AFi-ALN-R), SW 4.0.8, HW rev 10, AP mode (bridge, not routing), wired uplink to a separate router. Not doing NAT/PPPoE, upstream is confirmed healthy through every single crash.

Symptom: The Alien intermittently stops broadcasting WiFi entirely (SSID vanishes from active scans) and, in the more severe failure mode, the wired LAN bridge and even the local management Web UI (login.php) go unresponsive at the same time. The device's own LCD/app telemetry keeps reporting "everything is great" (90%+ WiFi health, full green history, connected client counts) throughout the outage, so there's no way to detect the failure from the device's own reporting. Only an external monitor (WiFi scan + gateway ping from another device) catches it.

Scale of the problem: 28 documented crashes since July, with full timestamped telemetry (2-10 second to 2-minute polling resolution depending on period). Time-to-crash has been trending down, started around ~107 hours between crashes, dropped through a 27-42h band, briefly hit 16-18h, and is currently holding in a 20-39h range. A handful of crashes have self-recovered (device reboots itself, uptime resets, nobody touches power) but most require a manual power cycle, the recovery behavior itself is inconsistent and I haven't found a trigger pattern.

What I've ruled out:

• Upstream router/ISP: stays fully functional through every crash (independently verified via a second WiFi network in the house)
• - Cable fault: no PHY-level link flapping before failures begin; failures build gradually over hours then resolve instantly on power cycle, which a bad cable doesn't do
• - A stale mesh point entry in my config: tracked its connection attempts separately; crashes occur on the same timescale whether or not it's attempting to connect
• - App's own "Restart" command: tried it during an active crash, no effect (routes through the same locked-up local management stack)

Support ticket status: I've had ticket #392992 open with AmpliFi support since July, with pretty extensive back-and-forth. The agent was engaged early on and asked good technical questions, including asking me to capture a support file at the moment of failure. Turns out that's not possible with the current failure mode: the local Web UI itself becomes unreachable at the same moment as the WiFi radio, so there's no way to authenticate and pull a support file during the event. I explained this but haven't had a reply in about 3 weeks despite several follow-up updates with new crash data in the meantime.

I also found an older locked thread here from michal.uryga (AmpliFi Alien Wi-Fi Radio Failure) with the same complete-radio-loss symptom, where at least two other users (JasonMcG, TLW2) confirmed the same failure on their own Alien units, and multiple people reported official support going unresponsive for weeks. So this doesn't look like an isolated unit problem.

Questions for anyone else here:

1. Has anyone else on SW 4.0.8 (or later) seen the WiFi radio and local Web UI go dark simultaneously like this?
2. 2. Is there a known resource/memory leak in this firmware line? The degradation pattern (gradual, uptime-correlated, resolves instantly on power cycle) points strongly at a leak rather than anything environmental.
3. 3. Is there any way to get diagnostic/crash data off the device when it's in this locked-up state, serial console, recovery mode, anything? The local API keeps returning cached "healthy" values so there's nothing to pull through normal channels.
4. 4. Since Alien is EOL, is there a current UI product anyone would recommend for a stable AP-mode deployment behind an existing router?

Happy to share the full CSV telemetry or any specific crash window if it's useful to anyone debugging a similar issue.

Also tagging @UI-Team

What makes it worse is that devices in the list can only be edited (renamed, icon changed) while online. So all these old devices clutter up the list, without even the ability to add 'OLD' to their name or change their icon to something representing dead devices.

How can I clear the list of old, unused devices? (Without having to reset the entire router! That's no solution, not even a decent workarond, as this keeps happening throughout the router's lifetime, and requires reconfiguring the router after each reset.)

It is running the last released firmware update version 2.9.3, revision 0-g0041666d5d. App version 1.25.0 (2) @UI-Team

A good physics tutor begins by assessing the student's current understanding of key topics such as mechanics, electricity, magnetism, waves, thermal physics, and modern physics. Once learning gaps are identified, each lesson is tailored to strengthen concepts through clear explanations, worked examples, and regular practice.

Another important part of exam preparation is solving past papers. Tutors teach students how to interpret questions, apply the correct formulas, show working clearly, and avoid common mistakes that lead to lost marks. They also provide feedback based on the exam marking scheme, helping students improve both accuracy and time management.

Many tutors include regular revision sessions and mock exams to build confidence before the final assessment. These sessions help students become familiar with the exam format while improving problem-solving and critical-thinking skills under timed conditions.

At Mixt Academy, experienced tutors provide personalised one-to-one Physics tuition in dubai for students studying GCSE, IGCSE, A-Level, IB, AP, and other international curricula. Lessons are designed to strengthen conceptual understanding, improve calculation skills, and prepare students for excellent exam performance.

With consistent guidance, structured revision, and expert support, students can approach their Physics exams with greater confidence and achieve the grades they are aiming for.

`

sudo tcpdump -i itf0 -e vlan

`

I notice a lot of traffic on VLAN 4094..... multiple packets per second actually I swcided to disable that checkbox

`

19:51:27.297895 6c:0b:84:21:67:7a (oui Unknown) > 74:ac:b9:a7:6b:8a (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 4094, p 0

, ethertype IPv4, putin_lenovo.34934 > routerx.soul.ssh: Flags [.], ack 522704036, win 314, options [nop,nop,TS val 1221228014 ecr 2542

946687], length 0

19:51:27.297903 6c:0b:84:21:67:7a (oui Unknown) > 74:ac:b9:a7:6b:8a (oui Unknown), ethertype 802.1Q (0x8100), length 106: vlan 4094, p

0, ethertype IPv4, putin_lenovo.34934 > routerx.soul.ssh: Flags [P.], seq 352545:352581, ack 522704036, win 314, options [nop,nop,TS va

l 1221228014 ecr 2542946687], length 36

19:51:27.297907 6c:0b:84:21:67:7a (oui Unknown) > 74:ac:b9:a7:6b:8a (oui Unknown), ethertype 802.1Q (0x8100), length 70: vlan 4094, p 0

, ethertype IPv4, putin_lenovo.34934 > routerx.soul.ssh: Flags [.], ack 522705372, win 314, options [nop,nop,TS val 1221228015 ecr 2542

946687], length 0

19:51:27.298584 74:ac:b9:a7:6b:8a (oui Unknown) > 6c:0b:84:21:67:7a (oui Unknown), ethertype 802.1Q (0x8100), length 426: vlan 4094, p

0, ethertype IPv4, routerx.soul.ssh > putin_lenovo.34934: Flags [P.], seq 522707020:522707376, ack 352581, win 1526, options [nop,nop,T

S val 2542946689 ecr 1221228015], length 356

19:51:27.298858 74:ac:b9:a7:6b:8a (oui Unknown) > 6c:0b:84:21:67:7a (oui Unknown), ethertype 802.1Q (0x8100), length 426: vlan 4094, p

0, ethertype IPv4, routerx.soul.ssh > putin_lenovo.34934: Flags [P.], seq 522707376:522707732, ack 352581, win 1526, options [nop,nop,T

S val 2542946690 ecr 1221228015], length 356

19:51:27.299117 74:ac:b9:a7:6b:8a (oui Unknown) > 6c:0b:84:21:67:7a (oui Unknown), ethertype 802.1Q (0x8100), length 426: vlan 4094, p

0, ethertype IPv4, routerx.soul.ssh > putin_lenovo.34934: Flags [P.], seq 522707732:522708088, ack 352581, win 1526, options [nop,nop,T

S val 2542946690 ecr 1221228015], length 356

19:51:27.299436 74:ac:b9:a7:6b:8a (oui Unknown) > 6c:0b:84:21:67:7a (oui Unknown), ethertype 802.1Q (0x8100), length 426: vlan 4094, p

0, ethertype IPv4, routerx.soul.ssh > putin_lenovo.34934: Flags [P.], seq 522708088:522708444, ack 352581, win 1526, options [nop,nop,T

S val 2542946690 ecr 1221228015], length 356

^C19:51:27.299744 74:ac:b9:a7:6b:8a (oui Unknown) > 6c:0b:84:21:67:7a (oui Unknown), ethertype 802.1Q (0x8100), length 706: vlan 4094,

p 0, ethertype IPv4, routerx.soul.ssh > putin_lenovo.34934: Flags [P.], seq 522708444:522709080, ack 352581, win 1526, options [nop,nop

,TS val 2542946691 ecr 1221228015], length 636

`

I reckon if I reboot the router it will calm down since i only just disabled "VLAN aware".

Should I expect this traffic to subside shortly?

PS putin is my workstation, connected vu SSH to routerx running tcpdump remotely

I’m trying to add an extra AmpliFi HD unit to my existing network and I’m stuck.

My current AmpliFi HD kit is working fine. I also already added a mesh point to it successfully, and that is working with no issue. The problem is only with this additional unit I’m trying to add now.

The app does detect the new unit, but during setup it stops and says I need to make sure the new kit is up to date. I already checked that, and it also tells me to contact AmpliFi support for help.

Here are the device details:

Existing working unit

• AmpliFi Router HD
• Hardware ID: 21
• Firmware: 4.0.3
• Revision: 0-g0bc740d76d

New unit I’m trying to add

• AmpliFi Router HD
• Hardware ID: 22
• Firmware: 4.0.3

So basically:

• Existing kit works fine
• Existing mesh point works fine
• New unit is detected
• But it will not join the network and keeps showing the update/support message

Has anyone seen this before?

I’m mainly trying to figure out:

• Did anyone need AmpliFi support to do something from their side to allow the unit to connect?
• Any issue with Hardware ID 21 and 22 working together?
• is it country code? Where do I find that? All my devices purchased from USA

Would appreciate any advice from someone who has dealt with this.

Pero el problema es que algunos clientes están conectados, pero otros no tienen acceso a Internet. Por ejemplo, tenemos algunos moviles y uno tiene conexión a Internet y el otro no. Tengo dispositivos que controlan las persianas que si se conectan.

He revisado la configuración del router Huawei, pero no encuentro nada que indique que esto pueda ser un problema.

He probado diferentes configuraciones, como tener solo una subred y deshabilitar las demás. Intenté deshabilitar IPv6, pero no parece desactivarse por completo.

No entiendo por qué algunos dispositivos funcionan y otros no se conectan a Internet.

Tried many things from reset / factory reset, new installation etc.. nothing works. The device is configurable with the Amplifi App,

config visible etc. but the SSID does not show in the network list. And it is NOT set to hidden. HW ID = 10, FW 4.08, All devices updated. Even if the App connects to the device after a test installation etc..... the SSID is not visible.

I would like to bring back everything to normal on the old SSD to make my Smart Stuff to reconnect.

Has anyone any idea ?

When a device is connected to the wireless mesh point the connection speed is so slow it's unusable, about 5 Mbps down (screen shot attached)

. The mesh point shows "Perfect" signal strength in the Amplifi app (screen shot attached) and the lights on the outside of the mesh point show full signal strength for the connection to the router.

Things I have already tried, none of these resulted in any improvement

• Physically moving the mesh point 10 ft closer/farther to/from the router
• Disabling Band Steering
• Using 2.4 GHz backbone connection on the meshpoint

I also reached out via email to the Amplifi support team, and got a completely unhelpful response which I've quoted below:

"The main objective of the mesh point is to improve the coverage and not speed. The speeds that you will be getting from the mesh points, which are paired with the main router, will always be less than the main router. Additionally, if you notice that speeds are better when closer to the router but slower when further away, then that could be caused because of low signal."

I can't accept that it's normal for the connection through the mesh point to be 60x slower than the router.

Hoping the community has some helpful configuration suggestions or troubleshooting steps

Thanks!

I am posting here as a last attempt to receive any official response regarding my AmpliFi Alien unit.

My device has developed a recurring and now permanent failure of the Wi-Fi radio. The router powers on, Ethernet switching functions normally, but it completely stops broadcasting any wireless SSID (2.4 GHz / 5 GHz). The unit becomes effectively unusable as a Wi-Fi router.

This issue first appeared while the device was still under warranty (first week of the usage). At that time, the only suggested troubleshooting steps were:

• Enabling additional SSIDs
• Power cycling the router
• Disconnecting it from power and reconnecting

No explanation was given as to why it happened, nor was there any information on how to solve/structurally fix it.

Those steps temporarily restored the Wi-Fi signal, but the issue kept recurring multiple times.

Now the same problem has returned, and none of the previously suggested actions resolve it. The Wi-Fi radio no longer broadcasts at all.

Look at the movie I recorded:

• What is particularly concerning:
• On the official Ubiquiti website, it states that AmpliFi products are no longer handled there. Support told me to go to the AmpliFi webpage, but the support there is no longer available.
• The AmpliFi support forum appears inactive.
• Multiple posts and attempts to request assistance have gone unanswered.
• 
  

This device was marketed as a premium Wi-Fi 6 router, and complete loss of wireless functionality after recurring radio failures suggests a hardware defect.

I would appreciate a formal response from AmpliFi / Ubiquiti representatives.

Thanks you.

Attachments:

• AmpliFi issue.mp4

 Built this in Go with full Grafana dashboard. Tracks WAN stats, all connected devices, WiFi signal strength, Ethernet ports, connection history.

 Docker images for amd64/arm64/armv7, multi-platform binaries, unit tests.

github - tazhate/amplifi-hd-exporter

 Been running it for a while, works solid. If you have AmpliFi HD + Prometheus, give it a shot.

Error: “Unsupported device configuration”.

Opened tickets twice:

- Ticket #XXXXXX

- Ticket #YYYYYY

MeshPoints enter pairing mode but never adopt.

Firmware current, factory reset performed.

No Ethernet available (wireless mesh only).

Can an AmpliFi engineer confirm:

• whether HD routers from kits are restricted

• or whether controller state must be cleared / unit replaced?

After hours of trying I do now have the main router up again but can' connect to my meshpoint anymore. Not even trying the other router at this point.

I did factory reset the other router as well, but then I run into to the factory pairing issue, therefor I can't just change the router I have.

Any suggestions?

Ticket for support was opened as well.

AMPLIFI ALIEN

for the past two weeks, my router has been RESTARTING itself several times a week. So far (over two years), it's been working fine…

Does Anyone know a solution to this problem?