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.

CauseSigns
The router or its DHCP service is stuckSeveral devices fail at once; fixed by restarting the router
Bad cable, port or Wi-Fi linkOne device fails; a weak signal, a wrong Wi-Fi password or a loose cable
The router has no addresses leftNew devices fail, old ones work; many devices or a small address range
A setting on the deviceA manual (static) address, a VPN, a firewall or security app, or a network driver problem
No DHCP on the network at allA 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.

  1. Restart the router and the device. Unplug the router for 30 seconds; restart the computer, phone or printer.
  2. 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.
  3. Ask for a new address. Windows (Command Prompt): ipconfig /release then ipconfig /renew. Mac: System Settings › Network › your connection › Details › TCP/IP › Renew DHCP Lease.
  4. 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.
  5. Turn off the VPN, firewall or security app for a moment, then test again.
  6. 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.
  7. Reset the network stack or driver. Windows: netsh winsock reset and netsh int ip reset as 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"
  1. Run ipconfig: an "Autoconfiguration IPv4 Address" of 169.254.x.x confirms it.
  2. Run ipconfig /release, then ipconfig /renew. "Unable to contact your DHCP server" means the router isn't answering.
  3. Settings › Network & internet › your connection › IP assignment › Edit › Automatic (DHCP).
  4. Settings › Network & internet › Advanced network settings › Network reset, if nothing else works.
Mac "Self-assigned IP"
  1. System Settings › Network shows a yellow dot and "Self-assigned IP" next to the connection.
  2. Turn Wi-Fi off and on, then Details… › TCP/IP › Configure IPv4: Using DHCP › Renew DHCP Lease.
  3. Forget the network (Details… › Forget This Network) and join it again.
  4. Check VPN and filter apps: System Settings › VPN (in the sidebar).
iPhone and iPad
  1. Settings › Wi-Fi › ⓘ next to your network: a 169.254 address under IPv4 confirms it.
  2. Tap Renew Lease, or Forget This Network and join it again.
  3. Still failing: Settings › General › Transfer or Reset iPhone › Reset › Reset Network Settings.
Android
  1. Forget the Wi-Fi network and join it again; check that IP settings are DHCP, not Static (network › Advanced).
  2. Turn off "Private DNS" (what it is) or a VPN app for a moment to test.
  3. 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
  1. Restart the device and the router; check its cable or its Wi-Fi setup in its own menu.
  2. 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.
  3. 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).

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.

Range169.254.0.0/16 (mask 255.255.0.0)
Chosen from169.254.1.0 to 169.254.254.255 (the first and last 256 are reserved)
HowThe device picks one at random and asks the network (ARP) whether anyone already uses it; if so, it picks another.
ReachThe same cable or Wi-Fi only: routers never forward it.
NamesLink-local, APIPA (Microsoft, since Windows 98), Self-assigned IP (Apple), Auto-IP / Zeroconf
DHCPThe normal way to get an address (RFC 2131); a device on 169.254 keeps trying it in the background.
IPv6 equivalentfe80::/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?
An address a device gives itself when no router answers its request for one (DHCP). The range 169.254.0.0/16 is reserved for these link-local addresses: Windows calls them APIPA, a Mac shows "Self-assigned IP". The device can only talk to others on the same cable or Wi-Fi, not the internet.
Why is my IP address 169.254?
Your device asked the router for an address and got no answer: the router or its DHCP service is down or full, the cable or Wi-Fi link is bad (often a wrong Wi-Fi password or a weak signal), or something on the device (a static setting, a VPN, a security app, a driver) blocks the answer.
How do I fix a 169.254 IP address?
Restart the router and the device, check the cable or reconnect to Wi-Fi, then ask for a new address: on Windows run ipconfig /release and ipconfig /renew; on a Mac use Renew DHCP Lease; on a phone forget the Wi-Fi network and join it again. If the router's list of devices is full, remove old ones.
Is 169.254 a private IP?
Not an RFC 1918 private address, but like them it never goes on the internet. 169.254.0.0/16 is link-local: it only works on the cable or Wi-Fi the device is on, and routers don't forward it anywhere.
What is 169.254.169.254?
The address of the instance metadata service in cloud servers (AWS, Azure, Google Cloud and others): a program on a cloud server asks it for that server's settings and temporary credentials. It only answers from inside the server, never from a home network.
Can I ping a 169.254 address?
Only from a device on the same cable or Wi-Fi that also has a 169.254 address (or a route to that network). That's how two computers joined by one cable, with no router, can still reach each other.

Next steps

Related Tools

Public or Private IP
What kind of address is this?
IP Validator
Is this a valid IPv4 or IPv6 address?
What Is My ISP?
Your provider, once you're back online.

Related Guides

Guide Public vs Private IP
All the special address ranges.
Guide Find Your Router IP
To check its DHCP settings.
Guide DNS Server Not Responding
When you have an address but sites won't open.