Device Support-Lifespan Observatory

What vendors do, not what they announce.

TP-Link

RE700X v1.8

Gone quiet reasonably evidenced

no firmware for long enough to stand out against its own record

750 days since the last release against a median gap of 195 (3.8x)

Sign in to be emailed when this verdict changes.
Last firmware
9 September 2024 (2 years ago)
Releases seen
4
Update rhythm
about every 6 months
Support observed
≥2 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. RE700X(US)_V1.8_1.1.9 Build 20240426 9 September 2024

    Release notes — disclosure 0.40
    Note: 1. Added EasyMesh display on the Tether APP; 2. Enhanced system stability.
  2. RE700X(US)_V1.8_1.1.7 Build 20230721 18 October 2023

    Release notes — disclosure 0.50
    Note: 1. Optimized EasyMesh function; 2. Enhanced WiFi stability; 3. Fixed the bug that client list doesn't display link speed of wired client; 4. Optimized WPS function.
  3. RE700X(US)_V1.8_1.1.6 Build 20230307 6 April 2023

    Release notes — disclosure 0.57
    Note: 1. Optimized the networking configuration process; 2. Optimized the web management page display; 3. Added the support of customizing password and encryption type for extended network; 4. Optimized the methods to login the web management page; 5. Fixed the bug that the devices behind RE have no network in some cases.
  4. RE700X(US)_V1.8_1.1.5 Build 20221108 27 December 2022

    Release notes — disclosure 0.43
    Note: 1. Newly support EasyMesh; 2. Enhanced WiFi stability; 3. Optimized the system stability.

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 RE700X

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

Machine-readable: JSON · RSS