Quick Answer: ERR_CONNECTION_TIMED_OUT means Chrome successfully started connecting to a server but the connection stalled partway through and never completed. It’s a close relative of ERR_TIMED_OUT, but points more specifically at a slow or unstable link to that one server rather than a broader DNS or network failure. Reloading, switching networks, and disabling VPN or proxy extensions resolve most cases.
What Causes This Error
- A slow or congested Wi-Fi connection that can’t sustain the handshake to that server
- A VPN or proxy extension adding enough latency to exceed Chrome’s connection timeout
- A firewall or content filter silently dropping packets instead of rejecting the connection outright
- The destination server being overloaded or geographically distant with high latency
- A stale connection stuck in your router’s connection table
How to Fix It
Step 1: Reload the page
Press Ctrl + R. A single stalled connection attempt is common even on a healthy network, and a second try often completes normally.
Step 2: Test a different site
Try a well-known site like google.com. If it loads instantly, the problem is specific to the original destination, not your Chromebook or network.
Step 3: Disable VPN and proxy extensions
Go to chrome://extensions and turn off any VPN, proxy, or ad-blocking extension one at a time, reloading after each. Free or overloaded VPN servers are a frequent cause of exactly this timeout.
Step 4: Switch to a public DNS server
Go to Settings > Network > Wi-Fi > (your network) > Network > Name servers and switch to Google (8.8.8.8) or Cloudflare (1.1.1.1). See our DNS settings guide for the full steps.
Step 5: Restart your router
Unplug it for 30 seconds. A router holding onto a stale connection state for that destination can keep producing the same timeout on every attempt.
Step 6: Try a different network
Connect to a phone hotspot briefly. If the site loads there, the bottleneck is your home network or ISP route to that server, not the Chromebook.
Still Not Fixed?
If ERR_CONNECTION_TIMED_OUT follows one specific site across every network you try, that server is very likely slow, overloaded, or blocking your region. If it happens across many unrelated sites, check for wider connectivity issues, see our guide on slow Wi-Fi on a Chromebook for network-level causes.
FAQ
How is this different from ERR_TIMED_OUT?
They’re closely related. ERR_TIMED_OUT is Chrome’s general timeout message, while ERR_CONNECTION_TIMED_OUT more specifically means the TCP connection itself was established but stalled before completing.
Can my ISP cause this error?
Yes. Some ISPs route certain destinations through congested paths, which can produce connection timeouts on specific sites while everything else loads normally.
Does a VPN really cause this that often?
Yes, it’s one of the most common causes. A free or overloaded VPN server adds enough delay to some requests that they exceed Chrome’s timeout window entirely.
