An autonomous system number, or ASN, identifies a network or group of networks that presents a common routing policy to other networks. Routers use ASNs when exchanging information about how to reach IP address ranges. If an IP lookup lists an ASN beside your address, the number identifies an autonomous system associated with the address, not the person using it.

ASNs appear in routing records, network diagnostics, and IP lookup results. An AS organization field labels the organization associated with that number in the lookup service's data. Understanding that role helps you distinguish the network carrying traffic from the organization registered for an address block or the provider named on a customer's bill.

Autonomous Systems and Routing

The internet connects networks operated by internet providers, hosting companies, universities, and other organizations. An autonomous system, or AS, groups networks that follow a consistent policy for exchanging routes with other ASes. Border Gateway Protocol (BGP) carries information about which IP address ranges are reachable and the AS paths associated with those routes.

An IP prefix identifies an address range, while an ASN identifies an autonomous system. An AS can originate a route for a prefix and advertise routes learned from other networks, according to its routing policy. The AS that first announces a prefix into BGP is described as that route's origin AS. A transit AS helps carry traffic between networks. Confusing those roles can make an intermediate provider look like the organization responsible for the destination.

A BGP AS path records autonomous systems through which routing information has passed. Routers use that information to help detect routing loops and apply routing policies. The path is part of a route announcement, rather than a list of every device a packet visits. A lookup that shows one ASN for an IP address is therefore giving a different kind of result from a complete AS path.

One organization can operate several autonomous systems, and one AS can announce many address ranges. The organization may separate parts of its network for different routing policies or retain several ASNs after acquiring another business. A large network can also use several transit providers. The relationship between company names and ASNs is therefore not always one company to one number.

Public, Private, and Reserved ASNs

ASNs were originally represented with 16 bits, and the number space was later expanded to 32 bits to support more autonomous systems. A 16-bit ASN still represents the same number within the expanded space. In ordinary text, an ASN is often written with an AS prefix followed by decimal digits, such as AS64496. That particular value is reserved for documentation, so the example does not identify a live network.

IANA coordinates the global ASN number space and allocates blocks to regional internet registries. Those registries manage assignments within their service regions and publish registration information. A public ASN assignment identifies the organization responsible for that number. Receiving an ASN does not, by itself, provide an IP address block. Address resources and ASNs have separate registration records.

Some ASNs are reserved for private routing arrangements rather than globally unique public assignments. The private-use ranges are 64512–65534 and 4200000000–4294967294. Unrelated networks may use the same private ASN within their own arrangements, so the number alone cannot identify one organization worldwide. Private-use values and documentation values serve different purposes and should not be treated as ordinary public ASN assignments.

Reading an ASN Lookup Result

Suppose an IP lookup displays an address, an ASN, and an AS organization name. The ASN usually comes from the service's association between the address range and an autonomous system, often using routing data. The organization name describes the entity associated with that ASN in the dataset. Separate ISP or organization fields may describe different relationships, so read their definitions before expecting every name to match.

You can compare those fields with a regional internet registry's RDAP or Whois records. Searching an ASN returns information about the registered number and its associated organization; searching an IP address returns information about an address block. Follow a referral to the responsible registry when the first service does not hold the relevant record. A registration result and an observed BGP route answer related but different questions.

Check the address range covered by the result as well as the queried address. Routing data may include both a broad prefix and a more specific prefix covering that address. An IP-to-ASN service's choice of data and matching rules can affect which association it reports. A registry's parent allocation, a customer's assigned block, and a prefix seen in BGP need not have identical boundaries.

Also check what the source and date describe. A registry's last-change date records an update to that entry, while a routing observation describes information seen at a particular time and location in the network. A database may be incomplete or lag a routing change. A fresh lookup does not guarantee that its underlying records were refreshed at that moment.

Why an ASN Does Not Identify a Subscriber

Many customers, devices, and services can use addresses announced through one AS. A home connection may use addresses routed by an ISP, while a website uses addresses routed by a hosting network. If a browser request passes through a VPN, a lookup may report the autonomous system associated with the VPN's exit address. An ASN alone does not identify the individual who made a request.

The AS organization also need not be the registered holder of the IP block. Routing may be handled by a hosting operator, a downstream customer, or another provider under an agreement with the holder. Compare address registration with current routing evidence when deciding which organization is responsible for a particular network role. Using a single company-name field as the answer can conceal those separate responsibilities.

An ASN can help group related network observations, but that grouping is broader than a customer account or device. For example, blocking an entire ASN can affect unrelated customers and services that use its networks. When a problem concerns one address or connection, identify the affected resource before extending a conclusion to every address associated with the same ASN.