Fix "ERR_CONNECTION_TIMED_OUT" in Your Browser
ERR_CONNECTION_TIMED_OUTtook too long to respondthis site can't be reachedThis 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.
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.
A server that stays reachable
Host on our well-peered, protected Frankfurt network — stable routes and low latency across Europe.
Frequently asked questions
What does ERR_CONNECTION_TIMED_OUT mean?
Your browser resolved the domain but couldn't get a response in time. The connection stalled — usually a network issue on your side, a VPN/firewall, or the server being down or blocking you.
How do I know if it's my internet or the website?
If other sites load, it's that site or the route to it. If everything times out, it's your connection — restart the router and test another device. A traceroute shows where it stalls.
How is this different from NXDOMAIN?
NXDOMAIN means the domain didn't resolve at all (a DNS problem). A connection timeout means the name resolved but the server never replied — a connectivity or firewall problem.
Can my ISP cause ERR_CONNECTION_TIMED_OUT for one specific site?
Yes — some ISPs throttle, filter or route around certain destinations, especially under legal blocks or aggressive traffic shaping. If the site works over mobile data or a VPN but not your home connection, that points to ISP-level filtering.
Does ERR_CONNECTION_TIMED_OUT mean the site is hacked?
No — it just means no response arrived in time. That's almost always a network, firewall or server-availability issue, not a sign of compromise. A hacked site usually still loads, just with unexpected content.
How long does a browser wait before showing this error?
It varies by browser, typically around 20-30 seconds for the initial TCP connection attempt. If the server is simply slow to generate a response after connecting, that's a different symptom — a 504 Gateway Timeout — rather than a connection timeout.
Go deeper on this
Guides and explainers that pair with this fix — from our guides and blog.
What Is Ping, and How Do You Lower It?
What causes high ping and the practical ways to reduce it.
ReadWhat Is a DDoS Attack?
How DDoS works, the main types, and what actually stops it.
ReadProtect Your Game Server From DDoS
What real protection looks like, and what you can do yourself.
ReadGame Server Lag: CPU or Network?
How to tell which one is hurting you, and how to fix each.
ReadRelated articles
How to Port Forward for a Game Server (and Why You Might Not Need To)
How to port forward a home game server — the steps, the ports, and why CGNAT can block it.
Read fix NetworkingFix "Connection Timed Out" When Joining a Game Server
"Connection timed out" joining a server? How to tell whose side it is — and fix it.
Read fix NetworkingWhat Causes Packet Loss in Games (and How to Fix It)
Rubber-banding and warping is packet loss, not lag. What causes it, how to test, and how to fix it.
Read fix
