Uptime troubleshooting

When your site goes Down or Slow, every second counts. This section tells you what's happening and how to put it right.

If you're not sure what you're looking at, the site is down page helps you match your symptom to the specific issue.

Connection issues

Problems where the request never reaches your server.

Connection refused — the server actively rejected the connection. Usually a stopped web server, firewall rule, or the server binding to localhost only.
Connection timeout — nothing replied within the timeout window. Usually server overload, a deadlocked process, or a network black hole.
DNS resolution failed — the domain couldn't be resolved to an IP address. Could be an expired domain, missing records, or a nameserver problem.

Problems where the server responds but with an error code.

HTTP 4xx response — the server rejected the request. Common causes are authentication requirements on the checked URL, WAF rules, or a moved page.
HTTP 5xx response — the server returned an error. Covers 500 application crashes, 502/504 upstream failures, and 503 service unavailable.

Problems where the site loads but is too slow.

Site responding slowly — DomainDash shows the site as Slow. Guides you through finding the bottleneck, whether it's DNS, the server, or content delivery.

Site is down — a routing page from the user-facing symptom to the specific issue causing it.