How to fix ssh: connect to host hostname port 22: Host is down in SSH

SSHBEGINNERHIGHUpdated Jan 4, 2026· 234 views

The "Host is down" error occurs when SSH cannot reach the remote server at the network level. This indicates a network connectivity issue—the target host is unreachable, offline, or has network problems preventing any communication.

Quick fix

Fixes ssh: connect to host hostname port 22: Host is down

ssh user@correct-hostname.com
# or
ssh user@192.168.1.100
  1. Verify the hostname or IP address
  2. Test basic network connectivity with ping
  3. Check if the host is powered on
  4. Verify your network connection
ssh — error
ssh user@correct-hostname.com
# or
ssh user@192.168.1.100
ssh: connect to host hostname port 22: Host is down

What this error means

When SSH attempts to connect to a remote host, it first sends network packets (ICMP or TCP) to establish connectivity. The "Host is down" error means the SSH client received network-level confirmation that the target host is unreachable—either the host is powered off, disconnected from the network, or has a network interface problem. This is different from "Connection refused" (which means the host is up but SSH daemon isn't listening) or "Connection timed out" (where packets are being dropped). "Host is down" is a definitive network reachability problem.

Typical symptoms

  • ping command fails to the same hostname/IP
  • Error appears immediately without waiting for a response
  • All network connections to that host fail, not just SSH
  • Host was recently shut down or rebooted
  • Network cable is disconnected or interface is down
  • Host is on a different network and routes are broken

Common causes

  1. Remote host is powered off or shut down
  2. Remote host network interface is down or disconnected
  3. Network cable is unplugged from the host or switch
  4. Remote host lost power or experienced a hardware failure
  5. Routing path to the host is broken (missing routers, misconfigured firewall rules)
  6. Wrong IP address or hostname that doesn't exist on the network
  7. Host is on a different subnet and no gateway/router is configured between subnets
  8. DHCP server down and host didn't retain a static IP
  9. Network switch or router between you and the host is down
  10. ISP or WAN connection to the remote network is down

How to fix "ssh: connect to host hostname port 22: Host is down"

1Verify the hostname or IP address

Double-check that you're using the correct hostname or IP address:

bash
ssh user@correct-hostname.com
# or
ssh user@192.168.1.100

If you're not sure of the IP, try to resolve the hostname:

bash
ping hostname.com
nslookup hostname.com
dig hostname.com

If DNS resolution fails or returns an unexpected IP, that's your first problem. Verify the DNS records or use the known IP address directly.

2Test basic network connectivity with ping

Use ping to check if the host is reachable at the network level:

bash
ping -c 4 hostname.com
# or
ping -c 4 192.168.1.100

Expected output (host is up):

bash
PING hostname.com (192.168.1.100): 56 data bytes
64 bytes from 192.168.1.100: icmp_seq=0 ttl=64 time=15.234 ms

Expected output (host is down):

bash
PING hostname.com (192.168.1.100): 56 data bytes
(No response / Request timeout)

If ping fails, the host is genuinely unreachable and you need to resolve network connectivity before SSH will work.

3Check if the host is powered on

If you have physical access or can check the host status:

1. For cloud providers (AWS, Azure, GCP):
 - Log in to your cloud console
 - Check if the instance is running (not stopped or terminated)
 - Verify the instance has a public IP or is in the correct subnet

2. For physical servers:
 - Check if the server is powered on (look for power lights)
 - Verify network cable is plugged in
 - Check if it completed boot (may take 1-2 minutes after power on)

3. For remote machines you don't have access to:
 - Contact the server owner/administrator
 - Ask if the host is currently online
 - Request they check server logs or hardware status

4Verify your network connection

Ensure you have a working network connection:

bash
# Check if you have internet connectivity
ping 8.8.8.8  # Google's DNS server

# Check your routing table
netstat -rn  # Linux/Mac
route print  # Windows

# Check your network interfaces
ifconfig   # Linux/Mac
ipconfig   # Windows

If you can't reach external networks (like Google DNS), your local network is down or misconfigured. Fix that first.

5Check firewall rules and network routes

If the host is on the same local network but still unreachable:

bash
# Check ARP table to see if host is on the local network
arp -a

# If on same subnet, check firewall on your machine
# macOS:
sudo pfctl -sa

# Linux with UFW:
sudo ufw status

# Windows:
netsh advfirewall show allprofiles

If the host is on a different network:

bash
# Check your route to that network
# Trace the path packets take:
traceroute hostname.com  # Linux/Mac
tracert hostname.com     # Windows

# If traceroute stops at an intermediate router, that's where the break is

If a firewall is blocking the connection, configure it to allow SSH traffic (port 22 or custom SSH port) from your IP.

6Wait for the host to boot and retry

If the host was recently powered on, it may need time to fully boot:

bash
# Check once
ping hostname.com

# Wait 30-60 seconds for boot to complete
sleep 60

# Try again
ssh user@hostname.com

Cloud instances can take 1-3 minutes to be fully ready after starting. If you just launched an instance, wait a minute before trying SSH.

7Check with your cloud provider or network administrator

If the host should be online but isn't reachable:

1. Cloud instances (AWS, Azure, GCP):
 - Verify the instance status in the cloud console (should be "Running")
 - Check security groups allow inbound SSH (port 22)
 - Verify the instance has a public IP assigned
 - Check instance monitoring/logs for crashes

2. Data center or shared hosting:
 - Contact your hosting provider
 - Ask if the server is running
 - Check if there's a network issue affecting that data center
 - Request they restart the machine if it's hung

3. On your local network:
 - Ask the network administrator
 - Check if the subnet/VLAN is active
 - Verify the switch/router that connects to that host is working

Advanced notes

Advanced troubleshooting:

IPv4 vs IPv6: If you have both IPv4 and IPv6 addresses, try specifying the version explicitly:

bash
# Force IPv4
ssh -4 user@hostname.com

# Force IPv6
ssh -6 user@hostname.com

VPN/Proxy Connections: If connecting through a VPN or jump host, the issue could be on the intermediate hop:

bash
# Test connectivity through jump host
ssh -J jump-host user@target-host

# Or manually:
ssh user@jump-host
# Then from jump host:
ping target-host

Kubernetes/Container Networks: For containers, the "host is down" usually means:
- Container is not running: kubectl get pods -o wide
- Pod IP is stale: Check if pod was recently restarted
- Network policy is blocking traffic: Review NetworkPolicy objects

NAT/Port Forwarding: If using port forwarding:

bash
# Connect through forwarded port
ssh -p 2222 user@localhost

If the forwarding is broken, the host appears down even if it's actually reachable on the other side.

Cloud Metadata Services: Some cloud platforms require instance metadata service to be reachable. If that's down, instances may not boot properly. Check your cloud provider's instance logs.

Frequently asked questions

What does "ssh: connect to host hostname port 22: Host is down" mean?
When SSH attempts to connect to a remote host, it first sends network packets (ICMP or TCP) to establish connectivity. The "Host is down" error means the SSH client received network-level confirmation that the target host is unreachable—either the host is powered off, disconnected from the network, or has a network interface problem. This is different from "Connection refused" (which means the host is up but SSH daemon isn't listening) or "Connection timed out" (where packets are being dropped).
How do I fix "ssh: connect to host hostname port 22: Host is down"?
The "Host is down" error occurs when SSH cannot reach the remote server at the network level. This indicates a network connectivity issue—the target host is unreachable, offline, or has network problems preventing any communication.
What causes "ssh: connect to host hostname port 22: Host is down"?
Remote host is powered off or shut down Remote host network interface is down or disconnected Network cable is unplugged from the host or switch
Is the "ssh: connect to host hostname port 22: Host is down" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading