Home / Learn / Host unreachable (no route)

NET Reachability failure: opens an incident

Host unreachable (no route)

There was no network path to the server at all.

What it usually means

There was no network route to the host at all. Usually a firewall rule, a withdrawn route, or a server that is switched off.

What to check first

How ErrorDetector reports it

This is a reachability failure. The check is repeated immediately to rule out a blip; once confirmed, an incident opens with this cause on it, every channel on the monitor is alerted, and the outage counts against uptime until the next successful check closes the incident.

Caught by: httpkeywordapipingportdns monitors. Read about the incident management feature.

Get the cause, not a red dot

Ten monitors free, no card, no time limit. Every incident names the failure.

Start monitoring free

Other causes