Chrome ERR_CONNECTION_TIMED_OUT — What It Means & How to Fix It

What Does This Error Mean?

ERR_CONNECTION_TIMED_OUT means Chrome tried to connect to a website but the server did not respond in time. This is different from a refused connection — the server simply did not answer before Chrome gave up waiting. It is usually caused by a slow network, an overloaded server, or a firewall blocking the connection.

Affected Models

Google Chrome Windows
Google Chrome macOS
Google Chrome Linux
Google Chrome Android
All Chrome versions

Common Causes

The website server is overloaded or temporarily down
Your internet connection is too slow or unstable to complete the connection
A firewall, antivirus, or VPN is blocking or delaying the connection
Your DNS server is taking too long to resolve the domain name
Windows hosts file or a Chrome extension is redirecting the request to the wrong address

How to Fix It

Check your internet connection — open another website to confirm you are online.

If other sites also time out, the problem is your internet connection, not the specific website.
Reload the page with Ctrl+R — the timeout may have been a one-time blip on the server.

High-traffic sites occasionally have brief overloads that resolve within seconds — a simple reload often works.
Flush your DNS cache: on Windows, open Command Prompt and run `ipconfig /flushdns`.

A stale or corrupted DNS cache can direct Chrome to the wrong server address, causing timeouts — flushing forces a fresh lookup.
Change your DNS server to Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) in your network adapter settings.

Your ISP's default DNS server may be slow or down — Google and Cloudflare DNS are faster and more reliable.
Temporarily disable your VPN, antivirus, or firewall and try loading the page again.

Security software can add latency or block connections to certain sites — disabling briefly confirms if it is the cause.
Restart your router and modem by unplugging them for 30 seconds, then reconnecting.

A stuck router can cause widespread connection timeouts that affect all browsers — a full restart clears the router state.

When to Call a Professional

ERR_CONNECTION_TIMED_OUT is almost always self-fixable without professional help. If the timeout only occurs on your company network, contact your IT department — a firewall rule may be blocking the site. For persistent timeouts on a specific website, the site owner may need to investigate their server performance.

Frequently Asked Questions

What is the difference between ERR_CONNECTION_TIMED_OUT and ERR_TIMED_OUT?

ERR_CONNECTION_TIMED_OUT means Chrome could not establish the initial connection to the server. ERR_TIMED_OUT means the connection was established but the server stopped responding while loading the page. Both have similar fixes, but a connection timeout usually points to a network or firewall issue.

Why does ERR_CONNECTION_TIMED_OUT only happen on one website?

That specific website may be down, overloaded, or geo-blocked in your region. Check if the site is reachable from a different network (like your phone on mobile data). If it works on mobile data but not on your Wi-Fi, your router or ISP may be blocking it.

Can a VPN fix ERR_CONNECTION_TIMED_OUT?

Sometimes yes — if your ISP is throttling or blocking a specific site, a VPN can route around it. However, a VPN can also cause timeouts if the VPN server itself is slow or overloaded. If you already have a VPN active when you get the error, try disabling it first.