# What Is an ASN? The Network Behind an IP Address | ProxyJam

What is an ASN? The number a network goes by in internet routing: how BGP uses it, who assigns it, which ranges are reserved, and how to look one up.

- Canonical: https://proxyjam.com/blog/what-is-an-asn/
- Updated: 2026-11-02
- Language: en

An ASN (autonomous system number) identifies a network with one routing policy when it exchanges routes with other networks over BGP. An IP address has no ASN of its own: the number shown beside it belongs to the network that originates the route to its block. Regional internet registries assign the numbers, some ranges are reserved, and one company can run several, so check a number before reading a company into it.


## Read an AS number in three places

1. **Find its registry** Open IANA's [AS numbers registry](https://www.iana.org/assignments/as-numbers/) and find the block your number falls in. The row names the regional registry that assigned it and that registry's RDAP server.
2. **Read the registration** Query that RDAP server for the number and note the AS name, the organisation it is registered to, and the dates it was registered and last changed.
3. **List what it announces** Run RIPEstat's announced-prefixes query for the number and note the prefixes it has announced over the past two weeks.
4. **Read the operator's record** Search [PeeringDB](https://www.peeringdb.com/) for the number. Its record shows the network type, the organisation, other names the network goes by and its peering policy, as the operator entered them.
5. **Keep the number** Record the AS number beside anything you note down, with the name only as a label. If the sources name different organisations, the number still points at one network.

## Reserved AS numbers and what they mean

|  | Numbers | What it means when you meet one |
|---|---|---|
| AS 0 | 0 | No network at all. RFC 7607 bars it from BGP paths, and a route origin authorisation naming AS 0 says the holder wants the block left unrouted (RFC 6483) |
| AS112 | 112 | A distributed set of name servers that absorbs reverse DNS queries for private addresses (RFC 7534). Many sites announce it at once, by design |
| AS_TRANS | 23456 | A stand-in for a 32-bit number, written for routers that only understand 16-bit ones (RFC 6793). The real number travels in a separate attribute |
| Documentation | 64496 to 64511, and 65536 to 65551 | Examples in RFCs, manuals and articles such as this one (RFC 5398). They are not meant to appear in live routing |
| Private use | 64512 to 65534, and 4200000000 to 4294967294 | Numbers for routing that stays inside an organisation or between it and its provider. RFC 6996 requires them to be removed before routes reach the global internet |
| Last numbers | 65535 and 4294967295 | The final 16-bit and 32-bit numbers, reserved by RFC 7300. Some BGP communities of AS 65535 carry meanings every router knows |

Each row follows IANA's registry of special-purpose AS numbers and the RFC that entry cites. The registry was last updated on 7 August 2015.


## Quick answers

### What does ASN mean?

Autonomous system number. An autonomous system is a network, or a group of networks, with a single routing policy, and its number identifies it in BGP, the protocol networks use to exchange routes. Lookups print it as AS followed by the number, for example AS64496, a number reserved for documentation.

### Does every IP address have an ASN?

Only an address in a block that some network announces on the internet. Private ranges such as 192.168.0.0/16 from RFC 1918 are not routed on the public internet, so a lookup finds no origin AS for them, and a public block that nobody announces at the moment returns none either.

### Why does AS23456 appear in a path?

It is AS_TRANS, the placeholder RFC 6793 defines for a 32-bit AS number passing a router that only understands 16-bit numbers. It stands in for another network, and the real number travels in the AS4_PATH attribute of the same route.

### What is the difference between asplain and asdot?

They are two ways of writing a 32-bit AS number. Asplain is the plain decimal, the form RFC 5396 asks documents, systems and user interfaces to use. Asdot writes any number from 65536 upwards as two 16-bit halves joined by a dot, so AS65546 becomes 1.10.

### How does a network get an ASN of its own?

By applying to the regional internet registry that serves its region. The rules differ by registry: ARIN's policy makes a single ASN available to any organisation that requests one, while RIPE NCC's requires the network to be multihomed and the applicant to state its routing policy.

### Which ASN is a ProxyJam address on?

The ASN of the carrier named on the order, since that carrier's network announces the address. Every ISP address we sell names its carrier, so you can look that carrier's AS up in a registry or PeeringDB before you order.


## Sources

- [RFC 1930: Guidelines for creation, selection, and registration of an Autonomous System](https://www.rfc-editor.org/rfc/rfc1930), one routing policy per AS, the warning against using an AS as an administrative grouping, and multihoming as the main case for an AS of one's own
- [RFC 4271: A Border Gateway Protocol 4 (BGP-4)](https://www.rfc-editor.org/rfc/rfc4271), the AS path, prepending, loop detection, the shortest-path tie-breaker and the Bad Peer AS check when a session opens
- [RFC 6793: BGP Support for Four-Octet Autonomous System (AS) Number Space](https://www.rfc-editor.org/rfc/rfc6793), 32-bit AS numbers, AS_TRANS and the AS4_PATH attribute
- [RFC 5396: Textual Representation of Autonomous System (AS) Numbers](https://www.rfc-editor.org/rfc/rfc5396), the asplain, asdot and asdot+ notations
- [IANA: Autonomous System (AS) Numbers](https://www.iana.org/assignments/as-numbers/), the blocks allocated to each regional registry with its whois and RDAP servers
- [IANA: Special-Purpose AS Numbers](https://www.iana.org/assignments/iana-as-numbers-special-registry/), the reserved numbers in the table, with the RFC behind each
- [RFC 5398](https://www.rfc-editor.org/rfc/rfc5398), [RFC 6996](https://www.rfc-editor.org/rfc/rfc6996), [RFC 7300](https://www.rfc-editor.org/rfc/rfc7300), [RFC 7607](https://www.rfc-editor.org/rfc/rfc7607), [RFC 6483](https://www.rfc-editor.org/rfc/rfc6483) and [RFC 7534](https://www.rfc-editor.org/rfc/rfc7534), the documentation, private-use, last and zero AS numbers, the AS 0 route origin authorisation and AS112
- [RFC 1918: Address Allocation for Private Internets](https://www.rfc-editor.org/rfc/rfc1918), the private address ranges that are not routed on the public internet
- [RFC 6888: Common Requirements for Carrier-Grade NATs (CGNs)](https://www.rfc-editor.org/rfc/rfc6888), carrier-grade NAT sharing one public address among many subscribers
- [RFC 6811: BGP Prefix Origin Validation](https://www.rfc-editor.org/rfc/rfc6811), checking a route's origin AS against signed route origin authorisations
- [ARIN: Number Resource Policy Manual](https://www.arin.net/participate/policy/nrpm/), version 2025.1, section 5 on issuing AS numbers
- [RIPE NCC: Autonomous System (AS) Number Assignment Policies (RIPE-679)](https://www.ripe.net/publications/docs/asn-assignment-policies/), the multihoming requirement, the routing policy in RPSL and the single 32-bit pool from 2010
- [RIPEstat: Announced Prefixes](https://stat.ripe.net/docs/data-api/api-endpoints/announced-prefixes), the prefixes an AS announced, the two-week default window and the threshold of 10 RIS peers
- [PeeringDB: About](https://www.peeringdb.com/about), the purpose of the database and its user-maintained records
- [CenturyLink: completion of the Level 3 acquisition, press release of 1 November 2017 filed with the SEC as Exhibit 99.2](https://www.sec.gov/Archives/edgar/data/0000018926/000119312517329388/d465108dex992.htm), the date the two companies combined
- [Lumen: CenturyLink Transforms, Rebrands as Lumen, press release of 14 September 2020](https://s21.q4cdn.com/756714007/files/doc_news/CenturyLink-Transforms-Rebrands-as-Lumen-2020.pdf), the Lumen brand, CenturyLink kept for residential and small business customers, and the ticker change on 18 September 2020




An autonomous system number (ASN) is how internet routing refers to a network.
Here the starting point is the number itself: what it stands for, how routers
use it and where to read about it. To find the ASN behind a particular IP
address, use the methods in [what is my ISP](/blog/what-is-my-isp/). ProxyJam
sells static residential (ISP) proxies, each announced by a named carrier's
network, so a carrier's ASN is something our buyers check.
Our [editorial policy](/editorial-policy/) explains how articles like this are
sourced and corrected.

## What is an autonomous system?

An autonomous system (AS) is a network, or a set of networks, that the rest of
the internet treats as one unit for routing, with one routing policy deciding
which routes it accepts and which it passes on.
[RFC 1930](https://www.rfc-editor.org/rfc/rfc1930) puts the rule in a single
sentence: "Without exception, an AS must have only one routing policy." Inside
its own AS, an operator routes traffic as it chooses, with whatever interior
protocol it runs. Between autonomous systems, routes travel over the Border
Gateway Protocol (BGP), and the AS number is how BGP tells one network from
another.

Because the number stands for a policy, RFC 1930 warns against using an AS to
group prefixes that sit "under the same administrative umbrella" but follow
different policies. Its main case for a network to have an AS of its own is a
network connected to two or more providers. Such a network has preferences
among those providers that differ from each provider's, and a separate AS is
how it expresses them. The guideline calls this "ALMOST THE ONLY case where a
network operator should create its own AS number."

## How does BGP use AS numbers?

Every route BGP carries has an AS path, the list of autonomous systems the
announcement has passed through
([RFC 4271](https://www.rfc-editor.org/rfc/rfc4271), section 5.1.2). The network
that starts the announcement, called the origin, puts its own number in the
path, and each network that hands the route on to another AS adds its number
in front. Seen from a router in a fourth network, a route for one block can
look like this (every number here is reserved for documentation):

```
Prefix:   203.0.113.0/24
AS path:  64500 64501 64496
```

Read the path from right to left. AS64496 originated the route, AS64501
received it and passed it on, and AS64500 is the neighbour that delivered it to
the router you are looking from. Traffic toward 203.0.113.0/24 travels the
other way, from AS64500 through AS64501 to AS64496.

Routers use the path in three ways.

- **To refuse loops.** By default, a router excludes any route whose path
  already contains its own AS number, since accepting it would send traffic
  back through a network it has already crossed (section 9.1.2).
- **To break ties.** When a router holds several equally preferred routes to
  one block, the first tie-breaker in section 9.1.2.2 keeps those with the
  fewest AS numbers in their path. The preference an operator sets on a route
  is applied before that, so the shortest path does not always carry the
  traffic.
- **To steer traffic.** The RFC lets a network add its own number more than
  once. When other preferences are equal, a longer path makes that route less
  attractive to others, which an operator can use to move incoming traffic onto
  another link.

The origin AS is the network an address is on, as far as routing is
concerned, and its number is the ASN that tools print beside an IP address.
Who holds the block is written down elsewhere, in the address registration,
and the two can name different organisations.

## Who assigns AS numbers?

IANA allocates blocks of AS numbers to the five regional internet registries,
which "further allocate or assign AS Numbers to network operators in line with
RIR policies", in the words of IANA's
[AS numbers registry](https://www.iana.org/assignments/as-numbers/). Each row
of that registry names the registry a block went to and the servers that answer
for it.

The policies are not the same everywhere. Under section 5 of ARIN's
[Number Resource Policy Manual](https://www.arin.net/participate/policy/nrpm/)
(version 2025.1), any organisation "may be issued a single Autonomous System
Number (ASN) upon request", and ARIN asks for a justification only when an
organisation wants more than one. RIPE NCC's
[assignment policy](https://www.ripe.net/publications/docs/asn-assignment-policies/)
(RIPE-679) sets a condition first: "A network must be multihomed in order to
qualify for an AS Number". An applicant there also has to state the routing
policy of the new AS, written in RPSL, the language of the RIPE Database. So
whether a network with a single provider can get a number of its own depends on
the registry that serves it.

## What are 16-bit and 32-bit AS numbers?

BGP-4 carried the AS number in a two-octet field, which holds 65,536 values,
from 0 to 65535. To prepare for running out,
[RFC 6793](https://www.rfc-editor.org/rfc/rfc6793) extended it to four octets,
which raises the ceiling to 4294967295.

The two sizes still meet on the same internet. A router that understands only
16-bit numbers cannot carry a 32-bit one. When a newer router sends a route
to an older one, it writes AS_TRANS, number 23456, in place of any number from
65536 upwards and sends the real path in a separate attribute, AS4_PATH,
which the older router forwards without reading. AS23456 in a path therefore
stands in for some other network.

RIPE NCC no longer treats the sizes differently: it has assigned from a single
32-bit pool since 1 January 2010, and before that it handed out 32-bit numbers
by default from 2009 (RIPE-679).
[RFC 5396](https://www.rfc-editor.org/rfc/rfc5396) asks documents, systems and
user interfaces to write every AS number in plain decimal, called asplain. Older
material sometimes uses asdot, which splits any number from 65536 upwards into
two 16-bit halves joined by a dot, so AS65546 appears as 1.10.

Some numbers are reserved and do not identify an ordinary network. The table
Reserved AS numbers and what they mean lists them from IANA's special-purpose
registry, and two of the ranges come up often. The documentation ranges exist
so that examples in RFCs, manuals and posts cannot collide with a real network.
The private-use ranges let an organisation run BGP internally, or with its
provider, without an assigned number. RFC 6996 requires them to be removed from
paths before routes reach the global internet, so a private number in a public
path means somebody did not remove it.

## Why does one company run several ASNs?

Because an AS is a unit of routing policy, and a network keeps its number when
its owner changes. That number is configured on every neighbouring network it
exchanges routes with. When a BGP session opens, each side checks the AS number
the other announces, and a number it does not accept ends the session with a
Bad Peer AS error (RFC 4271, section 6.2). Renumbering after a merger therefore
means changing the configuration of every one of those sessions, and nothing in
BGP requires it, so old numbers can outlive the companies that registered them
by years.

Lumen shows how this looks from the outside. CenturyLink completed its
acquisition of Level 3 Communications on 1 November 2017
([press release filed with the SEC](https://www.sec.gov/Archives/edgar/data/0000018926/000119312517329388/d465108dex992.htm)).
On 14 September 2020 it announced its new brand, Lumen, kept CenturyLink as the
brand for residential and small business customers, and moved its stock ticker
from CTL to LUMN on 18 September
([press release](https://s21.q4cdn.com/756714007/files/doc_news/CenturyLink-Transforms-Rebrands-as-Lumen-2020.pdf)).
When we checked on 26 October 2026, the records told the story in two
vocabularies:

- **ARIN's registry** listed the Level 3 and CenturyLink networks we queried
  under Level 3 Parent, LLC and CenturyLink Communications, LLC, with AS names
  such as LEVEL3 and CENTURYLINK-US-LEGACY-QWEST. None of the records we read
  carried the Lumen name.
- **[PeeringDB](https://www.peeringdb.com/)** listed several networks under the
  organisation Lumen Technologies Inc, most of them named Lumen followed by
  the AS number, with other names that include CenturyLink, Level3, Qwest and
  Savvis.

So one company runs several ASNs, a single ASN can carry several brands (the
PeeringDB record for the network ARIN lists as LEVEL3 gives both CenturyLink
and Level3 as other names), and the name you see depends on the database you ask.
The registry shows the legal entity a number is registered to; PeeringDB shows
what the operator calls its network today.

Lumen and CenturyLink also appear in our US catalogue as two separate carriers.
The carrier named on one of our addresses is the network that announces it, so
two carrier labels can belong to one parent company. Check the AS behind each
one before you pick between them.

## How do you look up an ASN?

Start from the number. If you have an IP address instead,
[what is my ISP](/blog/what-is-my-isp/) gives three ways to get from the
address to its ASN, and [What Is My IP](/what-is-my-ip/) shows the one for your
own connection in its Network (ASN) row. The steps in Read an AS number in three
places take a number through its registration, RIPEstat and PeeringDB, and each
of the three answers a different question.

### Who the number is registered to

IANA's row for the number names the regional registry that assigned it and the
server to query, and the record there gives the AS name, the organisation and
the dates. This is the administrative view, and it usually changes only when
the organisation updates it, which can be years after a rebrand, as the Lumen
records show. In the RIPE NCC region, where applicants describe their routing
policy in RPSL, the record may also list the neighbouring networks the AS
exchanges routes with.

### Which prefixes it originates

RIPE NCC's [RIPEstat](https://stat.ripe.net/) reads routing data gathered by
RIPE NCC's Routing Information Service (RIS). Its
[announced-prefixes query](https://stat.ripe.net/docs/data-api/api-endpoints/announced-prefixes)
returns the prefixes an AS originated that at least 10 RIS peers saw, over a
window that defaults to the past two weeks:

```
https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS64496
```

Put your number in place of the documentation one. A count of prefixes
describes how the network splits its address space for routing. It says
nothing about how many people use the network, since one prefix can hold a
single server or a large group of subscribers.

### How the operator describes it

[PeeringDB](https://www.peeringdb.com/about) was set up "to facilitate peering
between networks and peering coordinators", and its records are user-maintained.
A network's entry is therefore the operator's own description: its name and
other names, its organisation, its network type (such as NSP, Content or
Cable/DSL/ISP), its peering policy and the exchange points and facilities where
it connects. Not every AS has an entry, and an entry is only as current as its
operator keeps it.

## What does the ASN tell you about a proxy address?

It tells you which network announces the address, which is also the network
that IP-to-ASN services report for it. We name that network on every ISP
address we sell for this reason, so you can check its AS before you order. On
the
[US ISP proxies page](/isp-proxies/usa/), some carriers are backbone networks
and others are regional providers, and the network type in PeeringDB can hint
at which is which. Our addresses sit on servers in data centres and are
announced by the carrier's network. The
[definition of an ISP proxy](/blog/what-are-isp-proxies/) covers what that
combination is good for, and
[residential vs datacenter proxies](/blog/residential-vs-datacenter-proxies/)
compares it with addresses that sit in a hosting company's own AS.
[Static residential proxies](/static-residential-proxies/) is the second name
the market uses for the same product, with its own page.

## When does an ASN not answer the question?

- **Where an address is.** A number names a network, and a large network
  serves many countries: Lumen's 2020 release describes customers in more than
  60. Location comes from geolocation data, a separate source.
- **Whether a route is authorised.** The origin AS in a path is whichever
  network originated the route, with or without the permission of the
  organisation that holds the block. Route origin validation compares the
  origin with signed authorisations
  ([RFC 6811](https://www.rfc-editor.org/rfc/rfc6811)).
- **How much traffic a network carries.** Prefix lists and peering records
  describe routing. Neither measures the traffic on it.
- **How many people share one address.** On mobile networks, carrier-grade NAT
  puts many subscribers behind each public address, and the AS number cannot
  show it. Mobile proxies are not on sale here yet; the
  [mobile proxies page](/mobile-proxies/) describes them.

Before you buy, the [US ISP proxies page](/isp-proxies/usa/) names all
23 carriers whose networks announce our US addresses, so each AS
can be checked in advance. For the rest of the world, the
[ISP proxies page](/isp-proxies/) covers all 76 countries in the
catalogue, and the [pricing page](/pricing/) gives the price per IP per period.

