Fix ERR_CONNECTION_TIMED_OUT: 5 Steps That Work

Quick answer: Restart your router, flush DNS, disable proxy, check firewall rules — do them in that order. 80% of the time it's one of those.

This error shows up when your browser sends a request but nothing comes back within a set time — Chrome waits 30 seconds by default, then gives up. The server might be down, your network might be blocking the route, or something on your machine is eating the request. Don't assume it's the website; most of the time it's local.

Fix 1: Restart Your Router and Modem

I know it's cliché, but routers are small Linux boxes that accumulate memory leaks and corrupted NAT tables. Here's the correct order:

Power off the router and modem (if separate).
Wait 30 seconds.
Power on the modem, wait for all lights to sync.
Power on the router, wait for it to fully boot.
Try the site again.

If you're on a corporate network, skip this — you can't restart the core switch. Call IT.

Fix 2: Flush DNS and Reset Winsock

A corrupted DNS cache is a classic cause. It holds stale IP addresses that point nowhere. Clear it:

ipconfig /flushdns
ipconfig /registerdns
netsh winsock reset
netsh int ip reset

Run those in an elevated Command Prompt (Run as Administrator). Then reboot. Don't skip the reboot — the Winsock reset needs it to take effect.

Fix 3: Kill Proxy Settings

If you've ever installed a VPN or a privacy tool, it can leave a system proxy that goes nowhere. Check your proxy settings:

Windows: Settings → Network & Internet → Proxy.
Turn off "Use a proxy server" unless you know you need it.
Mac: System Preferences → Network → Advanced → Proxies.

This is the one people forget. I've seen proxies lingering after uninstalling software for years.

Fix 4: Check Firewall and Antivirus

Your firewall might be silently dropping outgoing packets — especially to certain IP ranges. Temporarily disable Windows Defender Firewall or any third-party suite (just for testing, not permanently). If the site loads with the firewall off, you've found the culprit.

Also check for any "network protection" features in your antivirus — they can act like a mini-firewall. Add the site to exceptions if it's legitimate.

Fix 5: Switch DNS to a Public Resolver

Your ISP's DNS is often slow or broken. Use Google or Cloudflare instead:

netsh interface ip set dns name="Local Area Connection" static 8.8.8.8
netsh interface ip add dns name="Local Area Connection" 8.8.4.4 index=2

Or set it in router settings so all devices benefit. Cloudflare's 1.1.1.1 is also solid. If DNS was the issue, you'll notice the difference immediately.

When None of That Works

If you've done all five and still get the timeout, try these:

Ping the domain to see if it resolves: ping example.com. If it fails, but pinging the IP works, it's DNS.
Traceroute to find where the packets stop: tracert example.com. If they die at your gateway, it's your router. If they die mid-path, it's your ISP or the site's host.
Test with another device on the same network. If that works, it's your machine. If it also times out, it's the network or the site.

Prevention Tips

After you fix it, stop it from coming back:

Reboot your router weekly — yes, really. Set a calendar reminder.
Keep your network drivers up to date. Check the manufacturer's site, not Windows Update.
Make sure your system time is correct. SSL handshakes fail if your clock is off by even minutes — that shows up as an SSL error, but sometimes it masquerades as a timeout.

In my 14 years, I've seen this error a hundred times. It's almost always DNS or proxy, rarely a real dead website. Fix it methodically and you'll be back online in ten minutes.