A10 Networks — 00:1F:A0 (MA-L)
Summary
- // what this is
- A10 Networks is registered to MAC prefix
00:1F:A0in the IEEE OUI database. When a device's MAC address begins with00:1F:A0, that block was registered by A10 Networks — the OUI identifies the maker of the network hardware, which is not always the brand on the device. - // analyst note
- A 00:1F:A0 globally-administered MAC identifies genuine A10 networking hardware (not a consumer endpoint); given the CVE profile, treat a sighting as a cue to verify patch level and management-plane exposure.
About this vendor.
The OUI prefix 00:1F:A0 is registered to A10 Networks, the San Jose application-networking vendor (NYSE: ATEN), at the registry address 3 West Plumeria Drive, San Jose, CA 95134. It is a single MA-L (24-bit) block — the registry's largest assignment class, roughly 16.7M addresses — and the IEEE data shows no other A10 prefixes in the MA-M (the IEEE MA-M registry) or MA-S (the IEEE MA-S registry) tiers, so this one block carries the vendor's entire OUI footprint. A10 ships physical network appliances rather than consumer gear: the Thunder line (Thunder ADC application delivery controllers, Thunder CGN carrier-grade NAT, Thunder CFW convergent firewall) plus the earlier AX/EX/ID series, used for load balancing, DDoS mitigation, SSL/TLS offload and inspection, and CGNAT/IPv6 migration at enterprise and service-provider scale. For a network defender the security context is meaningful: these appliances sit at the network edge or core, and A10's ACOS management plane has documented CVEs including authenticated command injection and remote code execution (CVE-2024-30368 / CVE-2024-30369) plus IPMI/LoM weaknesses on the physical hardware — a 00:1F:A0 MAC on a network reliably flags a high-value piece of A10 infrastructure, not an endpoint. Note the data-quality trap common to OUI lookups: third-party tools (e.g. maclookup.app) show a "2008-01-20" registration date for this block, but IEEE publishes no OUI assignment dates; that figure is a database artifact and must not be presented as an IEEE fact.
- IEEE assignment
- 00:1F:A0 → A10 Networks, registered San Jose, CA, US [Confirmed] — IEEE MA-L
- Registry / block size
- MA-L (24-bit OUI, ~16.77M addresses); single block, the vendor's only IEEE prefix [Confirmed] — IEEE the IEEE MA-L registry; not present in the IEEE MA-M registry (MA-M) or the IEEE MA-S registry (MA-S)
- HQ / country
- 3 West Plumeria Drive, San Jose, CA 95134, US (registry address; corporate HQ also San Jose, CA) [Confirmed] — IEEE MA-L / en.wikipedia.org/wiki/A10_Networks
- Company status
- active; publicly traded (NYSE: ATEN), IPO March 21, 2014; founded 2004 by Lee Chen [Confirmed] — a10networks.com, en.wikipedia.org/wiki/A10_Networks
- Device types
- physical network appliances — Thunder ADC (application delivery controllers), Thunder CGN (carrier-grade NAT), Thunder CFW (convergent firewall); legacy AX / EX / ID series; also software and cloud-native ADC [Confirmed] — a10networks.com
- Primary use context
- enterprise and service-provider infrastructure — load balancing, DDoS mitigation, SSL/TLS offload and inspection, CGNAT/IPv6 migration, WAF/API security; telecom, financial, government, healthcare, education sectors [Confirmed] — a10networks.com, gartner.com/reviews
- Security note
- ACOS / Thunder management plane has documented CVEs — authenticated command injection and RCE / privilege escalation (CVE-2024-30368, CVE-2024-30369) and IPMI/LoM vulnerabilities on physical appliances; these units sit at edge/core, so a compromise can affect large traffic volumes[Confirmed] — support.a10networks.com security advisories, cvedetails.com
- No-date caveat
- third-party tools list a "2008-01-20" registration date; IEEE publishes NO OUI assignment dates (the IEEE MA-L registry columns are only Registry, Assignment, Organization Name, Organization Address). Treat any such date as a database artifact, never an IEEE fact.[Confirmed] — IEEE the IEEE MA-L registry schema
- Analyst note
- a 00:1F:A0 globally-administered MAC reliably identifies genuine A10 networking hardware (not a consumer endpoint); given the security profile, finding one on a network is a signal to confirm patch level and management-plane exposure.