941 records

Is my router, extender or adapter still getting firmware updates?

941 records, one fact each. Every value is transcribed from the source that states it and carries the sentence it was taken from: 3 sources across 3 sites, last checked 2026-09-24, due for re-check by 2026-12-23. Every record has a page of its own, quoting the line that states it.

About this data

End-of-life and end-of-support dates for home networking hardware, each read off the vendor's own EOL list and quoted from it. Counted 2026-09-16 across the 987 published records: TP-Link 649 (from TP-Link's dated Home EOL list, which prints an announcement date and an end-of-support date per model and regional SKU) and ASUS 335 (from ASUS's networking EOL page, which prints membership of the end-of-life list and no dates at all), plus three Linksys rows that are software features rather than models — see _curator_2026_09_16. TWO THINGS THIS DOES NOT COVER, both of which the description claimed until 2026-09-16. NETGEAR: no records. Its consumer end-of-service list is a JavaScript model lookup that still returns 'No end of service results found' to a fetcher (re-tested 2026-09-16), and the enterprise EOL PDF its own notes point at downloads to an empty file, so there is nothing here for a NETGEAR owner and the page should not imply there is. Routers only: no. About 600 of the 987 (61%) are routers or mesh systems; the rest are range extenders, USB and PCIe Wi-Fi adapters, powerline kits, a handful of cable modems, access points, a USB hub and a print server — all of them on the vendors' own home-network EOL lists, so they belong here, but a title promising routers alone was describing three fifths of the asset. Answers 'is my TP-Link Archer C2600 still getting security updates', which nobody else has assembled: endoflife.date's device category is 20 consumer phones and tablets with zero router vendors (verified in the 2026-08-10 eol-recon), and the enterprise-gear niche is occupied by refurb resellers.

The data

Showing the first 400 of 941 records. Every record has its own page, with its source and the quoted line that states it; these list the rest.

• Records 1–4004G-AC53U … DSL-N17U
• Records 401–800DSL-N55U A1 (Annex A) … TL-WN851ND 1.0
• Records 801–941TL-WN881ND 1.0 … ZenWiFi XT9 (only EU)

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 3 sources this dataset was assembled from.

• asus.comhttps://www.asus.com/event/network/eol-product/
• static.tp-link.comhttps://static.tp-link.com/upload/manual/2026/202606/20260624/US%20EOL_List_Home%20-%20V8.1.pdf
• linksys.comhttps://www.linksys.com/pages/linksys-product-end-of-life

Machine-readable

• data.jsonThe whole dataset — every record with its source URL and source quote.
• Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
• data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
• How this is made and checkedWhat "verified against source" does and does not mean.

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup router-firmware-support-status vendor=ASUS

npx -y refsource lookup router-firmware-support-status vendor=ASUS

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "TP-Link and ASUS routers and network gear — end-of-life and end-of-support dates by model", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `router-firmware-support-status`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

941 records. last verified against source 2026-09-24. due for re-check by 2026-12-23.

Licence. Facts (dates, model status) cited and quoted from each vendor's own published EOL list with attribution; no compilation reproduced beyond the facts.