RegistryReviewed September 2026 · ASN probe 2026-09-06

Mobile Carrier & ASN Registry

134 mobile operators in 44 countries, each with the autonomous system numbers that route its traffic, the MCC/MNC codes that identify it on the radio network, and the prefixes each ASN announced when the probe last ran. Every value links to RIPEstat, PeeringDB or the operator.

134
carriers
44
countries
455
ASNs, RIPEstat-confirmed
133,173
announced prefixes

By country

Each country page lists its operators with ASNs, MCC/MNC codes and a prefix summary.

By parent group

Groups that own operators in more than one country in this registry.

Method

  1. Operators are the ones named on this site's country pages. For each, a researcher located the official website, the parent group where a source states one, and the MCC/MNC rows in a public network code table, recording a URL for each value.
  2. Candidate ASNs came from the RIPE NCC's ASN name list. Each was checked against PeeringDB or RIPEstat and marked confirmed only when the record names the operator; otherwise it is marked as a name match only.
  3. A script then queried RIPEstat for every listed ASN: holder name, whether it is announced, and the count of announced IPv4 and IPv6 prefixes. ASNs with no RIPEstat holder were dropped.
  4. Roles (mobile, fixed, enterprise) are recorded only when PeeringDB or the operator documents them; the rest are marked as not documented.

This registry is a reference for classifying traffic and understanding carrier address space. It does not list individual IP addresses and it changes nothing about how any network behaves.

Questions

What is the carrier and ASN registry?

A read-only reference of 134 mobile network operators in 44 countries. Each entry lists the operator's autonomous system numbers (ASNs), which network each ASN carries where public records say so, the MCC/MNC codes that identify the operator on the mobile network, and the number of IPv4 and IPv6 prefixes each ASN announced when the registry probe last ran. Reviewed September 2026.

Where does the data come from?

Three places, and every row names its source. ASN holder names and announced prefix counts come from the RIPE NCC's RIPEstat Data API, fetched by a script on 2026-09-06. Network records come from PeeringDB where the operator has one. Carrier identity, parent group and MCC/MNC codes come from the operator's own site or a public network code table, with the URL beside each value. An ASN with no RIPEstat holder is not listed.

What does an ASN tell me about a mobile IP?

Every public IP address is announced by an autonomous system. Looking up the ASN of an address tells you which organisation routes it, so an address inside Verizon Wireless or Vodafone UK ASN space is carrier space. Fraud, ad-verification and analytics systems use exactly this lookup to classify traffic as mobile, residential or datacenter.

Why do some carriers list several ASNs?

Large operators run separate networks for consumer mobile, fixed broadband, enterprise and transit, often under different ASNs acquired through mergers. The registry marks the role of each ASN where PeeringDB or the operator documents it and marks the rest as role not documented rather than guessing.

Is the dataset free to use?

Yes. The full registry is published as an open dataset under CC BY 4.0, downloadable as CSV, NDJSON or JSON, with citation blocks on the dataset page.

Crawler & Bot Registry
AI crawlers and search bots with user agents and IP ranges.
Anti-Bot Registry
Bot-protection vendors observed on popular sites.
Research & open datasets
All datasets published by PROXIES.SX.