Device Support-Lifespan Observatory

What vendors do, not what they announce.

TP-Link

Archer A54 v1

Slowing down reasonably evidenced

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

701 days since the last release against a median gap of 376 (1.9x)

Sign in to be emailed when this verdict changes.
Last firmware
28 October 2024 (2 years ago)
Releases seen
4
Update rhythm
about every 1 year
Support observed
≥4 years
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 A54(US)_V1_240816 28 October 2024

    Release notes — disclosure 0.40
    Modifications and Improvement: 1. Optimized wireless performance of the device. 2. Improved stability of the device. 3. Enhanced security of the device.
  2. Archer A54(US)_V1_230810 18 October 2023

    Release notes — disclosure 0.34
    Note: Enhanced device stability. Improved device security. Fixed the bug that caused time synchronization to fail in specific environments.
  3. Archer A54(US)_V1_211108 9 February 2022

    Release notes — disclosure 0.35
    Modifications and Bug Fixes: 1. Fixed some security vulnerabilities, enhanced system safety. 2. Optimized IPv6 module.
  4. Archer A54(US)_V1_21011 4 February 2021

    Release notes — disclosure 0.45
    Modifications and Bug Fixes 1. Added WPA3 on Router mode and AP mode. 2. Optimized the wireless cinnection stability. 3. Enhanced device security.

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 A54

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

Machine-readable: JSON · RSS