Fix ERR_TIMED_OUT in Chrome

Chrome’s ERR_TIMED_OUT error looks like a connection problem — but in most cases the website is fine. The real culprit is usually a stuck socket pool or a stale DNS cache on your end, both of which Chrome never tells you about directly. For the bigger picture, our Google Chrome Errors pulls everything together.

The good news: both fix in under two minutes. Start with Step 1 below — it resolves the error for the majority of users without touching any settings.

ERR_TIMED_OUT in Chrome means the browser sent a request and waited the full timeout period — around 30 seconds by default — without receiving any response. The connection didn’t get refused or reset; it just never got an answer. That distinction matters, because it tells you something specific: either the request didn’t reach the server, the server received it but is too slow or overloaded to respond, or something between you and the server is silently dropping packets rather than actively rejecting them.

The single most useful diagnostic question with ERR_TIMED_OUT: does this happen on every website, or just specific ones? Everything you do next depends on the answer.

Diagnose First: One Site or All Sites?

Open two or three different websites you trust are normally up — Google, Wikipedia, BBC News. If they all time out, the problem is your network connection or your PC’s network configuration, not the specific site you were trying to reach. Work through Fixes 1, 2, and 3 in that order.

If only one site times out while others load fine, the problem is either that specific server (it could be down, overloaded, or geographically far away), or something on your network is blocking connections to that specific server’s IP address. Fix 4 (check the site status) and Fix 5 (firewall and VPN check) are the right starting points.

A quick test that confirms whether the issue is DNS or connectivity: open Command Prompt and run ping 8.8.8.8. This sends a direct ICMP packet to Google’s public DNS server without any DNS lookup needed. If that ping times out, your internet connection is genuinely down. If it gets replies but websites still time out, DNS is working but something else is blocking or delaying web connections specifically.

ERR_TIMED_OUT Fix 1: Check the Connection and Restart the Router

When ERR_TIMED_OUT affects every site, the internet connection itself is the first thing to check. This seems obvious but is worth being methodical about — there’s a difference between “the router is connected to power but the internet is down” and “the Wi-Fi is connected but the Ethernet cable fell out of the router.”

Check other devices first. Can your phone load websites on Wi-Fi? Can a tablet? If all devices have no internet, the problem is upstream — either the router or the connection from the router to your ISP. Unplug the router from power, wait a full 60 seconds (not 10, not 30 — 60), plug it back in, wait 2 minutes for it to fully reconnect, and test again. Most consumer router issues that cause ERR_TIMED_OUT clear with a full power cycle.

If only your PC has the issue while other devices are fine, the problem is specific to your PC’s network connection. Check the Ethernet cable if you’re wired — a loose cable can make Windows report “connected” while actually dropping packets. If you’re on Wi-Fi, check that the signal is strong and try moving closer to the router. Also try right-clicking the network icon in the taskbar and running the Windows network troubleshooter — it occasionally catches straightforward issues like an IP address conflict that would otherwise require several manual steps to diagnose.

ERR_TIMED_OUT Fix 2: Flush DNS and Switch DNS Server

If the ping to 8.8.8.8 succeeds but websites still time out, the internet connection is fine but DNS resolution is failing or extremely slow. Chrome is timing out while waiting for the DNS server to respond rather than timing out on the actual page load. The distinction matters because the fix is DNS-specific, not general network troubleshooting.

1. Open Command Prompt as administrator
2. Run: ipconfig /flushdns
3. In Chrome: chrome://net-internals/#dns → Clear host cache
4. Change DNS server: Settings → Network and internet → your connection → DNS server assignment → Manual → Preferred: 1.1.1.1, Alternate: 8.8.8.8
5. Test immediately after saving

Cloudflare’s 1.1.1.1 responds in single-digit milliseconds from most locations. If your ISP’s DNS is taking 5–10 seconds to respond — which is long enough to cause ERR_TIMED_OUT on Chrome’s internal DNS resolution step — switching to 1.1.1.1 fixes the timeouts immediately and permanently.

ERR_TIMED_OUT Fix 3: Reset the Windows Network Stack

When ERR_TIMED_OUT appears across multiple sites and multiple browsers, and the router restart didn’t fix it, accumulated corruption in Windows’ network stack is often the cause. This happens more after major Windows updates, after VPN software installations and uninstallations, or after certain security products that modify network drivers. The network appears connected but connections time out because the underlying TCP/IP layer has become corrupted.

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /flushdns
ipconfig /renew

Run all of these in Administrator Command Prompt in order, then restart the PC. The Winsock reset requires a restart to take effect. After restarting, test Chrome. This combination of commands returns the network stack to a clean state and resolves ERR_TIMED_OUT caused by stack corruption in the majority of cases.

ERR_TIMED_OUT Fix 4: Check Whether the Site Is Actually Down

When ERR_TIMED_OUT appears on one specific site while everything else loads fine, the most likely explanation is that the site itself is down or overloaded. Servers under DDoS attack, servers experiencing hardware failures, and servers that are intentionally offline for maintenance all produce ERR_TIMED_OUT from Chrome’s perspective — the requests reach the server’s network but never get answered.

Test this in under a minute: open the site on your phone with Wi-Fi turned off (mobile data only). If it also times out on mobile data, the server is genuinely down. If it loads on mobile data, the issue is specific to your home network’s connection to that server — possibly an IP routing issue between your ISP and the server’s hosting provider, which you can’t fix yourself and will typically clear within a few hours as routing tables update.

A site status service (search “[site name] down” or check downdetector.com) shows whether others are reporting the same issue. If the site is confirmed down, nothing you do on your end will help — wait it out, check the site’s social media for status updates, or find an alternative if the content is urgently needed.

ERR_TIMED_OUT Fix 5: Firewall, VPN, and Extension Check

A firewall that’s silently dropping packets — rather than actively rejecting connections — causes ERR_TIMED_OUT rather than ERR_CONNECTION_REFUSED. The connection request goes out, the firewall intercepts and drops it without sending a rejection, and Chrome waits 30 seconds before giving up. This is actually how firewalls are typically configured to block connections: silence rather than explicit rejection, because an explicit rejection reveals what’s blocked.

• Temporarily disable Windows Firewall: Settings → Windows Security → Firewall and network protection → active network → toggle off. Test immediately. Turn it back on after testing — this is just a diagnostic step.
• If a VPN is active, disconnect it completely. VPN routing issues cause ERR_TIMED_OUT when the path through the VPN to a specific server is broken or has extremely high latency.
• Test in Chrome Incognito (Ctrl + Shift + N) — if sites that were timing out now load, an extension is adding enough latency to push connections over Chrome’s timeout threshold. Common culprits: poorly written proxy extensions, aggressive content blockers, and security extensions that inspect every connection.

If disabling the firewall resolves the timeout, re-enable it and look for recently added firewall rules that may be blocking the site. Windows Security’s Firewall log (under Advanced Settings → Windows Defender Firewall with Advanced Security → Monitoring → Firewall) shows blocked connections with timestamps that you can match to when the timeout occurred.

ERR_TIMED_OUT Quick Reference

Our guide on ERR_CONNECTION_RESET covers the related error where connections are actively cut rather than silently dropped — the two errors share several causes but have different behaviour. For connection refusals where the server actively rejects the connection, ERR_CONNECTION_REFUSED is the relevant guide. Google Chrome’s support documentation includes additional timeout troubleshooting for enterprise environments where proxy configurations introduce latency that causes ERR_TIMED_OUT on specific internal or external destinations.

Slow connections that hover just above the timeout threshold are a frustrating variant of ERR_TIMED_OUT that’s hard to diagnose because the connection sometimes works and sometimes doesn’t. You’ll see ERR_TIMED_OUT intermittently — some page loads succeed after a long wait, others time out. This pattern usually points to either a congested network link between your ISP and the server, a server that’s borderline overloaded (responding to some requests but not others), or a network adapter or cable that’s dropping packets inconsistently.

For intermittent ERR_TIMED_OUT on a wired connection, try a different Ethernet cable if you have one available. Ethernet cables fail in ways that are invisible to Windows — the link shows as connected and transferring data, but the error rate is high enough that some connections time out before getting enough data through. A cable swap is a 30-second test that has resolved chronic intermittent ERR_TIMED_OUT for a notable number of users. Also run ping -t google.com in Command Prompt (Ctrl+C to stop it) and watch for any “Request timed out” lines in the output — more than one or two in a hundred pings indicates genuine packet loss on the connection, which will cause ERR_TIMED_OUT under load.

For intermittent ERR_TIMED_OUT on Wi-Fi, the cause is almost always signal quality or channel congestion. Wi-Fi running on an overcrowded 2.4GHz channel — particularly in dense housing where every neighbour has their router broadcasting on the same channel — drops packets under load in ways that cause intermittent timeouts. Switching the router to 5GHz (which is less congested in most environments) or manually changing the 2.4GHz channel to one that’s less occupied (use a Wi-Fi analyser app on a phone to see which channels neighbouring networks are using) reduces the packet drop rate and the resulting ERR_TIMED_OUT frequency significantly.

Geographic distance to the server is the last cause worth mentioning, particularly for ERR_TIMED_OUT on services hosted in distant regions. Round-trip latency from Europe to an Asia-Pacific server can exceed 200ms, and under load with multiple round-trips for connection setup, Chrome’s timeout can be reached on very high-latency connections. Using a VPN server in the destination region — counter-intuitive given that VPNs can cause ERR_TIMED_OUT in other scenarios — actually reduces the effective round-trip time by placing the “connection entry point” closer to the destination server. It’s worth trying if ERR_TIMED_OUT is consistently affecting one specific foreign-hosted service while domestic sites load normally. The VPN makes the connection geographically shorter even if it adds a small overhead, and that trade-off can be enough to get below Chrome’s timeout threshold.

One thing to be cautious about with ERR_TIMED_OUT: don’t confuse a slow page load with a genuine timeout. If Chrome shows a mostly-loaded page with some elements still loading after many seconds, and you’re getting ERR_TIMED_OUT on specific resources rather than the whole page, those specific resources may be hosted on a slow CDN or a different server from the main page. The fix in that case is specific to those resources — not a general network issue — and often resolves on a reload when the CDN selects a different edge server. True ERR_TIMED_OUT as covered in this guide is a blank page with the error code, not a partially loaded page where some elements are slow.

Chrome’s behaviour on ERR_TIMED_OUT has a small nuance worth knowing: it will automatically retry certain types of requests before showing you the error page. For GET requests (standard page loads), Chrome typically tries twice before giving up. For POST requests (form submissions, logins), it usually only tries once — because retrying a POST could cause duplicate submissions. This means ERR_TIMED_OUT on a form submission that was on the edge of the timeout threshold may have been sent and may have succeeded on the server even though Chrome showed an error. Before resubmitting a form that timed out, check whether the action actually went through (log in separately, check the account, verify the order, etc.) to avoid processing duplicates. This isn’t relevant to fixing the ERR_TIMED_OUT itself, but it avoids the common consequence of retrying a form submission that already completed.

For users in countries with government-level internet filtering, ERR_TIMED_OUT on specific sites may not be a technical problem at all — it may be intentional censorship at the network level. Governments and ISPs that block sites often use silent packet dropping rather than active connection refusal, which produces ERR_TIMED_OUT rather than a more informative error. A VPN routed through a country without the same filtering will bypass this, though legal and policy considerations around VPN use vary by jurisdiction.