Guide

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

Learn why a device assigns itself a 169.254 IPv4 address, what link-local connectivity permits, and what to check when DHCP fails.

by Tools in a Tab · Published on 2026-08-09 · Reviewed on 2026-08-15

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.

What a 169.254 address means at a glance

If a laptop, phone, printer, or server unexpectedly shows 169.254.x.x, the address is a symptom rather than the original fault. The interface is up far enough to configure itself, but it has not received the normal IPv4 settings expected for that network.

What you see	What it usually means	Check next
`169.254.x.x` on one device	That client did not complete DHCP	Its cable, Wi-Fi association, and DHCP setting
`169.254.x.x` on several devices	A shared path to DHCP may be unavailable	Router, access point, VLAN, relay, or DHCP pool
A printer answers, Internet does not	Link-local communication works on one segment	The missing lease, gateway, and normal DNS setup
A manually assigned `169.254.x.x`	It may be intentional link-local use	The device or application documentation

The important distinction is whether the address was expected. An intentional link-local setup is valid; an unexpected one usually means the DHCP exchange or the path to the DHCP server failed.

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.

The block uses a /16 prefix, equivalent to the mask 255.255.0.0. That does not mean every device with a 169.254 address can necessarily reach every other one: they still need to share the same link, and local firewall or interface rules can block traffic.

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.

Confirm the diagnosis before changing settings

Inspect the complete interface configuration, not only the address:

On Windows, ipconfig /all shows whether DHCP is enabled and whether a DHCP server and lease are present.
On macOS, the Network settings panel shows the active service, configured IPv4 method, address, router, and DNS values.
On Linux, ip address shows the assigned addresses; NetworkManager systems can also use nmcli device show to inspect the active connection.

An unexpected 169.254 address together with no normal default gateway is a strong DHCP-failure signal. A normal address but missing DNS or a bad default route is a different problem and should not be diagnosed as APIPA.

A troubleshooting sequence

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

Renewing a lease is useful only after the underlying link or DHCP service is available. Repeating a renew command cannot repair a disconnected cable, wrong Wi-Fi network, exhausted pool, or blocked VLAN path.

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.

Frequently asked questions

Is every 169.254 address APIPA?

169.254.0.0/16 is the IPv4 Link-Local block. APIPA is Microsoft’s common name for automatic private addressing when a client cannot obtain a DHCP lease. An address from the block can also be assigned deliberately, so the address alone does not prove how it was configured.

Can a 169.254 address access the Internet?

Not through normal IP routing. IPv4 link-local packets remain on the local link, and routers must not forward them. A device may still communicate with a peer on that same link, which explains why a local printer can work while websites do not.

Should I replace it with a random 192.168 address?

No. 192.168.0.0/16 is private space, but the correct subnet, free address, prefix, gateway, and DNS settings depend on the actual network. Guessing can create an address conflict or place the device in the wrong subnet. Restore DHCP or obtain the approved static configuration instead.