
APIPA: What It Is, the 169.254 Address Range, and How to Fix It
When a Windows laptop suddenly shows a 169.254.x.x address instead of your usual 192.168.x.x address, the internet stops working. That strange address is not random, and it is not a hack. It is APIPA — Automatic Private IP Addressing — a built-in fallback that lets a device give itself an address when it cannot reach a DHCP server. This guide explains what APIPA is, how the 169.254 range works, why a device ends up with an APIPA address, and exactly how to fix it, plus the security risks to watch for.
What Is APIPA?
APIPA stands for Automatic Private IP Addressing. It is built into Windows, macOS, and Linux, and it automatically assigns a device a private IP address from the link-local range 169.254.0.1 to 169.254.255.254 when the device is set to get an address automatically through DHCP but no DHCP server answers. The idea is simple: a device with no address cannot talk to anything, but a device with an APIPA address can at least communicate with other devices on the same local network segment that also have APIPA addresses. APIPA is defined in RFC 3927, which standardizes IPv4 link-local addressing. In short, APIPA is a safety net, not a normal way to run a network: it keeps local communication possible while telling you that something is wrong with DHCP.
APIPA Address Range and Quick Facts
Everything you need to recognize an APIPA address at a glance is in the table below.
| Fact | Detail |
|---|---|
| Full name | Automatic Private IP Addressing |
| Address range | 169.254.0.1 to 169.254.255.254 |
| Network block (CIDR) | 169.254.0.0/16 |
| Subnet mask | 255.255.0.0 |
| Reserved addresses | 169.254.0.0 (network) and 169.254.255.255 (broadcast) are never assigned to a device |
| Default gateway | None |
| DNS servers | None assigned |
| Routable on the internet? | No, link-local only |
| Defined by | RFC 3927 (IPv4 link-local addressing) |
| Used by | Windows, macOS, Linux, printers, cameras, and IoT devices |
| What it means | The device could not reach a DHCP server |
Two addresses in that range are reserved and never assigned: 169.254.0.0 identifies the network itself, and 169.254.255.255 is the broadcast address. Everything between them — 169.254.0.1 through 169.254.255.254 — is available, giving 65,534 usable addresses. Because APIPA assigns no default gateway and no DNS servers, a device with an APIPA address cannot reach the internet or any other network. It can only exchange traffic with other devices on the same segment that also hold 169.254 addresses.
How APIPA Works
APIPA follows a predictable sequence every time a device fails to get a DHCP lease.
- The device asks for an address. When it boots or connects, it broadcasts a DHCP Discover message asking any DHCP server on the network for an address.
- No server answers. After several retries with no reply, the device gives up waiting and picks a random address from the 169.254.0.0/16 range.
- The device checks the address is free. It sends ARP probes to confirm no other device is using it; if the address is taken, it picks another one.
- The APIPA address is assigned. The device applies the address with the subnet mask 255.255.0.0, and no gateway or DNS servers.
- The device keeps retrying DHCP. Every few minutes it retries, and as soon as a server answers it drops the APIPA address and takes the DHCP lease.
That background retry is why an APIPA problem sometimes fixes itself when the router comes back online. Until a DHCP server responds, the APIPA address stays and the device remains cut off from the internet.
Why Your Device Gets an APIPA Address
An APIPA address is a symptom, not the disease. It appears whenever a device that expects DHCP cannot complete the DHCP exchange. The most common causes are:
- The DHCP server is down or unreachable. The router has rebooted, crashed, or had DHCP switched off.
- The DHCP scope is exhausted. Every address in the pool is already leased, common on busy guest networks.
- A cable or Wi-Fi problem. A damaged Ethernet cable, loose connector, faulty switch port, or weak Wi-Fi signal blocks the DHCP request.
- A switch, VLAN, or port misconfiguration. The device is on a VLAN with no DHCP server or relay, or the port is in the wrong VLAN.
- A firewall or security program is blocking DHCP. DHCP uses UDP ports 67 and 68, which a misconfigured firewall can drop.
- The network has no DHCP server at all. This happens when a laptop moves to a network that only uses static addressing.
- The DHCP client service is not running. On Windows, if the DHCP Client service has stopped, the device never asks for an address.
Your Device Shows 169.254 — What to Check
Work through these steps in order. Most APIPA problems are fixed by step 3, but each step rules out a different cause.

- Check the physical connection. Reseat the Ethernet cable at both ends, try a different cable and switch port, or reconnect to Wi-Fi.
- Restart the device and the router. Reboot the computer first; if the problem remains, restart the router and wait two minutes.
- Release and renew the address. On Windows, run
ipconfig /releasefollowed byipconfig /renewin an administrator Command Prompt. - Check whether other devices are affected. If every device shows 169.254, the DHCP server or switch is at fault; if only one is, the fault is local to it.
- Check the DHCP Client service. On Windows, open Services and confirm DHCP Client is running and set to Automatic.
- Check the router’s DHCP settings. Confirm DHCP is enabled, the address pool is not exhausted, and increase the pool if it is full.
- Rule out VLAN and port problems. Confirm the switch port is on the correct VLAN with a DHCP server or relay, and try a known-good port.
- Temporarily disable the firewall or VPN. If DHCP works with it off, add an exception for UDP ports 67 and 68 instead of leaving protection off. If nothing works, assign a temporary static IP in the correct subnet while you fix DHCP.
APIPA vs DHCP vs Static IP
These three ways of giving a device an IP address solve different problems. APIPA is the fallback; DHCP is the normal automatic method; a static IP is a deliberate manual choice.
| Feature | APIPA | DHCP | Static IP |
|---|---|---|---|
| How the address is assigned | Automatic fallback, chosen by the device itself | Assigned by a DHCP server | Configured manually by an administrator |
| Address range | 169.254.0.1 to 169.254.255.254 | Any range the server manages | Any address the administrator chooses |
| Default gateway | None | Provided by the server | Configured manually |
| DNS servers | None | Provided by the server | Configured manually |
| Internet access | No | Yes, when the network is set up for it | Yes, when configured correctly |
| Management effort | None, but the result is a broken connection | Centralized and easy to manage | Predictable, but hard to manage at scale |
| Best for | Temporary local-only fallback | Most home and office networks | Servers, printers, routers, and network equipment |
The practical difference is the gateway and DNS settings. DHCP and static IP both deliver a complete configuration — address, subnet mask, gateway, and DNS — so the device can reach the internet and other networks. APIPA delivers only an address and a subnet mask, enough for two devices on the same switch to find each other and nothing more. That is why a 169.254 address is a useful diagnostic clue: it proves the network hardware works and the link is up, but the DHCP conversation failed.
Can You Use APIPA on Purpose?
Yes, in two narrow situations APIPA is genuinely useful. First, on an ad-hoc local network with no router — two laptops connected directly, or a laptop plugged straight into a printer — APIPA gives both devices addresses so they can communicate without setup. Second, some printers, cameras, and industrial devices only need to talk to other devices on the same switch, and APIPA lets them do that with zero configuration. For anything else, treat APIPA as a warning light, not a choice: a device that depends on the internet, a VPN, cloud services, or a server on another subnet will not work on an APIPA address.
APIPA Security Notes: What to Watch For
An APIPA address is not a security feature, and it can quietly create risks if it is ignored.
- A device stuck on APIPA is an unmanaged blind spot. It cannot reach update servers, cloud security tools, or central logging, so it misses patches and monitoring. Network monitoring tools such as SNMP can help you spot devices that have fallen back to 169.254 addresses before users complain.
- Local traffic is still exposed. APIPA traffic never leaves the local segment, but an attacker on the same switch segment can still reach an APIPA device. Keep a host firewall running; a network firewall still matters on a local segment.
- Do not fix APIPA with static addresses everywhere. Handing out static IPs across the office to work around a broken DHCP server creates conflicts and undocumented addresses.
- A sudden wave of APIPA addresses is a warning sign. If many devices get 169.254 addresses at once, suspect a DHCP outage or a DHCP starvation attack, and check the DHCP server logs.
- Remote access stops working. A device with an APIPA address cannot reach a VPN gateway or a remote office. See how a site-to-site VPN connects offices to understand what an APIPA device is cut off from.
Frequently Asked Questions
Is a 169.254 address bad?
Not dangerous by itself, but it means your device could not reach a DHCP server, so it has no gateway and no DNS. It can only talk to other devices on the same local segment that also have 169.254 addresses, and it cannot reach the internet.
Why does my PC keep getting a 169.254 address?
The usual causes are a DHCP server that is down or unreachable, an exhausted DHCP address pool, a faulty Ethernet cable or switch port, a VLAN without a DHCP relay, or a firewall blocking DHCP traffic on UDP ports 67 and 68.
Can I use the internet with an APIPA address?
No. APIPA assigns no default gateway and no DNS servers, so the device cannot send traffic outside its own network segment or resolve domain names. You need a valid DHCP lease or a correctly configured static IP to get online.
How do I fix a 169.254 address?
Check the cable and Wi-Fi connection, restart the device and the router, then release and renew the address with ipconfig /release and ipconfig /renew on Windows. If that fails, check that the DHCP Client service is running and that the router has free addresses in its pool.
Is APIPA the same as DHCP?
No. DHCP is the normal service that assigns IP addresses, gateways, and DNS settings from a server. APIPA is the automatic fallback a device uses on its own when DHCP fails, and it provides only a link-local address with no gateway or DNS.
Conclusion
APIPA is your network’s way of telling you DHCP is broken. A 169.254.x.x address means the device gave itself a link-local address because no DHCP server answered — useful for local communication, useless for the internet. Check the cable, restart the router, renew the lease, and verify the DHCP server and its address pool. Fix the DHCP problem, and the APIPA address will disappear on its own.



[…] a device cannot get an address from DHCP, it falls back to a self-assigned address — our guide to what APIPA is and how it works explains that fallback. And the hardware that carries all of this traffic is explained in our guide […]