How to Fix ERR_CONNECTION_TIMED_OUT in Chrome

By ErrorFix · Updated October 13, 2026 · 7 min read

What ERR_CONNECTION_TIMED_OUT means

ERR_CONNECTION_TIMED_OUT means Chrome sent its request and then waited past its patience limit — about 30 seconds — without getting a usable response. The server might be painfully slow, overloaded, or offline; something in the middle (your router, firewall, VPN, or ISP) might be dropping the connection; or the server might be deliberately ignoring you, as some firewalls do instead of refusing outright.

The tricky part is that the same message covers both "your side is broken" and "their side is broken." The fix is therefore a process of elimination: prove your connection is healthy, strip away everything that could interfere (extensions, VPN, firewall), and test from a second network. Whatever remains is the site's problem, and only waiting or contacting the owner helps.

Common causes

• Slow or unstable internet connection: packet loss or a saturated connection means the server's reply never arrives in time.
• Server overload or outage: the site's server is too busy or down, so it cannot answer before Chrome gives up.
• VPN or proxy slowing or breaking the route: a distant or failing VPN server adds latency or drops the connection entirely.
• Firewall or antivirus blocking Chrome: security software can silently block Chrome's outbound connections to specific sites or ports.
• Conflicting browser extensions: proxy-switching, ad-blocking, or privacy extensions can stall or reroute requests until they time out.

How to fix ERR_CONNECTION_TIMED_OUT — step by step

Work through these fixes in order. Most cases are fixed by step 1, 2, or 4.

1. Check your connection and restart your router. First confirm the problem is not everything: try two or three other major sites. If they all time out, your connection is the issue — unplug your router and modem for 30 seconds, plug them back in, and wait for the lights to stabilize. On a laptop, also try moving closer to the router or switching from Wi-Fi to a wired connection. Run a speed test; high ping or heavy packet loss explains timeouts even when pages partially load.
2. Clear Chrome's cache and cookies. Corrupted cached data can stall page loads until they time out. Press Ctrl + Shift + Delete (Cmd + Shift + Delete on a Mac), set the time range to All time, check Cached images and files and Cookies and other site data, and click Clear data. Restart Chrome and retry the site. This also clears any half-downloaded resources from earlier timed-out attempts that might be confusing the page.
3. Disable extensions one by one. Type chrome://extensions in the address bar and toggle off every extension, then reload the site. If it loads, re-enable extensions one at a time, reloading after each, until the timeout returns — the last one enabled is interfering. Pay special attention to VPN/proxy extensions, ad blockers, and privacy tools, which directly meddle with connections. Remove or update the culprit, or whitelist the site in its settings.
4. Disable your VPN and check the firewall. Disconnect your VPN completely and reload the site. If it loads, the VPN server was too slow or blocking the route — try a different server location or contact the VPN provider. Next, check your firewall: on Windows, open Windows Security, then Firewall & network protection, then Allow an app through firewall, and confirm Google Chrome is checked for both Private and Public networks. Temporarily disabling third-party antivirus (then re-enabling it) is a valid test, but never browse unprotected longer than the test takes.
5. Flush DNS and try another network. Stale DNS can send Chrome to a dead server address. Open Terminal (Admin) or Command Prompt (Admin) and run ipconfig /flushdns, then restart Chrome. Then switch networks: tether to your phone's mobile hotspot and load the site. If it works on mobile data but not your home connection, your ISP's route to that site is broken — report it to the ISP, or use a reputable VPN as a temporary workaround. If it fails everywhere, the site itself is down.
6. Check whether the site is down. When every network fails, confirm with an independent checker like DownDetector or isitdownrightnow.com. Also try the site's social media accounts, which often acknowledge outages. If the site is down for everyone, there is nothing to fix on your end — bookmark it and try again in an hour. If it is up for everyone but you, revisit step 4: something on your machine or network is still blocking it.

Did this fix it? Quick checklist

• The site loads within a few seconds
• Other websites load normally
• The error is gone with extensions disabled
• It works on a second network (mobile hotspot)

If timeouts happen only on one specific site and only from your home connection, your IP may be rate-limited or blocked by the site's firewall — some firewalls silently drop connections instead of showing a block page. Contact the site owner with your IP address (search "what is my ip") and the time of the failures. If timeouts plague many sites at once, call your ISP: chronic packet loss or an overloaded local node is their problem to fix.