This means your browser tried to reach the site and got no reply in time. Unlike NXDOMAIN (DNS), the name resolved — the connection itself stalled. Here is how to fix it.
Quick answer
ERR_CONNECTION_TIMED_OUT means the domain resolved but the connection got no reply. If only one site fails, the problem is that site or its server; if everything fails, restart your router. Turn off any VPN or proxy, flush your DNS cache, and try another network to see whether the problem is on your side.
Step 1: is it just this site?
If other sites load fine, the problem is that site or the path to it. If everything times out, it's your connection — restart your router and check other devices.
Step 2: clear the local culprits
- Disable a VPN/proxy that may be stalling or blocked.
- Flush DNS and clear the browser cache.
- Turn off a firewall/antivirus temporarily to test.
- Try another browser or an incognito window (rules out extensions).
Step 3: test the route to the site
See where it stalls with a ping/traceroute to the domain:
ping example.com
tracert example.com # Windows (traceroute on Linux/macOS)Step 4: if it's the server
If everyone times out, the site's server is down or its firewall is dropping traffic. For a server you own, confirm the web server is running and the firewall allows 80/443 — see origin/firewall checks.
Timed out = no reply (the name resolved). Check if it's only one site, clear VPN/DNS/cache, then traceroute to find where it stalls.
Step 5: check for an IP block or rate limit
If you were rate-limited or blocked — by the site's firewall, a WAF, or even your own ISP's filtering — rather than the server being down, the symptom looks identical: a stall with no response. Try from a different network (mobile data) to see if the block is IP-specific.
How to prevent connection timeouts
- Keep your router firmware and DNS settings up to date.
- Avoid unreliable free VPNs/proxies for anything you rely on daily.
- For your own server, whitelist your monitoring/uptime checker's IP if you run aggressive rate limiting.
- Keep firewall rules on your server reviewed so a tightening change doesn't silently block real visitors.
Related errors
This is different from DNS_PROBE_FINISHED_NXDOMAIN — that means the name never resolved, while a connection timeout means it resolved but nothing answered. If it's your own server that visitors can't reach, also check packet loss and 502 Bad Gateway if the server does sometimes respond.