Browser & network errors

    ERR_ADDRESS_UNREACHABLE: The IP address cannot be reached

    Also searched as: net::ERR_ADDRESS_UNREACHABLE · address unreachable · EHOSTUNREACH

    Is ERR_ADDRESS_UNREACHABLE happening on your domain?

    The DNS lookup shows every A and AAAA record returned, which is where a private or stale address becomes immediately obvious.

    Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.

    Short answer

    DNS returned an address and the network has no route to it. Common when a DNS record points at a private, retired, or IPv6 address the client cannot reach.

    What ERR_ADDRESS_UNREACHABLE means

    The failure is at the routing layer, before any service is involved. The browser knows where to go and the network says it cannot get there.

    Causes and fixes, most likely first

    most common

    The A record points at a private or stale IP address.

    Update the DNS record to the server's current public address. Private ranges are unreachable from the internet by design.

    common

    An AAAA record exists but IPv6 is broken on the path.

    Verify IPv6 connectivity end to end, or remove the AAAA record until it works. A half-configured AAAA breaks only IPv6-capable visitors, which makes it easy to miss.

    How to stop it happening again

    • •Monitor over both IPv4 and IPv6 if AAAA records are published — otherwise half the failure surface is invisible.

    Frequently asked questions

    Why does it work for some people and not others?

    Usually a broken AAAA record: IPv6-capable clients try the unreachable address while IPv4-only clients succeed.

    Related errors

    Monitor this continuously with LemWatch

    A one-off err_address_unreachable monitoring shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

    Last verified: by the Lemwatch research team.