Why does my IP start with 169.254? (APIPA fix)
If your device shows an IP address starting with 169.254, it means your computer couldn’t get a proper address from your router and assigned itself a fallback. The short version: your device can’t talk to the router right now, so it isn’t really on the network. Here’s what that means and how to fix it.
What is a 169.254 address?
A 169.254.x.x address is a link-local address, assigned automatically by your operating system through a mechanism called APIPA (Automatic Private IP Addressing). Your device normally gets its local IP from the router’s DHCP server. When it asks and gets no answer, it falls back to 169.254.x.x so it at least has an address — but this address can’t reach the router or the internet. It’s the network equivalent of a dial tone that never connects.
Why did my device assign itself this address?
It happens whenever the device can’t reach the DHCP server. The usual causes are a loose or unplugged Ethernet cable, a Wi-Fi connection that authenticated but isn’t fully working, a router that needs restarting, or a DHCP service on the router that has stopped handing out addresses. It’s almost always a local link problem between your device and your router — not an outage with your internet provider.
How do I fix a 169.254 address?
Work through these in order — most cases are fixed by the first two:
- Check the physical connection. Reseat your Ethernet cable at both ends, or turn Wi-Fi off and back on. A loose cable is the single most common cause.
- Restart your router. Power it off at the wall, wait 30–60 seconds, and turn it back on. This restarts the DHCP service that hands out addresses.
- Release and renew your address. Once the router is back, tell your device to ask for a fresh address (commands below).
- Restart the device. If it still shows 169.254, reboot the computer or phone — this re-runs the whole connection process cleanly.
Commands to release and renew your address
Run the commands for your system after the router is back online. These ask your device to request a new address from the router:
Windows (Command Prompt):
ipconfig /release
ipconfig /renew
macOS / Linux (Terminal):
sudo dhclient -r && sudo dhclient (Linux)
sudo ipconfig set en0 NONE && sudo ipconfig set en0 DHCP (macOS)
If you now get a normal address — one starting with 192.168, 10., or 172.16 — you’re back on the network. See how to check your IP on any device to confirm.
When it keeps coming back
If the address returns to 169.254 after every fix, the problem is usually one of: a failing cable or port (try a different cable/port), the router’s DHCP server disabled or its address pool exhausted (check the router admin page — see how to log in to your router), or a network adapter driver issue on the device. On a managed or office network, DHCP may be restricted — ask whoever runs it. As a stopgap you can set a manual static IP in your device’s network settings, but fixing DHCP is the proper solution.
Is 169.254 a security risk?
No. A link-local address is harmless in itself — it just means you’re not connected. It can’t be reached from the internet (it’s in a non-routable range), so there’s nothing to worry about from a privacy or security angle. The only “problem” it signals is that your connection to the router is down.
Related: Find your IP on any device · Log in to your router · What private IP ranges mean