Firewall and network security appliance hardware end-of-life dates by brand

End-of-sale and end-of-support dates for the physical hardware of firewall and network security appliances (not the OS or firmware version, the box itself), taken from each manufacturer's own hardware lifecycle page. Answers 'when does support end for [model] firewall hardware', the question a network admin planning a refresh needs answered, where the free software-lifecycle aggregators (e.g. endoflife.date) do not cover hardware end-of-support and each vendor's own lifecycle page uses a different format and a different name for the same two dates.

The data

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.

• documentation.meraki.comhttps://documentation.meraki.com/General_Administration/Other_Topics/Meraki_End-of-Life_(EOL)_Products_and_Dates
• paloaltonetworks.comhttps://www.paloaltonetworks.com/services/support/end-of-life-announcements/hardware-end-of-life-dates
• sonicwall.comhttps://www.sonicwall.com/support/product-lifecycle-tables

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 firewall-hardware-end-of-life-dates-by-brand brand="Cisco Meraki"

npx -y refsource lookup firewall-hardware-end-of-life-dates-by-brand brand="Cisco Meraki"

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 "Firewall and network security appliance hardware end-of-life dates by brand", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `firewall-hardware-end-of-life-dates-by-brand`) 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.

93 records. last verified against source 2026-08-26. due for re-check by 2027-02-22.

Licence. factual compilation from manufacturer lifecycle pages