How do I fix a 169.254 address?

It means no DHCP server replied. Check the cable or Wi-Fi association, restart the router, then renew the lease with ipconfig /release and ipconfig /renew on Windows or sudo dhclient -r and sudo dhclient on Linux.

Can two devices with 169.254 addresses talk to each other?

Yes, if they are on the same link. That is the point of the range. It is how two laptops joined by one Ethernet cable can exchange files with no router present.

What is 169.254.169.254?

The instance metadata endpoint on AWS, Azure, Google Cloud, and most other providers. A virtual machine queries it to read its own configuration and credentials.

Is 169.254.0.0/16 the same as a private IP?

No. RFC 1918 private addresses are handed out by a working DHCP server and route within the network. Link-local addresses are self-assigned and never routed off the link.

169.254.0.0/16: IPv4 link-local

169.254.0.0/16 is the IPv4 link-local range defined by RFC 3927. A device picks an address from it by itself when no DHCP server answers. Windows calls this APIPA. A machine with a 169.254 address can talk to others on the same link but has no gateway and no internet access.

reserved169.254.0.0/16

Operated by Reserved by IANA, defined in RFC 3927.

Live data

Fetched now, cached at the edge

Classification: reserved

Not a recognisable address. There is no registry entry, no reverse DNS and no reputation to look up for a reserved address, so this page shows the classification only.

Registry data from RDAP. Reverse DNS and blocklist checks over DNS-over-HTTPS. Run a full lookup on 169.254.0.0/16.

How a device chooses one

RFC 3927 describes the procedure. The host picks a pseudo-random address from 169.254.1.0 through 169.254.254.255, then sends ARP probes to see whether anyone else already has it. If someone answers, it picks again. The first and last /24 of the block, 169.254.0.0/24 and 169.254.255.0/24, are reserved by the RFC and must not be self-assigned.

The mechanism predates the RFC. Microsoft shipped Automatic Private IP Addressing in Windows 98, and Apple’s implementation is the reason a Mac with no DHCP still shows other Macs in Finder. The IETF standardised the behaviour in 2005.

What it tells you when you see it

A 169.254 address in ipconfig or ip addr is a diagnosis, not a configuration. It says the interface came up and the DHCP client gave up. The usual causes, in the order worth checking:

Layer 1: unplugged cable, dead switch port, Wi-Fi associated to the wrong SSID.
No DHCP server: the router is off, rebooting, or its DHCP service is disabled.
Exhausted DHCP pool: the scope is full, common on guest networks with a small range.
VLAN mismatch: the port is in a VLAN with no DHCP relay.
Firewall or security software on the client blocking UDP 67 and 68.

On Windows: ipconfig /release then ipconfig /renew. On Linux: sudo dhclient -r then sudo dhclient, or restart the relevant NetworkManager connection. On macOS: System Settings, Network, Details, TCP/IP, Renew DHCP Lease.

The cloud metadata address

169.254.169.254 is the one address in this range that almost every engineer meets deliberately. AWS, Azure, Google Cloud, Oracle Cloud, DigitalOcean, and OpenStack all expose instance metadata there. A virtual machine reads its hostname, its network configuration, its user data script, and in many cases short-lived credentials by making an HTTP request to it.

The address was chosen because it is link-local: it cannot be routed, so it cannot be reached from outside the instance. That property is also why server-side request forgery bugs are so dangerous on cloud hosts. An application that fetches a URL supplied by a user can be pointed at 169.254.169.254 and made to read credentials. AWS’s IMDSv2 added a token requirement specifically to make that harder.

IPv6 does the same thing, always

Every IPv6 interface has a link-local address in fe80::/10, defined in RFC 4291. The difference is that IPv6 treats it as normal rather than as a failure state. Neighbour discovery, router advertisements, and OSPFv3 adjacencies all run over link-local addresses while global addresses do their own work. An fe80: address on your interface is healthy; a 169.254 address usually is not.

What it is not

169.254.0.0/16 is not a private range you should configure by hand. It is not routable, so no static route or NAT rule will make it reach the internet. It is not the same as 100.64.0.0/10, which is a carrier NAT range your ISP assigns on purpose. And it is not a security problem in itself: a device that self-assigned an address is isolated, not exposed.

Questions people ask

How do I fix a 169.254 address?: It means no DHCP server replied. Check the cable or Wi-Fi association, restart the router, then renew the lease with ipconfig /release and ipconfig /renew on Windows or sudo dhclient -r and sudo dhclient on Linux.
Can two devices with 169.254 addresses talk to each other?: Yes, if they are on the same link. That is the point of the range. It is how two laptops joined by one Ethernet cable can exchange files with no router present.
What is 169.254.169.254?: The instance metadata endpoint on AWS, Azure, Google Cloud, and most other providers. A virtual machine queries it to read its own configuration and credentials.
Is 169.254.0.0/16 the same as a private IP?: No. RFC 1918 private addresses are handed out by a working DHCP server and route within the network. Link-local addresses are self-assigned and never routed off the link.

Last reviewed 2026-09-04. editorial