What Is APIPA (169.254.x.x)? The "No Internet" IP Address

Q: What does a 169.254 IP address mean?

It means your device self-assigned an IPv4 link-local address because it could not get one from DHCP. Microsoft calls this APIPA. The address works only on your local network segment and cannot reach the internet, so a 169.254 address is a sign that the DHCP server, usually your router, did not give your device a real address.

Q: Why is my IP address 169.254 and I have no internet?

Because a 169.254 link-local address is only valid on the local link and has no route to the internet and no default gateway. Your device fell back to it after DHCP failed, so it can reach other devices on the same segment but nothing beyond. Restoring a working DHCP lease is what brings internet access back.

Q: How do I fix a 169.254 IP address?

Get DHCP working again: confirm the router or DHCP server is on and reachable, renew the lease by reconnecting or running your platform renew command, check the cable or Wi-Fi link, reboot the router if needed, and ensure the device is set to obtain an IP automatically rather than a bad static address. Once DHCP responds, a normal address replaces the 169.254 one.

Q: What is APIPA (Automatic Private IP Addressing)?

APIPA is the Microsoft name for the IPv4 link-local mechanism standardized in RFC 3927. When DHCP is unavailable, the operating system automatically assigns itself an address from 169.254.0.0/16 so that devices on the same link can still communicate, even though there is no internet connectivity.

Q: Is 169.254.x.x a private IP address?

Not in the usual sense. 169.254.x.x is a link-local address from RFC 3927, which is a different reservation from the RFC 1918 private ranges like 192.168.x.x. Private addresses are handed out by DHCP and routed to the internet through NAT, while a 169.254 address is self-assigned when DHCP fails and never reaches the internet.

~/sheets/what-is-apipa.md

The Address Your Device Gives Itself When Nothing Else Works
If your IP address starts with 169.254, your device did not get an address from the network. It assigned one to itself. This is an IPv4 link-local address, which Microsoft calls APIPA (Automatic Private IP Addressing), and it appears when DHCP fails to hand out an address. In practice a 169.254 address almost always means "connected to the network hardware, but no working internet."
You can confirm what public address, if any, the outside world sees for you with our IP Lookup or on the HackMyIP home page.
The 169.254.0.0/16 Range
IPv4 link-local addressing is defined in RFC 3927 and uses the block 169.254.0.0/16, which contains 65,536 addresses in total. The standard reserves the first 256 and the last 256 addresses, so the usable self-assignment pool is 169.254.1.0 through 169.254.254.255. A device picks a random candidate from that pool and checks that no one else on the link is already using it before claiming it.
Why It Means No Internet
A link-local address only works on the local link, the single physical or wireless segment your device is attached to. It can talk to other devices on the same link that also self-assigned a 169.254 address, but it cannot be routed to the wider internet, and no default gateway is configured. So a 169.254 address is best read as a symptom: the DHCP server, usually your router, did not give your device a real address, so the device fell back to talking only to itself and its immediate neighbors.
APIPA Is Not the Same as a Private IP
It is easy to confuse 169.254 addresses with the private ranges like 192.168.x.x, but they are different reservations. Private addresses (RFC 1918: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) are handed out by a working DHCP server and are routed within your network to the internet through NAT. A 169.254 link-local address (RFC 3927) is self-assigned precisely because that did not happen, and it never reaches the internet.
How to Fix a 169.254 Address
The goal is to get DHCP working again. Check that your router or DHCP server is powered on and reachable, then renew the lease by reconnecting the network or running your platform's renew command. Verify the cable or Wi-Fi link is solid, reboot the router if needed, and make sure the device is set to obtain an address automatically rather than a bad static IP. Once DHCP responds, the 169.254 address is replaced with a normal private address and internet access returns.
Frequently Asked Questions
What does a 169.254 IP address mean?
It means your device self-assigned an IPv4 link-local address because it could not get one from DHCP. Microsoft calls this APIPA. The address works only on your local network segment and cannot reach the internet, so a 169.254 address is a sign that the DHCP server, usually your router, did not give your device a real address.
Why is my IP address 169.254 and I have no internet?
Because a 169.254 link-local address is only valid on the local link and has no route to the internet and no default gateway. Your device fell back to it after DHCP failed, so it can reach other devices on the same segment but nothing beyond. Restoring a working DHCP lease is what brings internet access back.
How do I fix a 169.254 IP address?
Get DHCP working again: confirm the router or DHCP server is on and reachable, renew the lease by reconnecting or running your platform renew command, check the cable or Wi-Fi link, reboot the router if needed, and ensure the device is set to obtain an IP automatically rather than a bad static address. Once DHCP responds, a normal address replaces the 169.254 one.
What is APIPA (Automatic Private IP Addressing)?
APIPA is Microsoft name for the IPv4 link-local mechanism standardized in RFC 3927. When DHCP is unavailable, the operating system automatically assigns itself an address from 169.254.0.0/16 so that devices on the same link can still communicate, even though there is no internet connectivity.
Is 169.254.x.x a private IP address?
Not in the usual sense. 169.254.x.x is a link-local address from RFC 3927, which is a different reservation from the RFC 1918 private ranges like 192.168.x.x. Private addresses are handed out by DHCP and routed to the internet through NAT, while a 169.254 address is self-assigned when DHCP fails and never reaches the internet.
Last updated: April 2026