ERR_CONNECTION_TIMED_OUT occurs when Chrome waits too long for a response from the website’s server and gives up. Chrome’s default timeout is around 30 seconds. If the server does not respond within that window, the browser displays this error. The cause is either network congestion on your end, an overloaded remote server, or something blocking the connection in between.
This ranks among the most common Chrome errors because dozens of factors can delay server responses. Your ISP might throttle certain traffic, your antivirus could inspect packets slowly, the website might experience heavy load, or a misconfigured proxy might add latency. Here is how to systematically diagnose and fix it.
Test Your Internet Speed
Run a speed test at fast.com or speedtest.net. If your download speed drops below 1 Mbps or your ping exceeds 200ms, network congestion on your end causes the timeout. Restart your router, disconnect other devices using bandwidth, or contact your ISP. A stable connection with ping under 50ms should not produce ERR_CONNECTION_TIMED_OUT unless the server itself is slow.
Clear Browser Cache and Cookies
Corrupted cache entries force Chrome to make malformed requests that servers cannot process. Press Ctrl+Shift+Delete, select “All time,” check all boxes, and click “Clear data.” This eliminates stale cookies that cause authentication loops and cached redirects that point to dead endpoints, both of which trigger ERR_CONNECTION_TIMED_OUT.
Flush DNS and Renew IP
Open Command Prompt as administrator. Run ipconfig /flushdns, then ipconfig /release, then ipconfig /renew. This clears outdated DNS records and requests a fresh network configuration from your router. Old DNS entries might point Chrome to an IP address that no longer hosts the website, causing the connection to hang until timeout.
Disable Firewall and Antivirus Temporarily
Security software inspects every outgoing connection, adding latency. Disable Windows Defender Firewall and any third-party antivirus for 60 seconds and try loading the site. If the page loads, your security software adds enough inspection delay to trigger the timeout. Add the website to your security software’s whitelist rather than leaving protection disabled.
Change DNS Servers
Slow DNS resolution eats into Chrome’s timeout budget. Switch from your ISP’s DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8). Cloudflare resolves queries in under 12ms on average, compared to 30-80ms for most ISP DNS servers. That 50ms difference matters when the server already responds slowly, as it prevents ERR_CONNECTION_TIMED_OUT at the margin.
Check Your Hosts File
A modified hosts file can redirect domains to wrong or nonexistent IP addresses. On Windows, open C:\Windows\System32\drivers\etc\hosts with Notepad (run as administrator). On Mac, open Terminal and type sudo nano /etc/hosts. Remove any entries pointing the problematic domain to 127.0.0.1 or other addresses. Malware and development tools sometimes modify this file.
Disable Proxy Settings
Proxy servers add a network hop that increases latency. Open Settings > Network & Internet > Proxy on Windows and ensure “Automatically detect settings” is on and “Use a proxy server” is off. Chrome inherits system proxy settings, and a misconfigured or offline proxy guarantees ERR_CONNECTION_TIMED_OUT on every page load.
Try Incognito Mode
Press Ctrl+Shift+N to open an incognito window and visit the site. Incognito mode disables all extensions and uses a clean session without cached data. If the page loads in incognito, one of your extensions or a corrupted cookie causes the timeout. Disable extensions one by one in normal mode to find the culprit.
Frequently Asked Questions
How long does Chrome wait before showing ERR_CONNECTION_TIMED_OUT?
Chrome waits approximately 30 seconds for a server response before displaying ERR_CONNECTION_TIMED_OUT. This timeout applies to the initial TCP connection handshake. If the server accepts the connection but responds slowly during data transfer, Chrome may wait longer before showing a different timeout error.
Does ERR_CONNECTION_TIMED_OUT mean the website is down?
Not necessarily. ERR_CONNECTION_TIMED_OUT can result from problems on your end (network issues, DNS failures, firewall blocking) even when the website works fine for other users. Test the site using a service like downforeveryoneorjustme.com to check whether the outage is universal or specific to your connection.
