How to Fix ERR_CONNECTION_TIMED_OUT in Chrome (2026)

By /

ERR_CONNECTION_TIMED_OUT is Chrome’s way of telling you that it successfully found the website’s IP address, started trying to connect — and then gave up waiting because the server never responded. Unlike DNS errors where the domain can’t be found, a timeout means Chrome found the destination but couldn’t establish a connection to it.

What Does ERR_CONNECTION_TIMED_OUT Mean?

When Chrome connects to a website, it goes through several steps:

  1. DNS lookup (translate domain to IP) — this worked, otherwise you’d see a DNS error
  2. TCP connection (three-way handshake to establish the connection) — this is what timed out
  3. TLS handshake (for HTTPS sites)
  4. HTTP request and response

The connection timed out at step 2. Chrome sent a SYN packet to initiate the TCP connection and the server either never responded, or a firewall silently dropped the packet before it reached the server. After waiting several seconds, Chrome shows ERR_CONNECTION_TIMED_OUT.

Common Causes

  • The website’s server is down or overloaded
  • Your firewall or antivirus is blocking the connection
  • Your router has a stale or stuck connection state
  • A proxy is misconfigured
  • Your ISP is blocking or throttling the connection to that server
  • A VPN is routing the connection poorly

Fix 1: Check if the Site Is Down

Before troubleshooting your end, verify the problem isn’t with the website itself:

  • Try downforeveryoneorjustme.com
  • Use the DNS Checker to verify the domain resolves correctly — if DNS lookup fails, it’s a DNS problem, not a timeout
  • Try on mobile data — if it loads, the problem is on your home network

Fix 2: Restart Your Router

A router with a stuck or exhausted NAT table will drop new outbound connections, causing timeouts. Restarting it clears all state:

  1. Unplug from power, wait 30 seconds
  2. Plug back in, wait for all lights to stabilize
  3. Try Chrome again

Fix 3: Flush DNS and Reset Network Stack

Open Command Prompt as Administrator and run each command:

  1. ipconfig /flushdns
  2. netsh winsock reset
  3. netsh int ip reset
  4. ipconfig /release
  5. ipconfig /renew
  6. Restart your computer

This clears DNS cache, resets the network stack, and gets a fresh IP from your router.

Fix 4: Disable Firewall and Antivirus Temporarily

Your firewall or antivirus may be blocking the connection to that specific server. Test by temporarily disabling them:

  1. Temporarily disable Windows Defender Firewall (Settings → Windows Security → Firewall)
  2. Pause your antivirus real-time protection
  3. Try loading the site
  4. If it loads, add the site to your security software’s whitelist, then re-enable protection

Fix 5: Check Proxy Settings

A misconfigured proxy causes connection timeouts for all sites or specific ones depending on proxy rules:

  1. Chrome → Settings → System → Open your computer’s proxy settings
  2. Windows: Settings → Network → Proxy → turn OFF “Use a proxy server” unless you intentionally configured one
  3. Restart Chrome and test

If your proxy settings were changed without your knowledge, scan for malware — this is a common sign of browser hijacking. See our guide on ERR_PROXY_CONNECTION_FAILED for more detail.

Fix 6: Change Your DNS Server

While DNS itself isn’t the cause of a timeout, a slow DNS resolver can make Chrome time out before the connection even starts properly. Switch to Google (8.8.8.8) or Cloudflare (1.1.1.1) in your network adapter settings.

Verify DNS resolution is working with the DNS Checker tool — enter the domain and confirm both Google and Cloudflare DNS resolve it correctly.

Fix 7: Use a VPN to Route Around the Problem

If your ISP is blocking or throttling connections to specific servers, a VPN bypasses this entirely by routing your traffic through a different network path:

  1. Connect to PureVPN or IPVanish
  2. Try loading the site again
  3. If it works through the VPN, your ISP is blocking or throttling the route to that server

This is especially effective if the timeout only happens on specific sites, or only at certain times of day (peak hours throttling).

ERR_CONNECTION_TIMED_OUT vs Related Errors

  • ERR_CONNECTION_TIMED_OUT: Server found, connection attempt made, no response received. Could be server-side or network blocking.
  • ERR_CONNECTION_REFUSED: Server found, connection attempt made, server actively rejected it. Usually a firewall or no service running on that port.
  • DNS_PROBE_FINISHED_NXDOMAIN: DNS lookup failed, domain not found. Fix: How to fix DNS_PROBE_FINISHED_NXDOMAIN.
  • ERR_INTERNET_DISCONNECTED: No internet connection at all.

Quick decision tree: Site down globally? Wait. Mobile data works but not home Wi-Fi? ISP blocking — use VPN. All sites timing out? Restart router and run network reset commands. Specific sites only? Firewall, antivirus, or ISP throttling.

Frequently Asked Questions

Why does ERR_CONNECTION_TIMED_OUT happen on only one website?

Site-specific timeouts usually mean that server is down, overloaded, or your ISP is throttling/blocking it. Test with a VPN to distinguish between server-side and ISP-side causes.

Can ERR_CONNECTION_TIMED_OUT fix itself?

Yes, if the cause is a temporarily overloaded server. Wait a few minutes and try again. If the cause is a router issue or network stack problem, it won’t fix itself without the steps above.

Does this error mean my IP is blocked by the website?

A blocked IP typically results in ERR_CONNECTION_REFUSED (active rejection), not a timeout. A timeout is more likely a server availability or routing issue. However, some firewalls block by silently dropping packets rather than refusing — in that case, yes, a timeout can indicate an IP block.

Scroll to Top