ERR_TIMED_OUT appears in Chrome when your browser sends a request to a server but receives no response within Chrome’s timeout window, typically 30 seconds. This happens because your internet connection is too slow or unstable, the target server is overloaded and cannot respond in time, a proxy or VPN adds excessive latency, or DNS resolution takes too long to complete.
Most people see this error when a site that was loading fine yesterday suddenly stops responding. The connection does not get refused outright, which would give you ERR_CONNECTION_REFUSED. Instead, Chrome waits and waits until it gives up entirely. That distinction matters because it tells you whether the problem is your network or the server.
What Causes ERR_TIMED_OUT
ERR_TIMED_OUT is Chrome’s signal that the server never completed the TCP handshake within its timeout threshold. The four most common triggers are a slow or intermittent internet connection on your side, a server that is overloaded or temporarily offline, a VPN or proxy that routes your traffic through an overloaded intermediary node, and stale or slow DNS resolution that adds several seconds before the actual connection attempt even starts.
Security software is a less obvious culprit. Antivirus programs like Avast, ESET, and Kaspersky perform real-time HTTPS inspection by acting as a man-in-the-middle proxy. When their inspection engine is slow or encounters a certificate it cannot validate quickly, it holds the connection open too long, pushing the total round-trip time past Chrome’s threshold. Corporate firewalls behave similarly.
Finally, Chrome itself can be the problem. A corrupted profile, a misbehaving extension, or a misconfigured proxy setting in Chrome’s network stack can delay every outbound request. Testing in Incognito mode immediately tells you whether Chrome’s state is causing the timeout or whether the issue lives at the OS or network level.
Check Your Internet Connection First
Before touching Chrome settings, confirm your connection is functional. Visit fast.com or run a speed test. If your download speed is below 2 Mbps or if you see packet loss above 2%, your connection is the bottleneck. Restart your router by unplugging it for 30 seconds, then reconnecting. If you are on WiFi, switch to ethernet to eliminate wireless interference as a variable.
Run a quick ping test from Command Prompt: ping google.com -n 20. If you see timeouts or latency spikes above 200ms, the problem is network instability between you and the DNS server, not Chrome. Contact your ISP if packet loss persists after a router restart.
Flush DNS and Switch to a Faster DNS Server
DNS resolution adds latency to every page load, and a slow or unreachable DNS server can push Chrome past its timeout before the connection even starts. Open Command Prompt as administrator and run ipconfig /flushdns. This clears the local DNS cache. Then switch your system DNS to Cloudflare (1.1.1.1 primary, 1.0.0.1 secondary) or Google DNS (8.8.8.8 primary, 8.8.4.4 secondary).
To change DNS on Windows 11, go to Settings, then Network and Internet, then your active connection, then DNS server assignment. Set it to Manual and enter the Cloudflare or Google addresses. Cloudflare’s 1.1.1.1 resolver averages under 12ms globally, compared to 50-150ms for many ISP resolvers. That gap is significant enough to prevent timeout errors on marginal connections.
Also clear Chrome’s internal DNS cache at chrome://net-internals/#dns and click Clear host cache. Chrome maintains its own DNS cache separately from Windows, and stale entries in Chrome’s cache can send traffic to unresponsive IP addresses.
Clear Cache and Disable Extensions
Press Ctrl+Shift+Delete in Chrome, select All time, check Cached images and files and Cookies and other site data, then click Clear data. A corrupted cache entry can cause Chrome to send malformed requests that the server drops, resulting in a timeout. Clearing it forces a fresh request cycle.
Extensions that modify requests, block content, or inject scripts add processing time to every page load. On slow connections or overloaded servers, this overhead tips the balance toward ERR_TIMED_OUT. Open chrome://extensions/ and toggle all extensions off. If the page loads, re-enable extensions one at a time to identify the conflict. Common culprits are ad blockers with aggressive rule sets, VPN extensions, and privacy-focused extensions that inspect outbound requests.
Disable Proxy and VPN
A VPN or proxy routes your traffic through an additional server before it reaches the destination. If that intermediate server is overloaded, located far from you, or experiencing packet loss, the added latency causes ERR_TIMED_OUT. Disconnect your VPN client entirely, not just pause it. Go to Settings, then Network and Internet, then Proxy, and set Use a proxy server to Off.
If you need a VPN for your use case, switch to a server node geographically closer to the target website’s server. A VPN tunnel from the US to a European server, passing through an overloaded UK VPN node, can add 200-400ms of latency on top of an already marginal connection.
Try Incognito Mode and Test in Another Browser
Press Ctrl+Shift+N to open an incognito window. Incognito mode runs without extensions, ignores cached data, and uses a fresh session. If the page loads in incognito but not in your regular window, the problem is either a corrupted extension or a bad cache entry. If it fails in incognito too, the issue is at the OS network level or is server-side.
Also test the URL in Microsoft Edge or Firefox. If it loads in a different browser, Chrome’s network stack or proxy configuration is the culprit. Go to chrome://settings/system and click Open your computer’s proxy settings to review and clear any leftover proxy configuration.
Advanced Fixes for Persistent ERR_TIMED_OUT
If basic troubleshooting has not resolved the issue, work through these deeper fixes in order. Reset Chrome’s network settings by running netsh winsock reset and netsh int ip reset in an elevated Command Prompt, then restart your computer. A corrupted Winsock configuration causes Chrome’s TCP connections to fail silently, producing timeout behavior.
Check your antivirus HTTPS scanning settings. If you use Avast, ESET, Kaspersky, or Bitdefender, find the HTTPS scanning or SSL inspection setting and disable it temporarily. Test the page. If it loads, re-enable scanning and add the specific domain to your antivirus exclusion list.
Restart your router and check for firmware updates in its admin panel, usually at 192.168.1.1. Routers with outdated firmware have known bugs that cause intermittent TCP timeout behavior on specific connection types. Some routers also develop DNS relay issues after extended uptime, which a full power cycle resolves.
If ERR_TIMED_OUT happens only on specific sites and not others, the problem is server-side. Use downforeveryoneorjustme.com to confirm. If the site is down for everyone, there is nothing to fix on your end.
Frequently Asked Questions
Does ERR_TIMED_OUT mean my computer has a virus?
ERR_TIMED_OUT is a standard network timeout error, not a malware indicator. Malware that modifies your DNS settings, proxy configuration, or hosts file can indirectly cause timeout errors by routing traffic to unresponsive addresses. If the error appears on many sites simultaneously and basic fixes fail, run a scan with Windows Defender or Malwarebytes to rule out interference.
Why does ERR_TIMED_OUT only happen on some websites?
Site-specific ERR_TIMED_OUT errors almost always indicate a server-side problem: the target server is down, overloaded, or has a misconfigured firewall that silently drops connections from your IP range. Your ISP may also throttle traffic to certain servers. Clearing your DNS cache and trying a different DNS server resolves the issue when stale records point to an offline server IP.
How long should I wait before trying to fix ERR_TIMED_OUT?
If ERR_TIMED_OUT appears once on a site that was working earlier, wait 2-3 minutes and refresh. Temporary server overload and transient network issues often resolve on their own. If the error persists across multiple refresh attempts over five or more minutes, work through the fixes in this guide starting with DNS flush and cache clearing.
Can a firewall cause ERR_TIMED_OUT?
Yes. Firewalls that silently drop packets rather than send a rejection response cause timeout behavior rather than ERR_CONNECTION_REFUSED. Windows Defender Firewall, corporate network firewalls, and third-party security suites all can produce this behavior. Temporarily disable your firewall and test. For connections that are actively refused rather than timed out, see the guide on fixing ERR_CONNECTION_REFUSED.
For a related reset error instead of a timeout, the article on ERR_CONNECTION_RESET covers that failure mode in detail. If Chrome is dropping connections before the response completes, the ERR_CONNECTION_CLOSED guide walks through those specific causes.
