Device Support-Lifespan Observatory

What vendors do, not what they announce.

TP-Link

Archer AX4400 v3.6

Slowing down reasonably evidenced

updates are coming less often than this product's own history

168 days since the last release against a median gap of 98 (1.7x)

Sign in to be emailed when this verdict changes.
Last firmware
14 April 2026 (6 months ago)
Releases seen
3
Update rhythm
about every 3 months
Support observed
≥6 months
Vendor's promise
no support period we can evaluate
Patch latency
not measurable — its changelogs name no CVE ids

Which one do I have?

TP-Link ships this model in more than one hardware revision, and they do not share firmware. The revision is printed on the label on the underside, usually after the model — Ver 1.0, V4.6. Getting it wrong is the easiest way to read the wrong answer here.

Firmware history

  1. Archer AX4400(US)_V3.6_1.4.6 Build 20260112 14 April 2026

    Release notes — disclosure 0.25
    New Features/Enhancements: Enhanced device security and stability. Bug Fixes: Fixed the bug that increases Bufferbloat latency when QoS is enabled.
  2. Archer AX4400(US)_V3.6_1.4.5 Build 20250928 5 November 2025

    Release notes — disclosure 0.53
    New Features/Enhancements: Improved system stability and security. Added support for VPN kill switch feature. Bug Fixes: Fixed the bug that importing an .ovpn file containing specific field parameters would prevent the VPN connection from being established. Fixed the bug that caused intermittent connectivity issues of VPN after the device restarted. Fixed a stability issue that could occur when forming an EasyMesh network with certain models.
  3. Archer AX4400(US)_V3.6_1.3.1 Build 20241119 30 September 2025

    Release notes — disclosure 0.30
    First firmware released.

Evidence

One archived page sits behind this record, the earliest read on 1 August 2026. Everything above was read from it, and each is kept byte for byte so it can be checked after the vendor edits the original.

Identifiers: marketing_name Archer AX4400

Judged by lifecycle-1 on 29 September 2026. How these verdicts are computed.

Machine-readable: JSON · RSS