- A 169.254.x.x address means your device asked for an IP and no DHCP server answered.
- Windows calls this APIPA. The device self-assigns a link-local address so it can talk on the local link only.
- With this address you have no gateway and no internet, even when Wi-Fi shows connected.
- Fix it on Windows with
ipconfig /releasethenipconfig /renew, and restart the DHCP Client service. - If that fails, reboot the router and check the cable or Wi-Fi link, then renew again.
- 169.254 is link-local (RFC 3927), not a private address. It is normal only on networks with no DHCP server.
You run ipconfig, expecting a normal address, and instead you see one that starts with 169.254. Your connection looks alive, but nothing loads. That number is the clue, and it points to a single cause.
A 169.254.x.x address is not random. It is a fallback your device assigns to itself when it cannot get a real address from the network. Once you know that, the fix is quick.
This guide explains what a 169.254.x.x address means and why DHCP hands it out. It then shows how to clear it on Windows, macOS, and Linux. It also covers the one case where the address is perfectly normal.
What a 169.254.x.x address means
A 169.254.x.x address is an IPv4 link-local address. Windows assigns it automatically through a feature called APIPA when no DHCP server replies. The device can talk on the local link only. It has no gateway and no internet, even though the network shows connected.
Normally your router runs a DHCP server. When a device joins, it asks for an address, and the router leases it one like 192.168.1.20. Our guide on public versus private IP addresses explains those normal ranges.
When that request gets no answer, the device cannot stay silent. It self-assigns an address from the 169.254 range so it can still reach others on the same link. Windows calls this Automatic Private IP Addressing, or APIPA.
The catch is that APIPA gives no default gateway. Without a gateway, traffic cannot leave the local network. That is why a 169.254 address always means no internet.
How to check if you have a 169.254 address
Before fixing anything, confirm the address. On Windows, run ipconfig in Command Prompt. On macOS or Linux, run ifconfig or ip address. If the IPv4 line begins with 169.254, the device never got a lease, and APIPA took over.
Open Command Prompt on Windows and run the command below. Look at the IPv4 Address line for your active adapter.
ipconfigYou can also check in seconds with our My IP Address tool, which shows the address your device is using. A healthy home address looks like 192.168.x.x or 10.x.x.x, not 169.254.x.x.
Why DHCP fails and hands out 169.254
A 169.254 address always traces back to one event: the DHCP request got no reply. The reasons range from a rebooting router to a loose cable to a full address pool. Knowing the common causes tells you where to look before you start changing settings.
The usual causes, in order
The router or DHCP server is down or rebooting. No server means no lease, so the device falls back to APIPA.
A physical problem. A loose Ethernet cable, a bad port, or a failed Wi-Fi join stops the request from reaching the server.
The DHCP pool is exhausted. If too many devices are connected, the router runs out of addresses to lease.
A stopped DHCP Client service. If the Windows service that requests addresses is not running, the device never asks.
A driver fault or a corrupted network stack can also block the request. Those are less common, but the network reset steps below clear them.
How to fix a 169.254 address on Windows
Start by forcing a fresh DHCP request. Release and renew the lease, then restart the DHCP Client service. If the address persists, reboot the router and reset the network stack. Work through these steps in order, and recheck the address after each one.
Release and renew the lease
Open Command Prompt as administrator and run these commands. The renew step asks the router for a new address.
ipconfig /release
ipconfig /renew
ipconfig /flushdnsRestart the DHCP Client service
Press Win + R, type services.msc, and find DHCP Client. Right-click it and choose Restart. This forces the address-request process to start fresh.
Reboot the router and check cabling
If the address stays at 169.254, power-cycle the router so its DHCP server restarts. Unplug it for 30 seconds, then power it back on. Confirm the Ethernet cable is seated, or that Wi-Fi joined the right network.
Reset the network stack as a last step
If nothing else works, the stack may be corrupted. Run the two commands below, then restart the computer.
netsh winsock reset
netsh int ip resetFix it on macOS and Linux
The fix is the same idea on every system: force the device to request a new lease. macOS does it through network settings or a single command. Linux uses the dhclient or NetworkManager commands. Renewing the lease clears the 169.254 address once a DHCP server answers.
macOS
Open System Settings → Network, pick your connection, then open Details → TCP/IP and click Renew DHCP Lease. You can also run a single command in Terminal.
sudo ipconfig set en0 DHCPLinux
Release and renew the lease with dhclient, or restart NetworkManager. Use the device name for your adapter in place of the example.
sudo dhclient -r
sudo dhclientWhen 169.254.x.x is actually normal
A 169.254 address is not always a fault. Link-local addressing is a real standard, used when two devices connect with no router and no DHCP at all. On those direct links, 169.254 is working as designed. On any network with a router, though, it still signals DHCP failure.
Link-local addressing is defined by RFC 3927. It lets devices on the same physical link reach each other without any central server. Some printers, cameras, and point-to-point cable links use it on purpose.
So the test is simple. If you connected two devices directly and expected no DHCP, 169.254 is fine. If you are on a normal home or office network and expected internet, it is a sign DHCP failed.
Related Tools & Resources
NetworkCheckr hosts free tools to confirm your address and trace a connectivity fault. Use the tools below to check what IP your device is using. The guides explain the broader problem behind a 169.254 address.
Frequently Asked Questions
Short answers to the questions people ask most about a 169.254 address. Each one expands on a point from the sections above. Together they cover what the address means, why it appears, and how it differs from a private IP.
What is a 169.254.x.x IP address?
It is an IPv4 link-local address, which Windows assigns automatically through a feature called APIPA. Your device gives itself this address when it uses DHCP but gets no reply from a DHCP server. The address only works on the local link. The device cannot reach the internet or most of the local network.
Why did my computer get a 169.254 address?
Because it asked for an IP address and no DHCP server answered. The usual reasons are a router that is down or rebooting, or a loose cable or failed Wi-Fi join. Others are an exhausted DHCP pool or a stopped DHCP Client service. The device then falls back to a self-assigned 169.254 address.
How do I fix a 169.254 IP address?
Release and renew the lease first. On Windows, run ipconfig /release then ipconfig /renew, and restart the DHCP Client service. If that fails, reboot the router so its DHCP server restarts, and check the cable or Wi-Fi connection. As a last step, reset the network stack and update the network driver.
Is 169.254.x.x a private IP address?
No. Private ranges are defined by RFC 1918, such as 10.x.x.x and 192.168.x.x, and a router hands those out. The 169.254 range is link-local, defined by RFC 3927, and a device assigns it to itself when DHCP fails. They look similar but mean very different things.
Does a 169.254 address mean my router is broken?
Not necessarily. It only means your device did not get a reply from the DHCP server. The router may simply be rebooting, the cable may be loose, or the DHCP pool may be full. Power-cycle the router and reconnect first. If only one device shows the address, the fault is usually that device.
What is APIPA?
APIPA stands for Automatic Private IP Addressing. It is the Windows feature that self-assigns an address from the 169.254 link-local range when no DHCP server responds. It lets devices on the same link talk to each other without a router. It provides no gateway and no internet access.
References
Primary sources for the link-local standard, the private address ranges, and the Windows commands described above. These cover the IETF specifications and the official documentation behind APIPA and DHCP. Each link points to a primary source.