Device Support-Lifespan Observatory

What vendors do, not what they announce.

TP-Link

RE300 v2.8

Actively updated reasonably evidenced

firmware is arriving about as often as it always has

107 days since the last release against a median gap of 143 (0.7x)

Sign in to be emailed when this verdict changes.
Last firmware
15 June 2026 (4 months ago)
Releases seen
4
Update rhythm
about every 5 months
Support observed
≥3 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. RE300(US)_V2.8_1.0.50 Build 250916 15 June 2026

    Release notes — disclosure 0.45
    New Features/Enhancement: 1. Added the Ethernet backhaul feature. 2. Added the customizable encryption method option for the extended network. 3. Optimized the device stability.
  2. RE300(US)_V2.8_1.0.13 Build 221216 9 August 2023

    Release notes — disclosure 0.31
    Note: Added the support of EasyMesh.
  3. RE300(US)_V2.8_1.0.23 Build 230418 30 June 2023

    Release notes — disclosure 0.49
    Note: 1. Newly supported EasyMesh function; 2. Enhanced WiFi stability; 3. Fixed the bug that some IoT devices can't connect to 2.4G WiFi.
  4. RE300(US)_V2.8_1.0.12 Build 221019 7 February 2023

    Release notes — disclosure 0.57
    Note: 1. The firmware cannot be downgraded to the previous firmware; 2. Enhanced login password settings and UI notification; 3. Added the support of WPA3 encryption; 4. Fixed wireless related bug and enhanced the wireless stability; 5. Fixed the bug that prompted the app to disconnect after frequently clicking to view various functions on Tether.

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 RE300

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

Machine-readable: JSON · RSS