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's 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.
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.
Related 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
