169.254 IP address: APIPA, link-local, and how to fix it

Short answer

A 169.254.x.x address is usually an IPv4 link-local address selected automatically when a device cannot obtain usable configuration through DHCP. It permits limited communication with devices on the same link, but routers must not forward it and it normally provides no Internet access.

The range that is actually used

RFC 3927 reserves 169.254.0.0/16 for IPv4 Link-Local addressing. Dynamically selected addresses run from 169.254.1.0 through 169.254.254.255; the first and last /24 of the block are reserved for future use.

Before claiming an address, a device uses ARP to check that it is not already in use. If it detects a conflict, it selects another one. This automatic configuration does not make the device a member of the normal home or office subnet.

What works and what does not

Two devices on the same physical segment or broadcast domain can communicate using link-local addresses. A router must not forward those packets to another network. A local printer may therefore respond even while public websites do not load.

The IPv4 subnet calculator can display the range for 169.254.0.0/16, but it cannot diagnose a DHCP server or prove that two devices are attached to the same link.

A troubleshooting sequence

1. Check the physical or Wi-Fi link: cable, access point, and association.
2. See whether other devices receive a normal address from the router.
3. Confirm that the client is configured for DHCP if that is the network policy.
4. Renew the lease or cycle the interface after repairing the link.
5. Check that the DHCP pool has free addresses and that no VLAN or filter blocks its messages.
6. For a statically configured network, obtain the correct address, prefix, gateway, and DNS values instead of copying another device’s settings.

The name APIPA is especially common in Microsoft products, while the standard uses the term IPv4 Link-Local.

Common misunderstandings

• It is not one of the RFC 1918 private ranges.
• It is not a public address and must not be advertised on the Internet.
• Changing DNS alone does not fix a missing DHCP lease.
• Manually choosing another address without knowing the subnet can create a conflict.
• Seeing 169.254 does not prove the router is faulty; the cause can be the link, client, VLAN, DHCP relay, or server capacity.

After normal configuration returns, verify that the address, mask, and gateway match the intended design and that a default route exists again.