ERR_CONNECTION_TIMED_OUT is Chrome telling you it tried to open a connection to a server and gave up waiting for a reply. Unlike a 404 or a 500 — which are answers from a server that's working — a connection timeout means no answer came back at all. The browser sent packets into the void and heard nothing. Most of the time that void is on your side of the wire, which is the good news: the things you can actually fix are the most likely causes.
What the error actually means ¶
When you load a page, your browser opens a TCP connection to the server: it sends a SYN packet and waits for a SYN-ACK back. If that handshake doesn't complete within Chrome's timeout (around 30 seconds), Chrome shows ERR_CONNECTION_TIMED_OUT. The key fact is that nothing answered — not even an error. That rules out a whole class of problems (the server isn't returning 500s or 403s, because the server isn't talking to you at all) and points at the layers between your browser and the server: your machine, your network, your ISP, the route, or the server being genuinely unreachable.
Firefox shows the same situation as "The connection has timed out." Edge shows Chrome's exact text since they share an engine. Safari says "Safari can't open the page because the server stopped responding." Same underlying event.
Local vs remote: the one question that matters ¶
Before trying any fix, answer this: does the timeout happen for one site or every site? It splits the diagnosis cleanly:
- Only one site times out, everything else loads: the problem is specific to that site or the path to it. Either the site is genuinely down/unreachable, or something on your machine is specifically blocking that one domain (hosts file, firewall rule, extension).
- Every site times out: the problem is your network connection, DNS, router, or ISP — not any individual site. Fixing your connection fixes all of them at once.
For the single-site case, the fastest way to learn whether the site itself is down is a multi-region check: open isitdown.io and probe the domain. If all four regions reach it, the site is up and your timeout is local. If they all fail too, the site is genuinely unreachable and there's nothing to fix on your end. Full diagnostic walkthrough →
The fix checklist, cheapest first ¶
1. Reload and check a second site (5 seconds)
Transient network blips clear on a retry. And opening a known-good site (e.g. a search engine) immediately tells you whether this is one-site or all-sites — the single most useful piece of information.
2. Flush your DNS cache (15 seconds)
A stale or poisoned DNS entry can send your connection to a dead IP, which then times out. Flushing forces a fresh lookup:
- Windows:
ipconfig /flushdns - macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Linux (systemd):
sudo resolvectl flush-caches - Chrome internal cache: visit
chrome://net-internals/#dns→ "Clear host cache"
Full flush-DNS reference for every OS →
3. Try a different network (20 seconds)
Switch to your phone's mobile hotspot. If the site loads on cellular but not on your home/office Wi-Fi, the problem is your router, your ISP, or a network-level filter — not the site and not your computer. This is the single most diagnostic test in the list because it isolates the network layer instantly.
4. Switch your DNS resolver (1 minute)
If your ISP's DNS resolver is slow or returning bad answers, switching to a public resolver fixes timeouts that are really DNS problems in disguise. Set your system DNS to Cloudflare (1.1.1.1 + 1.0.0.1) or Google (8.8.8.8 + 8.8.4.4). If the page loads after the change, your old resolver was the problem.
5. Disable VPN / proxy / extensions (30 seconds)
A VPN with a dead exit node, a misconfigured proxy, or a security/ad-blocking extension can intercept and stall connections. Test in an incognito window (extensions are off by default there) and temporarily disconnect any VPN. If incognito works, an extension is the culprit — re-enable them one at a time to find which.
6. Check the hosts file and firewall (2 minutes)
If exactly one site times out and steps 1-5 didn't help, something on your machine may be specifically blocking it. Check /etc/hosts (or C:\Windows\System32\drivers\etc\hosts on Windows) for an entry redirecting the domain to 0.0.0.0 or a dead IP. Check your firewall and any parental-control / security software for a rule blocking the domain. Pi-hole and similar local DNS sinkholes count here too.
7. Reset the network stack (last resort)
If everything else fails and multiple sites time out, a corrupted network stack can be the cause. On Windows: netsh winsock reset + netsh int ip reset + reboot. On macOS: remove and re-add the network interface in System Settings. On any OS: restarting the router clears a surprising number of these.
When it's the site, not you ¶
If a multi-region check shows the site failing from all regions, the timeout is on the server's side and none of the local fixes apply. The most common server-side causes:
- The server is down or overloaded and not accepting new connections.
- The site's firewall is blocking your country or IP range (geo-blocking).
- The hosting provider had a network event and the route to the server is broken.
- The domain points at an IP that no longer hosts anything (stale DNS on the site owner's side).
In all of these, the only options are to wait, use a VPN exit in a different region (if it's geo-blocking), or contact the site owner. There's no client-side fix for a server that isn't answering.
FAQ ¶
Is ERR_CONNECTION_TIMED_OUT the same as a site being down?
Not always. It means your browser couldn't establish a connection — which can be the site being down, but is just as often a local network, DNS, VPN, or firewall problem. The one-site-vs-all-sites test and a multi-region check tell you which. A genuinely-down site also fails from our four monitoring regions; a local problem doesn't.
Why does the site work on my phone but not my computer?
If it works on cellular but not Wi-Fi, the issue is your local network — router, ISP DNS, or a filter on that network. If it works on the phone over the same Wi-Fi but not the computer, the issue is specific to the computer: its DNS cache, hosts file, VPN, firewall, or an extension. Either way the site itself is fine.
Can a slow connection cause this even when the site is up?
Yes. If your connection is so congested or high-latency that the TCP handshake can't complete within ~30 seconds, you'll see a timeout even though the site is perfectly healthy for everyone else. This is common on saturated networks, far-from-server satellite links, or during heavy local network use. Testing on a different, faster network confirms it.
Does clearing browser cache fix ERR_CONNECTION_TIMED_OUT?
Rarely, because the browser cache holds rendered pages and assets, not network-layer connection state. Flushing the DNS cache (step 2) is the cache that actually matters for this error. Clearing the regular browser cache doesn't hurt but isn't usually the fix.