169.254.x.x: What a 169.254 IP Address Means
Why your device gave itself a 169.254 address, how to get a working one back, and when 169.254 is normal.
A 169.254.x.x address means your device asked the router for an address and got no answer, so it gave itself one. It's called a link-local address (APIPA on Windows, "Self-assigned IP" on a Mac), and it can't reach the internet. Restarting the router, reconnecting and renewing the address fixes it in most cases.
What kind of address is it?
Examples:
Runs in your browser; nothing is sent. Where to see it: Windows ipconfig ("Autoconfiguration IPv4 Address"), Mac System Settings › Network, phone Wi-Fi details.
Why Your Device Has a 169.254 Address
Every device asks the router for an address when it connects (DHCP); if nothing answers, it picks a 169.254 address itself so it can at least talk to the devices next to it.
| Cause | Signs |
|---|---|
| The router or its DHCP service is stuck | Several devices fail at once; fixed by restarting the router |
| Bad cable, port or Wi-Fi link | One device fails; a weak signal, a wrong Wi-Fi password or a loose cable |
| The router has no addresses left | New devices fail, old ones work; many devices or a small address range |
| A setting on the device | A manual (static) address, a VPN, a firewall or security app, or a network driver problem |
| No DHCP on the network at all | A cable straight between two computers, or a printer or camera set up without a router |
Windows keeps asking for an address in the background every five minutes, so a device can recover on its own once the router answers.
How to Fix a 169.254 IP Address, in Order
Test after each step: the first three solve most cases.
- Restart the router and the device. Unplug the router for 30 seconds; restart the computer, phone or printer.
- Check the connection. Try another cable or router port; on Wi-Fi, forget the network and join it again with the right password, closer to the router.
- Ask for a new address. Windows (Command Prompt):
ipconfig /releasethenipconfig /renew. Mac: System Settings › Network › your connection › Details › TCP/IP › Renew DHCP Lease. - Make sure the device is set to automatic. In its network settings, the address should come "automatically" or "using DHCP", not be typed in by hand.
- Turn off the VPN, firewall or security app for a moment, then test again.
- Check the router. On its page (find its address), make sure the DHCP server is on and its range is big enough (for example 192.168.1.100 to 192.168.1.199); remove old devices from the list.
- Reset the network stack or driver. Windows:
netsh winsock resetandnetsh int ip resetas administrator, then restart; or reinstall the adapter in Device Manager.
Steps for Your System
The steps for the system you're using are open below.
Windows 10 and 11 "Autoconfiguration IPv4 Address"
- Run
ipconfig: an "Autoconfiguration IPv4 Address" of 169.254.x.x confirms it. - Run
ipconfig /release, thenipconfig /renew. "Unable to contact your DHCP server" means the router isn't answering. - Settings › Network & internet › your connection › IP assignment › Edit › Automatic (DHCP).
- Settings › Network & internet › Advanced network settings › Network reset, if nothing else works.
Mac "Self-assigned IP"
- System Settings › Network shows a yellow dot and "Self-assigned IP" next to the connection.
- Turn Wi-Fi off and on, then Details… › TCP/IP › Configure IPv4: Using DHCP › Renew DHCP Lease.
- Forget the network (Details… › Forget This Network) and join it again.
- Check VPN and filter apps: System Settings › VPN (in the sidebar).
iPhone and iPad
- Settings › Wi-Fi › ⓘ next to your network: a 169.254 address under IPv4 confirms it.
- Tap Renew Lease, or Forget This Network and join it again.
- Still failing: Settings › General › Transfer or Reset iPhone › Reset › Reset Network Settings.
Android
- Forget the Wi-Fi network and join it again; check that IP settings are DHCP, not Static (network › Advanced).
- Turn off "Private DNS" (what it is) or a VPN app for a moment to test.
- Still failing: Settings › System › Reset options › Reset Bluetooth & Wi-Fi (older Android: Reset Wi-Fi, mobile & Bluetooth; names vary by brand).
Printers, cameras and other devices
- Restart the device and the router; check its cable or its Wi-Fi setup in its own menu.
- If it keeps a 169.254 address, connect to it with the maker's setup app, or give it a fixed address that fits your network.
- Better: reserve an address for it in the router (DHCP reservation), so it always gets the same one.
When a 169.254 Address Is Normal
On a network with no router, link-local addresses are how devices find each other, and that's by design.
- Two computers joined by one cable: both give themselves a 169.254 address and can share files directly.
- Setting up a device: some printers, cameras and storage drives use 169.254 until they join your network.
- A second network adapter that isn't connected to anything (a virtual or unused one) often shows 169.254: ignore it if your main connection has a normal address.
- Cloud servers: 169.254.169.254 and other 169.254 addresses provide services inside the cloud (below).
IPv6 does the same thing with addresses starting with fe80::: every device has one alongside its normal address, so seeing
one isn't a problem.
169.254.169.254: The Cloud Metadata Address
Inside a cloud server, 169.254.169.254 is the instance metadata service: programs ask it for the server's name, network settings and temporary credentials.
- AWS, Microsoft Azure, Google Cloud (also as
metadata.google.internal), Oracle Cloud and DigitalOcean all use it. - It only answers from inside the server itself; nobody can reach it from the internet or from a home network.
- It's a known target: a web application tricked into fetching URLs for an attacker (server-side request forgery) can leak the server's credentials. Clouds now protect it with tokens or required headers (AWS IMDSv2, Google's Metadata-Flavor header, Azure's Metadata header).
How Link-Local Addresses Work
RFC 3927 reserves 169.254.0.0/16 for addresses a device chooses itself, checks that no neighbour uses, and only uses on its own link.
| Range | 169.254.0.0/16 (mask 255.255.0.0) |
|---|---|
| Chosen from | 169.254.1.0 to 169.254.254.255 (the first and last 256 are reserved) |
| How | The device picks one at random and asks the network (ARP) whether anyone already uses it; if so, it picks another. |
| Reach | The same cable or Wi-Fi only: routers never forward it. |
| Names | Link-local, APIPA (Microsoft, since Windows 98), Self-assigned IP (Apple), Auto-IP / Zeroconf |
| DHCP | The normal way to get an address (RFC 2131); a device on 169.254 keeps trying it in the background. |
| IPv6 equivalent | fe80::/10 |
Check any address with our public or private IP checker, and see every special range in Public vs Private IP.
Frequently Asked Questions
What is a 169.254 IP address?
Why is my IP address 169.254?
How do I fix a 169.254 IP address?
Is 169.254 a private IP?
What is 169.254.169.254?
Can I ping a 169.254 address?
Next steps