Madge Ltd. — 4 prefixes (MA-L)

Madge Ltd. (registry org string "Madge Ltd.", registered to Madge House, Maidenhead, Berkshire, GB SL6 2HP — the IEEE record spells the town "Maindenhead", reproduced verbatim as cached) holds four separate MA-L (24-bit OUI) blocks: 00:00:6F, 00:00:C1, 00:80:E9, and 00:02:81. The company traces to Madge Networks N.V., founded in 1986 by Robert Madge and NASDAQ-listed from 1993; it became the dominant non-IBM maker of Token Ring adapters, hubs/MAUs, and switches through the 1990s, and later touched ATM and Ethernet (via its LANNET subsidiary, sold to Lucent in July 1998). Madge Networks filed for bankruptcy in April 2003; the Madge brand and assets were subsequently acquired around 2006 and merged into Network Technology (UK)'s Ringdale division. Devices carrying these prefixes are therefore legacy 1990s–early-2000s Token Ring network hardware, not current production. A critical data trap: the substring "Madge" also matches an entirely unrelated MA-L holder, "MadgeTech, Inc" (AC:E3:48, a data-logger manufacturer in Contoocook, NH, US), which must NOT be merged into this record. A second collision to avoid: the npm JavaScript package named "madge" (CVE-2021-23352, a ReDoS in a dependency-graph tool) is unrelated to Madge Networks and must not be cited as a hardware advisory.

IEEE assignment

4 MA-L prefixes → Madge Ltd. (00:00:6F, 00:00:C1, 00:80:E9, 00:02:81) [Confirmed] — IEEE the IEEE MA-L registry (lines 6468, 22289, 22327, 37442)

Registry / block size

MA-L (24-bit OUI); 4 IEEE prefixes. No MA-M (the IEEE MA-M registry) or OUI-36 (the IEEE MA-S registry) assignment exists for this vendor [Confirmed] — the IEEE MA-L registry, the IEEE MA-M registry, the IEEE MA-S registry. NOTE: IEEE public OUI data publishes NO assignment/registration date (columns are only Registry, Assignment, Organization Name, Organization Address); any "date registered" on third-party tools is a database artifact, not an IEEE fact.

Registry org name

"Madge Ltd." (exact string as printed in the IEEE MA-L registry, including trailing period) [Confirmed] — IEEE the IEEE MA-L registry

HQ / country

Madge House, Maidenhead, Berkshire, GB SL6 2HP (registry text prints "Maindenhead" — likely a typo, reproduced verbatim as cached) [Confirmed] — IEEE the IEEE MA-L registry

Company status

defunct as an independent vendor — Madge Networks N.V. filed for bankruptcy April 2003; brand/assets acquired ~2006 and merged into Network Technology (UK)'s Ringdale division [Confirmed] — en.wikipedia.org/wiki/Madge_Networks, fundinguniverse.com company history

Company history

founded 1986 by Robert Madge; NASDAQ-listed 1993; ~$482M revenue in 1997; acquired Olicom's Token Ring business to become the last major non-IBM Token Ring vendor; sold Ethernet unit LANNET to Lucent July 1998 [Confirmed] — en.wikipedia.org/wiki/Madge_Networks, fundinguniverse.com

Device types

legacy Token Ring network interface cards, hubs/MAUs, and switches (1990s–early 2000s); also ATM products [Likely] — en.wikipedia.org/wiki/Madge_Networks (device-to-OUI mapping is inferential from product line)

Verified prefixes (all MA-L, "Madge Ltd.")

00:00:6F, 00:00:C1, 00:80:E9, 00:02:81 [Confirmed] — IEEE the IEEE MA-L registry

Data trap #1 (entity collision)

AC:E3:48 → "MadgeTech, Inc" (data-logger maker, Contoocook, NH, US 03229) is a DIFFERENT company; do NOT merge into the Madge Ltd. record [Confirmed] — IEEE the IEEE MA-L registry (line 4331)

Data trap #2 (name collision)

the npm package "madge" (CVE-2021-23352, ReDoS) is unrelated to this hardware vendor; not a Madge Ltd. advisory [Confirmed] — acunetix.com CVE-2021-23352 writeup

Security context

no CVE or advisory specific to Madge Token Ring hardware was found [Unknown] — no source located; Token Ring is obsolete/end-of-life industry-wide but no Madge-specific advisory to cite

Analyst note

any of these four OUIs on a globally-administered address identifies genuine legacy Madge Token Ring hardware; the vendor is defunct so expect no firmware/support. Treat "MadgeTech" and the npm "madge" package as separate entities in any lookup or CVE cross-reference.