Cisco Meraki is Cisco's cloud-managed networking division, and its OUI footprint reflects a single-vendor hardware line rather than a sprawling consumer catalog: 57 MA-L (24-bit, large-block) prefixes in the IEEE registry, all assigned to the organization name "Cisco Meraki" rather than "Cisco Systems," even though Cisco acquired Meraki in 2012. Consolidating these 57 blocks into one vendor entry is far more useful than minting near-identical per-prefix pages, because they all point at the same product family. That family is built around cloud management: Wi-Fi access points (MR series), switches (MS series), security appliances and SD-WAN gateways (MX series), smart cameras (MV series), IoT/environmental sensors (MT series), and teleworker/cellular gateways (Z series). Every device depends on persistent connectivity to the Meraki dashboard for configuration, monitoring, and firmware. The practical consequence for network operators: a Cisco Meraki OUI-prefixed MAC on a network strongly signals managed enterprise infrastructure — branch offices, campuses, retail, healthcare, education — not consumer or rogue hardware. One behavior worth flagging for asset classification is BSSID derivation: Meraki access points generate per-SSID/per-radio BSSID MACs algorithmically by incrementing the device's base OUI-registered address, so a single physical AP can present multiple MAC addresses that all trace back to one registered Meraki prefix. The predominant registry address is 500 Terry A. Francois Blvd, San Francisco, CA 94158, with two older prefixes carrying earlier San Francisco addresses, reflecting office moves over time.
- IEEE assignment
- 57 prefixes → Cisco Meraki, registered San Francisco, CA, US [Confirmed] — IEEE MA-L (enrichment/registries/oui.csv)
- Registry / block size
- MA-L (24-bit OUI); all 57 Cisco Meraki blocks are MA-L. No Meraki entries appear in mam.csv (MA-M) or oui36.csv (MA-S). [Confirmed] — IEEE oui.csv / mam.csv / oui36.csv (enrichment/registries/). Third-party aggregator (Netify) also reports 57 prefixes [Likely on the count as an external cross-check] — https://www.netify.ai/resources/macs/brands/meraki. NOTE: IEEE's public OUI data publishes NO assignment/registration date; any "date registered" on third-party tools (e.g. Netify, maclookup.app showing "21 April 2006") is a database artifact, not an IEEE fact.
- HQ / country
- 500 Terry A. Francois Blvd, San Francisco, CA 94158, US (predominant registry address, 55 of 57 prefixes); two earlier addresses on record — 660 Alabama St, San Francisco, CA 94110 (prefix 881544) and 99 Rhode Island St, San Francisco, CA 94103 (prefix 00180A) [Confirmed] — IEEE MA-L (enrichment/registries/oui.csv)
- Company status
- active [Confirmed] — https://meraki.cisco.com/ , https://www.cisco.com/site/us/en/about/corporate-strategy-office/acquisitions/meraki/index.html
- Device types
- cloud-managed Wi-Fi access points (MR), managed switches (MS), security appliances / SD-WAN (MX), smart cameras (MV), IoT/environmental sensors (MT), teleworker/cellular gateways (Z) [Confirmed] — https://meraki.cisco.com/products/ , https://meraki.cisco.com/product-catalog/
- Notable products
- MX security/SD-WAN appliances, MR Wi-Fi access points, MS switches (the full Meraki cloud-managed line)
- Verified sample prefixes (all MA-L, Cisco Meraki)
- 9C:E3:30, B4:DF:91, 00:18:0A, 08:71:1C [Confirmed] — IEEE MA-L (enrichment/registries/oui.csv)
- Corporate history
- Meraki acquired by Cisco in 2012; blocks remain registered under "Cisco Meraki," not "Cisco Systems" [Confirmed] — https://www.cisco.com/site/us/en/about/corporate-strategy-office/acquisitions/meraki/index.html
- Special note
- BSSID derivation — Meraki access points generate per-SSID/per-radio BSSID MAC addresses algorithmically by incrementing the device's base OUI-registered address, so one physical AP can present multiple MACs that all resolve to a single Meraki prefix. [Confirmed] — https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Calculating_Cisco_Meraki_BSSID_MAC_Addresses
- Security context
- Recurring CVEs in the AnyConnect VPN server on MX/Z series — e.g. CVE-2025-20271 (unauthenticated DoS, no user interaction, SSL VPN session establishment) and CVE-2025-20212 (authenticated DoS), both fixed in Meraki MX firmware 18.107.13 / 18.211.6 / 19.1.8; CVE-2024-20509 (AnyConnect VPN server, CVSS 5.8). Separately, CVE-2024-20439/20440 (Cisco Smart Licensing Utility static credential + info disclosure, CVSS 9.8) affected Cisco broadly and were actively exploited from March 2025. Operators with Meraki MX/Z devices should patch firmware and avoid unnecessary internet exposure of AnyConnect VPN surfaces. [Confirmed] — https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-meraki-mx-vpn-dos-by-QWUkqV7X , https://www.securityweek.com/vulnerabilities-expose-cisco-meraki-and-ece-products-to-dos-attacks/
- Related vendors
- Cisco Systems (parent; holds separate registrations under the "Cisco Systems, Inc" name)
- Analyst note
- A Cisco Meraki OUI identifies cloud-managed enterprise hardware that continuously phones home to the Meraki dashboard control plane; its presence on a network is a strong signal of managed enterprise infrastructure (branch, campus, retail, healthcare, education) rather than consumer or rogue devices.