If your computer is showing an IP that starts with 169.254., you have an APIPA address. It's not a real working address — it's a sign that something went wrong with DHCP. Here's what's happening and how to fix it.

What APIPA is

APIPA stands for Automatic Private IP Addressing. When your device asks the network's DHCP server for an IP and gets no answer, the OS assigns itself an address from the reserved 169.254.0.0/16 range as a fallback. This lets devices on the same broken network at least find each other.

What it actually means

Your device is connected to a network but couldn't get a normal address. You'll have no internet, often no LAN access either. On a Mac this is also called "self-assigned IP." On Windows, ipconfig will show 169.254 with subnet mask 255.255.0.0.

Common causes

• Router or modem isn't responding (try power-cycling)
• DHCP server is down or out of leases
• Wi-Fi is connected but authentication never finished
• Network cable is loose or damaged
• Antivirus or VPN software interfering with the network stack
• Stuck IP lease that won't release

How to fix it

1. Power-cycle: unplug the router for 30 seconds, plug back in, wait 2 minutes.
2. Forget & rejoin Wi-Fi.
3. Renew the lease: Windows: ipconfig /release then ipconfig /renew. Mac: System Settings → Wi-Fi → Details → TCP/IP → Renew DHCP Lease.
4. Disable VPN/antivirus temporarily to rule out interference.
5. Try a different cable / port / network to isolate hardware vs software.

Full deep-dive in our release-and-renew guide.

When 169.254 is intentional

Some industrial and IoT setups use APIPA on purpose for ad-hoc device-to-device communication. If you're doing that, the address is normal. For everyone else, it's a warning sign.

Try it now

Curious what your IP is showing the world right now? Check your IP address & location instantly with our free tool — no signup, nothing stored. Or trace any other IP to see its geolocation, ISP, and network details.