What Is an Autonomous System Number (ASN)? BGP Routing & Internet Peering Guide

1. What Is an Autonomous System (AS)?

An Autonomous System (AS) is a connected group of IP networks and routers under the administrative control of a single organization (such as an Internet Service Provider, telecommunications carrier, cloud platform, or major financial institution) that presents a unified, consistent interior and exterior routing policy to the internet.

Within its own perimeter, an AS routes internal traffic using Interior Gateway Protocols (IGP) like OSPF (Open Shortest Path First) or IS-IS. Between distinct Autonomous Systems, traffic is routed across the global internet using the Exterior Gateway Protocol known as BGP-4 (Border Gateway Protocol Version 4 - RFC 4271).

2. 16-Bit vs. 32-Bit (4-Octet) ASN Architecture

Originally, ASNs were defined as 16-bit unsigned integers, providing a total pool of 65,536 unique numbers (ranging from ASN 0 to ASN 65535). As thousands of new enterprises and cloud providers joined the internet, the 16-bit space neared exhaustion.

In 2007, RFC 6793 expanded ASNs to 32-bit (4-octet) integers, expanding the total allocation pool to 4,294,967,296 numbers (ASN 0 to 4294967295). Modern BGP routers seamlessly negotiate 4-octet capabilities.

3. Internet Peering vs. IP Transit Relationships

Autonomous Systems connect to one another through two fundamental commercial and architectural arrangements:

1. IP Transit: An AS pays an upstream Tier-1 or Tier-2 provider (such as Lumen, Telia, or NTT) for access to the entire global routing table, allowing traffic to reach any internet destination.

2. Peering (Settlement-Free): Two Autonomous Systems connect directly at an Internet Exchange Point (IXP) or private facility (PNI) to exchange traffic between their respective customers for free, without paying third-party transit fees.

4. BGP Route Hijacking and RPKI Defense

Because BGP was originally designed based on mutual trust, any misconfigured or malicious router can inadvertently announce ownership of an IP prefix belonging to another ASN. This is known as a BGP Route Hijack, and it can misdirect global traffic through rogue networks.

To secure global routing, the internet is adopting Resource Public Key Infrastructure (RPKI - RFC 6480). Under RPKI, the legitimate owner of an IP block publishes a cryptographically signed Route Origin Authorization (ROA) specifying which ASN is authorized to announce the prefix. BGP routers perform Route Origin Validation (ROV), instantly dropping invalid announcements.

5. Practical Commands for ASN Investigation

Inspect which ASN originates an IP prefix or routes your network traffic using standard terminal tools:

# Query WHOIS database for IP allocation and originating ASN
whois -h whois.cymru.com "1.1.1.1"
# Output:
# AS      | IP               | AS Name
# 13335   | 1.1.1.1          | CLOUDFLARENET, US

# Query originating ASN via DNS TXT lookup using Team Cymru IP-to-ASN service
dig +short 1.1.1.1.origin.asn.cymru.com TXT
# Output: "13335 | 1.1.1.0/24 | US | arin | 2011-11-01"

# Traceroute displaying ASNs at every hop along the route (Linux)
traceroute -A 8.8.8.8