What is an Autonomous System (AS)?

Share This Article

Updated on July 22, 2025

An Autonomous System (AS) is a collection of interconnected Internet Protocol (IP) networks and routers under the control of a single administrative entity. This entity presents a common, clearly defined routing policy to the internet. Each AS receives a globally unique identifier called an Autonomous System Number (ASN).

Think of an AS as a distinct routing domain with its own rules and policies. Major internet service providers, large corporations, universities, and government agencies typically operate their own Autonomous Systems. This structure enables the internet to scale efficiently by breaking the global routing problem into manageable, independent units.

JumpCloud

JumpCloud’s simplified Cloud RADIUS solution gives you all the benefits of RADIUS with none of the traditional hassle.

Definition and Core Concepts

Single Administrative Entity

Every AS operates under unified control. A single organization makes all routing decisions within that system. This centralized management ensures consistent policies and prevents conflicting routing decisions that could disrupt traffic flow.

The administrative entity could be an Internet Service Provider (ISP), a multinational corporation, a university, or a government agency. Regardless of the organization type, they maintain complete authority over their AS routing policies.

Unified Routing Policy

An AS operates under a consistent set of rules for routing traffic. These policies determine how the system will send and receive data from other Autonomous Systems. Organizations can implement specific routing behaviors based on cost, performance, security, or business relationships.

Policy decisions might include preferring certain network paths, accepting or rejecting routes from specific sources, or implementing traffic engineering to optimize performance. These choices remain internal to the AS and invisible to external systems.

Autonomous System Number (ASN)

Each AS receives a globally unique identifier called an Autonomous System Number. ASNs come in two formats: 16-bit numbers (ranging from 1 to 65,535) and 32-bit numbers (ranging from 1 to 4,294,967,295). The Internet Assigned Numbers Authority (IANA) manages global ASN allocation, while Regional Internet Registries (RIRs) assign them within specific geographic regions.

ASNs serve as crucial identifiers in routing protocols, particularly the Border Gateway Protocol (BGP). They help prevent routing loops and enable policy application between different systems.

Public vs. Private ASNs

Public ASNs are globally unique and used for internet routing. These numbers must be obtained from an RIR and are visible to the entire internet. Private ASNs are reserved for internal use within organizations and are not advertised to the global internet.

Private ASNs include specific ranges: 64,512 to 65,534 for 16-bit numbers and 4,200,000,000 to 4,294,967,294 for 32-bit numbers. Organizations use private ASNs for internal network segmentation without requiring globally unique identifiers.

IP Address Space

An AS controls specific ranges or blocks of IP addresses called IP prefixes. These prefixes represent the network addresses that the AS can route traffic to and from. For example, an AS might control the IP prefix 192.168.1.0/24, which includes all addresses from 192.168.1.1 to 192.168.1.254.

The relationship between AS ownership and IP address space is fundamental to internet routing. When an AS advertises a route, it’s essentially telling other systems, “I can deliver traffic to this specific IP address range.”

How Autonomous Systems Work

Internal Routing (IGP)

Routers within an AS use Interior Gateway Protocols (IGPs) to exchange routing information and maintain internal routing tables. Common IGPs include Open Shortest Path First (OSPF), Enhanced Interior Gateway Routing Protocol (EIGRP), and Intermediate System to Intermediate System (IS-IS).

Internal routing decisions remain completely invisible to outside Autonomous Systems. This isolation allows organizations to modify their internal network structure without affecting external routing or requiring coordination with other systems.

IGPs focus on finding the best path within the AS based on metrics like hop count, bandwidth, delay, or administrative preferences. These protocols automatically adapt to network changes and maintain optimal routing within the system.

External Routing (BGP)

The Border Gateway Protocol (BGP) serves as the standard and only widely used Exterior Gateway Protocol (EGP) for routing between Autonomous Systems. BGP speakers—specialized routers at the edge of an AS—exchange routing information with BGP speakers in other systems.

BGP advertisements include IP prefixes and their associated AS paths. The AS path shows which Autonomous Systems a route has traversed, helping prevent routing loops and enabling policy application. When a BGP speaker receives a route advertisement, it can accept, reject, or modify the route based on local policies.

BGP operates as a path-vector protocol, meaning routers exchange full path information to destinations rather than just distance metrics. This approach provides flexibility for policy implementation but requires more complex configuration and management.

Routing Policy Application

Each AS implements specific rules for traffic exchange with other systems. These policies might prioritize certain paths for performance reasons, reject routes from competitors, or implement traffic engineering to balance network loads.

Policy decisions can be based on economic factors (preferring cheaper transit providers), security considerations (avoiding certain regions), or performance requirements (selecting low-latency paths). The flexibility to implement custom policies is a key advantage of the AS concept.

Types of Autonomous Systems

Stub AS

A stub AS connects to only one other AS and does not allow transit traffic to pass through its network. Small organizations and end-user networks typically operate as stub systems. They receive internet connectivity through a single upstream provider and don’t participate in global routing beyond their own traffic.

Stub systems have simpler routing configurations since they don’t need to manage multiple external connections or transit policies. They typically use default routing to send all external traffic to their single upstream provider.

Multihomed AS

A multihomed AS connects to two or more other Autonomous Systems but typically doesn’t provide transit services. Organizations choose multihoming to improve reliability and redundancy. If one upstream connection fails, traffic can still flow through alternative paths.

Multihomed systems must carefully manage their routing policies to prevent becoming inadvertent transit providers. They announce their own IP prefixes to multiple upstream providers but don’t typically re-advertise routes learned from one provider to another.

Transit AS

A transit AS connects to multiple other systems and allows traffic to pass through its network between those systems. Major ISPs typically operate as transit providers, forming the backbone infrastructure of the internet.

Transit systems must handle complex routing policies and maintain high-capacity network infrastructure. They generate revenue by providing connectivity services to other Autonomous Systems and must carefully manage their routing advertisements to optimize traffic flow.

Internet Exchange Points (IXPs)

IXPs provide physical infrastructure where multiple Autonomous Systems can peer directly to exchange traffic locally. These facilities bypass traditional transit providers and reduce costs while improving latency for regional traffic.

IXPs don’t operate as traditional Autonomous Systems but serve as neutral meeting points where multiple systems can interconnect. They play a crucial role in internet infrastructure by enabling efficient local traffic exchange.

Key Advantages and Considerations

Scalability Benefits

The AS concept divides the global routing problem into smaller, manageable units. Without this hierarchical structure, internet routers would need to maintain routing tables for every network worldwide—an impossible task given current technology limitations.

Autonomous Systems enable the internet to scale by containing routing complexity within individual systems. External systems only need to know how to reach entire ASes, not individual networks within them.

Policy Control and Flexibility

Organizations maintain independent control over their internal routing policies while participating in the global internet. This autonomy allows for customized network management based on specific business requirements, security needs, or performance goals.

The ability to implement custom routing policies enables organizations to optimize their network performance, control costs, and maintain security standards without external interference.

Complexity and Management Challenges

BGP configuration and management require specialized expertise. Routing policy errors can have widespread internet impact, making proper configuration and monitoring essential. The complexity of inter-AS routing represents a significant operational challenge for network administrators.

Organizations must invest in skilled personnel and proper tools to manage BGP effectively. Misconfigurations can lead to traffic hijacking, routing loops, or widespread connectivity issues.

Key Terms Appendix

  • Autonomous System (AS): A collection of IP networks and routers under unified administrative control with a common routing policy.
  • Autonomous System Number (ASN): A globally unique identifier assigned to each AS for routing purposes.
  • Border Gateway Protocol (BGP): The standard protocol for routing between Autonomous Systems.
  • Interior Gateway Protocol (IGP): Routing protocols used within a single AS, such as OSPF or EIGRP.
  • IP Prefix: A block of IP addresses represented in CIDR notation, such as 192.168.1.0/24.
  • Routing Policy: Rules that define how an AS sends and receives traffic from other systems.
  • Transit AS: An AS that carries traffic between other Autonomous Systems.
  • Stub AS: An AS that connects to only one other AS and doesn’t provide transit services.

Continue Learning with our Newsletter