Who Controls IP Address Allocation? IANA & RIRs

Who controls IP address allocation?

No single organization controls how every IP address is used. IANA coordinates the top of the global Internet number registry system and allocates large blocks to the five Regional Internet Registries (RIRs). RIRs distribute and register address space under regional policies. National or Local Internet Registries, Internet service providers, cloud networks, and other operators may then allocate or assign smaller prefixes to organizations and subscribers.

That hierarchy protects uniqueness and keeps registration records, but it does not operate every route or decide who used one connection. The network with authority over a prefix configures BGP, RPKI, IRR, DNS, subscriber assignments, and abuse handling within its own boundary. To understand one address, follow the registry chain with RDAP, then verify the current route and the provider or organization records relevant to the exact event.

Who is responsible at each IP address layer?
Layer	Typical responsibility	What it does not control by itself
IANA	Coordinates the global IPv4, IPv6, and AS-number registries; allocates top-level number-resource blocks to the RIR system; records special-purpose assignments made through the standards process.	Assign an address to an ordinary end user, approve a customer route, investigate subscriber activity, or operate Internet access.
Regional Internet Registry	Distributes and registers Internet number resources in its service region under the applicable community-developed policies.	Guarantee that a registered prefix is routed, reachable, reputable, or attached to one current user.
NIR, LIR, ISP, cloud, or network operator	Uses authorized resources to provision networks or customers, maintain downstream records, and operate routing and related services.	Change the global registry hierarchy or make its routes accepted by every other network.
Customer or end site	Uses assigned addresses or delegated prefixes and configures its own subnets, hosts, DNS, firewalls, and applications within the service terms.	Acquire registry authority merely by configuring an address, or prove ownership or identity from an address alone.

What does IANA do with IP addresses?

IANA is the top-level registry coordinator for Internet number resources. It maintains registries for IPv4, IPv6, Autonomous System Numbers, and special-purpose number assignments. Its ordinary allocation relationship is with the RIRs, not households, application users, or most network operators.

IANA does not “own the Internet,” operate the five RIRs, or control traffic sent from a registered address. IANA states that it is not an ISP and generally does not control the use of the numbers in its registries. If a public address appears in a log, the practical first step is to identify the responsible RIR and follow the more specific registration record.

ICANN performs the IANA functions through Public Technical Identifiers. That administrative relationship does not turn ICANN into the operator of every allocated network. Global number-resource policies, regional distribution policies, technical standards, registration data, and live routing are related but separate parts of the system.

Which organizations allocate public IP addresses by region?

The five RIRs serve different regions. The exact record for a prefix matters more than a country guess because legacy resources, transfers, multinational networks, and operational locations can cross simple geographic expectations.

The five Regional Internet Registries and their service regions
RIR	Service region	What to verify
AFRINIC	Africa and parts of the Indian Ocean	The current resource record, applicable policy, account relationship, and operational contacts.
APNIC	Asia and the Pacific	Whether the resource is registered directly, through a National Internet Registry, or through another account relationship.
ARIN	Canada, the United States, and parts of the Caribbean	The registered organization, resource status, reassignment or reallocation records, and current service requirements.
LACNIC	Latin America and parts of the Caribbean	The current holder or recipient record, policy path, and authorized contacts.
RIPE NCC	Europe, the Middle East, and Central Asia	The sponsoring or member relationship, registration objects, resource status, and current contacts.

Some countries use a National Internet Registry, and many providers act as Local Internet Registries. Those organizations work inside the wider RIR system rather than replacing it. An ISP can also receive address space from an upstream provider instead of directly from an RIR.

How are public IP addresses allocated?

Global coordination: IANA maintains the top-level number registries and allocates eligible large blocks to the RIRs under global policy.
Regional distribution: an RIR evaluates a request or another permitted transaction under its current policy and records the resulting allocation or assignment.
Downstream provisioning: an NIR, LIR, ISP, cloud provider, or other network operator may subdivide or assign authorized space for its infrastructure and customers.
Local addressing: the receiving organization or customer configures subnets and hosts. DHCP, SLAAC, manual configuration, NAT, or a delegated prefix can take part, depending on the service.
Routing and operations: the responsible networks establish reachability, origin authorization, routing policy, DNS, monitoring, abuse contacts, and lifecycle records.

The arrows are not a universal ownership chain. A registry allocation, a downstream assignment, a DHCP lease, a commercial IPv4 lease, and a BGP announcement describe different facts. Each needs its own evidence.

Allocation, assignment, delegation, registration, and routing

Terms that should not be treated as interchangeable
Term	Practical meaning	Evidence to inspect
Allocation	A block made available for further distribution under the applicable registry policy.	RIR or downstream registry record, policy basis, organization, status, and dates.
Assignment	Space recorded for use by an end site, customer, or network function rather than for further distribution.	Authoritative registration and the provider or organization record that defines the use.
Delegation	Authority or configuration passed to another party, such as reverse-DNS control or an IPv6 prefix delegated to a customer router.	Parent and child records, service configuration, scope, lifetime, and withdrawal process.
Registration	The maintained record for a number resource and its responsible contacts.	RDAP or RIR data, including the most specific record and its update time.
Routing	The control and data-plane work that makes a prefix reachable between networks.	BGP origin and visibility, upstream policy, IRR, RPKI, filters, monitoring, and live tests.
DHCP lease	A time-bounded protocol binding for an address and configuration on a network.	DHCP server and client state, lease times, relay path, and access-session records.
Commercial IPv4 lease	A contract for temporary use of a prefix with defined authority, routing, operations, renewal, and return.	Contract, holder authority, exact CIDR, registry and route evidence, service scope, and exit plan.

Who makes IP address allocation policy?

No single executive writes every rule. Global policies for IANA-to-RIR allocation follow the ICANN policy process. Each RIR develops regional number-resource policy through its community process and then applies the adopted policy to requests and transfers. The IETF publishes protocol standards and special-purpose number assignments; it does not approve ordinary customer allocations.

This division matters when a requirement changes. Questions about a top-level registry entry belong with IANA. Questions about regional eligibility, transfer, allocation, or assignment belong with the relevant RIR or downstream registry. Questions about a customer's address, route, reverse DNS, or service belong with the provider or operator that controls that layer.

What changed after IPv4 exhaustion?

IANA's ordinary central IPv4 free pool was exhausted in 2011, so IANA no longer has a normal supply of fresh /8 blocks to distribute. That does not mean every IPv4 address is usable, permanently assigned, or impossible to recover. IANA maintains a recovered IPv4 pool, and regional registries can receive small periodic shares under global policy. RIRs also operate region-specific waiting-list, recovery, transfer, or other limited distribution paths.

IPv6 allocations continue under a different and much larger address space. Most real networks therefore need an explicit coexistence plan: deploy IPv6 where supported, conserve or share IPv4 where appropriate, and use transfer or leasing arrangements only with verified authority and a complete routing and exit model.

Scarcity does not give an intermediary authority over a prefix. A broker can help find a counterparty, a marketplace can help with discovery, and a managed provider can coordinate operations, but the applicable registry applies its policy and each network controls its own route acceptance.

How do you look up who manages an IP address?

Use RDAP for the exact address or prefix. The bootstrap registry directs the query to the responsible service, and the most specific result identifies the registered resource and contacts available for that record.
Distinguish the registered organization from the current user. A provider allocation can contain many downstream customers, and a shared public address can represent multiple subscribers at one time.
Check live routing separately. Record the observed origin ASN, route visibility, RPKI state, IRR data, and timestamp. Registration does not prove current origination or reachability.
Use the right operational contact. For abuse or security issues, use the contact published for the most specific applicable resource and include precise, validated evidence.
Correlate provider records only when authorized. Subscriber or NAT attribution can require an exact timestamp, time zone, protocol, source and destination addresses, and ports. Public RDAP data does not reveal that private record.

Do not treat the registered country, organization name, GeoIP result, reverse-DNS name, or origin ASN as proof of a person's identity or physical location. Each is a different observation with a different owner and update cycle.

IP allocation and provider checklist

Identify the exact IPv4 or IPv6 prefix, requested size, and intended use.
Find the responsible RIR through RDAP and save the most specific registration result with a timestamp.
Confirm the registered organization, downstream authority, contracting parties, and people allowed to change records.
Separate a permanent transfer, provider assignment, commercial lease, and ordinary ISP service.
Record the origin ASN, BGP route, accepted prefix length, LOA, IRR object, RPKI ROA, reverse DNS, and rollback owner.
Define abuse handling, reputation and geolocation observations, monitoring, change windows, renewal, return, and renumbering.
Verify the current regional policy and provider terms at action time; old summaries do not establish present eligibility.

IP address allocation FAQ

Which organization is responsible for allocating public IP addresses?

IANA coordinates the top of the global hierarchy and allocates large blocks to the RIR system. RIRs, NIRs, LIRs, ISPs, and other authorized operators then distribute or assign smaller resources. The customer-facing address normally comes from the network provider, not directly from IANA.

Does ICANN control every IP address?

No. ICANN performs the IANA functions through PTI, but it does not operate every network, approve every customer assignment, route every prefix, or control the activity associated with registered addresses.

Does IANA assign IP addresses to people or companies?

Usually not. IANA's ordinary allocation relationship is with the five RIRs. Organizations and end users normally receive resources through an RIR, NIR, LIR, ISP, cloud provider, or other network operator.

What are the five Regional Internet Registries?

They are AFRINIC for Africa and parts of the Indian Ocean, APNIC for Asia and the Pacific, ARIN for Canada, the United States, and parts of the Caribbean, LACNIC for Latin America and parts of the Caribbean, and RIPE NCC for Europe, the Middle East, and Central Asia.

Who assigns the public IP address on my Internet connection?

Your ISP or another network provider provisions the customer-facing address or prefix. It may be static, dynamic, shared through CGNAT, delegated as IPv6, or supplied through another documented service model.

Can an RDAP lookup identify the person using an IP address?

No. RDAP provides registration data for number resources and responsible organizations. It does not normally reveal the subscriber or person using one connection. Attribution may require precise event data and authorized access to provider records.

Does registration prove that an IP prefix is routed?

No. Registration, BGP routing, IRR policy data, RPKI origin authorization, DNS, and application reachability are separate. Verify the exact route and service from appropriate independent vantage points.

Who controls a leased IPv4 block?

The answer depends on the contract and operating design. The registered holder may retain registry authority while the lessee receives limited use and routing rights. The agreement should name who controls the route, LOA, IRR, ROA, reverse DNS, abuse response, renewal, withdrawal, and return.

Primary sources

Where i.lease fits

i.lease is not IANA or an RIR, and it cannot grant registry approval or force another network to accept a route. It supports organizations that need temporary public IPv4 capacity through managed IPv4 leasing, including coordination of authority, routing, RPKI, IRR, reputation, abuse handling, renewal, return, and continuity within the agreed scope.

Use the Regional Internet Registry guide for a deeper RIR comparison, the ISP allocation guide for subscriber provisioning, and RIR membership management when an organization needs operational help with its own registry relationship. Bring the exact prefix, region, organization, intended use, origin model, timing, and current evidence so the responsible layer can be identified before action.

Who Controls IP Address Allocation? IANA, RIRs, and ISPs