What Is 169.254.0.0/16? The Link-Local Address Range Explained
Seeing a 169.254.x.x address on your network interface is a sign that something went wrong with DHCP. This range — defined in RFC 3927 — is assigned automatically when no DHCP server is reachable.
If a Windows machine cannot reach a DHCP server, it assigns itself an address from the 169.254.0.0/16 range — a process Microsoft calls Automatic Private IP Addressing (APIPA). You will see it when a network cable is unplugged, a DHCP server is down, or a misconfigured VLAN blocks discovery traffic. It means the device has no usable IP address and cannot communicate beyond the local link.
What Link-Local Means
The 169.254.0.0/16 range is designated for link-local addressing — addresses valid only on the directly connected network segment. Routers do not forward link-local packets; they are strictly local. The range covers 169.254.0.0 through 169.254.255.255 and is defined in RFC 3927. Use the loopback and link-local guide for more detail on how these special-purpose ranges are defined.
APIPA: Windows Self-Assignment
When a Windows host starts up and sends DHCP discovery packets without receiving a response within a few seconds, it randomly selects an address from 169.254.1.0/16 to 169.254.254.255/16 (the first and last 256 addresses are reserved). It then performs ARP conflict detection to verify no other host is using the chosen address. The result is a machine with an IP address that cannot reach anything except other machines on the same segment that have also self-assigned from the same range.
169.254.169.254 — The Cloud Metadata Address
The address 169.254.169.254 has a special role in cloud computing: it is the well-known IP address for the instance metadata service in AWS, GCP, Azure, and most other cloud providers. Running curl http://169.254.169.254/latest/meta-data/ inside an EC2 instance returns instance metadata — the instance ID, type, region, IAM role credentials, and more. This address is only accessible from within the instance itself and is not exposed outside the VM. It is a feature, not a failure.
Diagnosing a 169.254.x.x Address
If a device has a 169.254 address when it should not:
- Check physical or wireless connectivity first
- Verify the DHCP server is running and reachable
- Check whether the correct VLAN is configured on the switch port
- Look at DHCP scope utilisation — the pool may be exhausted
- Release and renew:
ipconfig /release && ipconfig /renewon Windows,dhclient -r && dhclienton Linux
A 169.254 address is always a symptom of a DHCP failure, never a desired outcome in a production environment.