You wait, and wait, and then Chrome gives up: ERR_CONNECTION_TIMED_OUT, usually under the heading "This site can't be reached — took too long to respond." Unlike a quick "not found" error, a timeout means your browser genuinely tried to connect and simply never heard back. That distinction matters, because it points to a specific set of causes — and a specific set of fixes. Here's what the error really means and how to clear it fast, whichever device you're on.
What ERRCONNECTIONTIMED_OUT actually means
When you open a page, your browser opens a connection to the site's server and waits for a reply. If that reply doesn't arrive within a set time limit (usually around 30 seconds), the browser stops waiting and shows a timeout error. In other words, the request left your device fine — nothing came back.
That failure lives at the connection stage, which is what separates it from a DNS error like DNS_PROBE_FINISHED_NXDOMAIN (where the address can't even be found). A timeout usually means one of these:
- The site's server is overloaded, slow, or down.
- A firewall, antivirus, or proxy on your side is silently blocking the connection.
- Your network is congested or dropping packets.
- Stale browser or DNS data is sending you down a dead path.
The trick is figuring out which side the problem is on before you start changing settings.
First: is the site down for everyone or just you?
This is the fastest way to save yourself pointless troubleshooting. Run the site through our live website down checker — it connects from our servers, on a completely different network from yours. If our server also times out, the site's server is overloaded or offline and there's nothing to fix on your end but wait. If our server connects fine while you time out, the problem is local, and the fixes below will clear it. Our guide on whether a site is down for everyone or just you covers this 60-second test in detail.
How to fix ERRCONNECTIONTIMED_OUT fast
Assuming the checker shows the site is up, work through these in order — the first few resolve the vast majority of cases.
1. Restart your router and check your connection
Open another website first. If everything times out, the problem is your connection — unplug your router for 30 seconds, plug it back in, and let it fully reconnect. Timeouts caused by network congestion or a flaky router often vanish after this alone.
2. Flush your DNS cache and clear browser data
Stale local data is a classic cause. Flush your DNS cache (ipconfig /flushdns on Windows; sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS) — our step-by-step DNS flush guide covers every platform. Then clear Chrome's cached images and cookies, or simply try the site in an incognito window to rule out cache and extensions instantly.
3. Disable your firewall, antivirus, VPN, or proxy
Security tools are the number-one cause of local timeouts. A firewall or antivirus can silently drop the connection, and a VPN or proxy can route you through a slow or blocked path. Turn each off one at a time and reload. If the site loads, you've found the culprit — then re-enable the tool and add the site to its allow-list.
4. Check your LAN proxy settings
A misconfigured proxy will make every connection time out. On Windows, go to Settings → Network & Internet → Proxy and make sure "Automatically detect settings" is on and no manual proxy is set unless you deliberately use one. On Mac, check System Settings → Network → Details → Proxies.
5. Switch to a public DNS server
If your ISP's DNS is slow to respond, connections can stall out. Switching to Cloudflare's 1.1.1.1 or Google's 8.8.8.8 in your network settings frequently fixes timeouts and speeds up browsing overall.
6. Reset your network stack (Windows)
If nothing above works, reset the underlying network components. In an admin Command Prompt, run netsh winsock reset and netsh int ip reset, then restart your computer. This clears corrupted network configuration that can cause persistent timeouts.
When the site itself is the problem
If our checker confirms the site is up for everyone but it still times out for you after all six steps, the issue may be that the server is simply slow — teetering on the edge of the timeout limit rather than fully down. You can test this directly with our free site speed (TTFB) test: it measures exactly how long the server takes to respond. If the time-to-first-byte is very high, the server is struggling, and the timeout is on their end.
For a fuller breakdown of what makes a server slow and what — if anything — you can do about it, our explainer on why a website loads slowly is worth a read. And if a single site keeps timing out only for you, our checklist on fixing a site that's down for you but not everyone covers the remaining edge cases.
The bottom line
ERR_CONNECTION_TIMED_OUT means your browser reached out and got silence back — a connection problem, not a dead computer. Start by confirming whether the site is down for everyone, then work down the list: restart your router, flush DNS, disable security tools, check your proxy, switch DNS, and reset your network stack if needed. In most cases you'll be back in under a couple of minutes — and if the checker shows the server itself is slow or offline, you'll know the wait isn't yours to fix.