How to fix ERR_CONNECTION_TIMED_OUT

ERR_CONNECTION_TIMED_OUT appears under "This site can't be reached … took too long to respond". Your browser found the website's address and tried to connect, but nothing answered before it gave up.

That happens when the website's server is down or overloaded, or when something between you and the site, such as a firewall, VPN, proxy or your router, is silently dropping the connection.

Is the website down?

Run the address through our website checker. If our servers can't connect either, the site is down and you'll need to wait for the owner to fix it. If our check succeeds, the problem is between you and the site.

How to fix it on your side

1. Reload once, then wait a minute and try again. Brief timeouts are common during traffic spikes.
2. Try another network, such as mobile data. If the site loads there, restart your router.
3. Turn off your VPN, proxy and any "secure browsing" extension. In Windows, check Settings, Network & internet, Proxy, and make sure no manual proxy is set unless you need one.
4. Check your firewall or antivirus. Temporarily pause it and try again. If the site loads, add an exception for your browser.
5. Clear DNS caches: run ipconfig /flushdns on Windows, and clear Chrome's host cache at chrome://net-internals/#dns. An out-of-date DNS answer can send you to an old server that no longer answers.
6. Reset your network settings on Windows with netsh winsock reset and netsh int ip reset in an administrator Command Prompt, then restart.

If you run the website

A timeout usually means the server isn't accepting connections on port 80 or 443: it's down, overloaded, or a firewall or security group is blocking traffic. Check that the web server is running, that the server's firewall allows ports 80 and 443, and that your DNS records point at the right IP address.