How IP Addresses Are Assigned

Short answer: IP addresses are assigned in layers. IANA coordinates the global address space, Regional Internet Registries allocate public blocks to networks in their regions, ISPs and organizations divide those blocks for customers and infrastructure, and your router assigns local addresses to devices on your home network.

That is the simple version of how IP addresses are assigned. The practical details depend on whether you mean a public IPv4 address, an IPv6 prefix, a private home-network address, a static address, or a dynamic lease that can change later.

The IP address assignment chain at a glance

The table below shows how IP addresses are assigned at each layer, from the global registry system down to the device on your desk or in your pocket.

How IP addresses are assigned globally

The public internet needs each globally routable IP address to be unique. That is why assignment follows a registry chain rather than random choice. IANA maintains official registries such as the IPv4 Address Space registry and IPv6 Global Unicast Address Space registry. Those registries show which large ranges are reserved, legacy, allocated, or delegated.

IANA does not usually assign a home router its address directly. It delegates large blocks to Regional Internet Registries, and those registries work with ISPs, hosting providers, universities, companies, governments, and other networks. The result is a layered chain that keeps public addresses unique and traceable at the network-registration level.

The assignment chain from IANA to your router

The full path usually has six practical layers: IANA, the RIR, the ISP or organization, routing registration, customer assignment, and the local router/device layer.

1. IANA coordinates the global pool. It records public IPv4 and IPv6 address space and delegates large ranges under global policy.
2. Regional Internet Registries manage regions. ARIN covers North America, RIPE NCC covers Europe, the Middle East, and parts of Central Asia, APNIC covers Asia-Pacific, LACNIC covers Latin America and the Caribbean, and AFRINIC covers Africa.
3. ISPs and organizations request resources. ARIN's resource request guidance explains that organizations request Internet number resources such as IP addresses and ASNs under policy requirements.
4. Networks register and announce prefixes. Address blocks are registered in public databases and announced through routing so traffic knows where to go.
5. ISPs divide blocks for customers. An ISP may assign one public IPv4 address, put many customers behind CGNAT, or delegate an IPv6 prefix.
6. Your router handles the local network. The router receives the upstream assignment, then gives private or local addresses to phones, laptops, TVs, consoles, and smart devices.

Public IP addresses vs private local addresses

A public IP address is reachable on the internet if routing and firewall rules allow it. A private local address is used inside a home, office, or school network and is not globally routed. Most home networks use private IPv4 ranges such as 192.168.x.x, 10.x.x.x, or 172.16.x.x; RFC 1918 defines these private IPv4 address blocks for internal networks.

This is where people often confuse how IP addresses are assigned. Your ISP assigns the public side. Your router assigns the local side. A phone may have a local Wi-Fi address at home, a different local address at work, a mobile carrier address on cellular data, and a different public route when using a VPN.

DHCP, SLAAC, and DHCPv6 in plain English

Inside a network, assignment is often automatic. With IPv4, a router usually runs DHCP. A device asks for settings, and the router gives it an address, default gateway, DNS resolver, and lease time. RFC 2131 describes DHCP for IPv4; in practical home terms, it is the reason a laptop can join Wi-Fi and receive working network settings without manual typing.

IPv6 works differently. A router can advertise an IPv6 prefix, and devices may create their own addresses using SLAAC, described in RFC 4862. In some networks, DHCPv6 provides additional settings or delegates prefixes to downstream routers; RFC 8415 covers modern DHCPv6 behavior. RIPE NCC's guidance on documenting IPv6 assignments shows how IPv6 allocations and assignments can be represented in registry data.

Static, dynamic, and shared assignments

A static public IP normally stays the same. It is useful for hosting, allowlists, remote access, business services, and predictable DNS records. It can also make activity easier to correlate over time because the same public address appears repeatedly.

A dynamic public IP can change after a lease renewal, router reboot, network maintenance, or ISP policy event. Dynamic addresses are common for residential service. They are not a privacy shield by themselves, but they can reduce long-term correlation compared with a stable static address.

Shared assignment is common too. Many mobile and residential networks use CGNAT, where multiple customers share one public IPv4 address. That can make simple public-IP lookup less personal, but it can also complicate gaming, self-hosting, port forwarding, and abuse reports.

Why IPv4 scarcity changed assignment

IPv4 has a small address space by modern internet standards. That scarcity led to NAT, CGNAT, address transfers, tighter registry policy, and widespread sharing of public IPv4 addresses. It is one reason a home router can have one public IPv4 address while dozens of devices behind it use private local addresses.

IPv6 was designed with a much larger address space. Instead of giving every home only one address, an ISP can delegate a prefix so multiple internal networks and devices can use globally unique IPv6 addresses. That is cleaner for routing, but it also makes firewalling and privacy-extension behavior important.

Why assignment affects geolocation, blacklists, and privacy

Services use IP assignment data to infer network owner, country, region, ASN, hosting status, mobile status, VPN/proxy likelihood, and abuse history. These signals are useful, but they are not perfect. A location database may point to an ISP office, a nearby city, a mobile gateway, or a region where the block is registered rather than your exact room.

• Geolocation: depends on registry data, routing, provider corrections, app signals, and commercial datasets.
• Blacklists: spam or abuse reports can affect an address, prefix, or shared network range.
• Account security: platforms may flag logins from new regions, data-center ranges, VPNs, or unfamiliar networks.
• Privacy: static assignments and rare IPv6 patterns can be easier to correlate than short-lived or shared assignments.

Why IP assignment matters for normal users

Normal users do not need to memorize how IP addresses are assigned, but the assignment type explains many everyday internet problems. It can affect whether an app sees your location correctly, whether remote access works, and why one service treats your connection differently from another.

• It affects whether you have public IPv4, CGNAT, or IPv6.
• It affects whether self-hosting, gaming, cameras, or remote access will work.
• It affects how websites estimate your location and network owner.
• It affects troubleshooting when DNS, VPN, ASN, or blacklist results look strange.
• It affects privacy because static or rare assignments can be easier to correlate over time.

How to tell what kind of assignment you have

You can usually identify the broad assignment type without calling your ISP. First, compare the public IP shown by a web tool with the WAN address inside your router. If the router WAN address is private, carrier-grade NAT, or different from the public address websites see, your ISP may be sharing one public IPv4 address across many customers. If the values match and inbound ports work after explicit firewall rules, you probably have a directly assigned public IPv4 address.

For IPv6, look for a delegated prefix in the router status page. A home connection may receive a prefix such as a /56 or /64, then advertise smaller subnets to devices. If your devices have IPv6 addresses but the firewall blocks inbound traffic, that is normal and usually desirable. If a service becomes reachable from outside unexpectedly, review router firewall rules before assuming the assignment itself is the problem.

• Dynamic IPv4: public address may change after lease renewal, router reboot, or ISP maintenance.
• Static IPv4: public address remains stable and may be listed on the bill or account portal.
• CGNAT: router WAN address often sits behind a shared provider address, limiting inbound hosting.
• IPv6 prefix delegation: router receives a prefix and advertises IPv6 routes to local networks.

Common mistakes when reading IP assignment data

• Expecting street-level geolocation. IP location is approximate and can be wrong, especially for mobile, VPN, corporate, and newly reassigned ranges.
• Confusing public and private addresses. A local 192.168.x.x address does not identify your public internet route.
• Treating IPv6 as firewall-free networking. IPv6 removes the need for NAT, not the need for sensible inbound filtering.
• Treating dynamic assignment as identity protection. A changing IP does not erase cookies, account logins, browser fingerprints, or provider logs.
• Blaming every blacklist on your device. Shared networks and previous address users can affect reputation.

What to do next

If you want to understand your own assignment, start with what your browser shows publicly, then compare the visible IP, ASN, IPv6, DNS, and geolocation signals. Ask your ISP whether your plan uses static IPv4, dynamic IPv4, CGNAT, or IPv6 prefix delegation if you need a precise answer.

The practical answer is that how IP addresses are assigned affects routing, troubleshooting, privacy, reputation, and remote-access design. It does not, by itself, prove who is using a device or whether a network is safe.