Fix ERR_CONNECTION_TIMED_OUT in Chrome

ERR_CONNECTION_TIMED_OUT appears when Chrome reaches a website’s server but never gets a response, usually due to network, DNS, or firewall issues. This guide walks through the most reliable fixes, from a simple browser restart to more advanced network settings, so you can get back online quickly.

What You’ll Need

Access to your router (admin password if you plan to restart it)
Windows: Administrator rights to open Command Prompt
Mac: Your system password for terminal commands
5-10 minutes of time

Step-by-Step

Check if the site is down for everyone. Open a different browser (Firefox, Edge, Safari) and try the same URL. If it fails there too, the problem is likely the site itself or your network, not Chrome. You can also try a site like downforeveryoneorjustme.com (or similar) to see if others report an outage.
Restart Chrome completely. Close all Chrome windows. On Windows, check the system tray for a Chrome icon and right-click it to exit. On Mac, press Cmd+Q. Then reopen Chrome and try the site again.
Restart your computer. A full reboot clears temporary network glitches and resets the network stack. After restarting, try the site again.
Clear Chrome’s cache and cookies. Click the three-dot menu (top right), go to More tools > Clear browsing data. Choose “All time” from the time range dropdown, check both “Browsing history” and “Cached images and files,” then click Clear data. Restart Chrome afterward.
Disable Chrome extensions. Type chrome://extensions in the address bar and press Enter. Toggle off all extensions (or remove ones you don’t recognize). Restart Chrome. If the site loads, re-enable extensions one by one to find the culprit.
Flush your DNS cache. This clears corrupted DNS entries that may be pointing to dead addresses. On Windows: Open Command Prompt as Administrator (search “cmd,” right-click, “Run as administrator”), type ipconfig /flushdns and press Enter. On Mac: Open Terminal and type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, then enter your password.
Renew your IP address. On Windows in the same Command Prompt, type ipconfig /release, press Enter, wait 5 seconds, then type ipconfig /renew and press Enter. On Mac, go to System Settings > Network, select your connection, click Details, then TCP/IP, and click Renew DHCP Lease.
Change your DNS server. Your ISP’s DNS may be slow or unreliable. Switch to a public DNS like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1). On Windows: Control Panel > Network and Sharing Center > Change adapter settings, right-click your connection, Properties, select “Internet Protocol Version 4 (TCP/IPv4)”, click Properties, choose “Use the following DNS server addresses,” and enter the numbers. On Mac: System Settings > Network > your connection > Details > DNS, add the addresses.
Disable your VPN or proxy. VPNs and proxy extensions can interfere with connections. Temporarily turn off your VPN (or uninstall the VPN extension) and try the site. Also check Windows: Settings > Network & Internet > Proxy and make sure “Use a proxy server” is off. On Mac: System Settings > Network > your connection > Details > Proxies, and disable any active proxies.
Restart your router and modem. Unplug both devices, wait 30 seconds, plug the modem back in, wait for it to fully boot (lights stabilize), then plug in the router. Wait another 2 minutes, then try the site.
Check your firewall or antivirus. Windows Defender Firewall or third-party antivirus may be blocking Chrome. Temporarily disable your firewall (Settings > Privacy & Security > Windows Security > Firewall & network protection) and try the site. If it works, add Chrome as an allowed app. Re-enable the firewall immediately after testing.
Reset Chrome’s network settings. Type chrome://net-internals/#sockets in the address bar, click “Flush socket pools.” Then go to chrome://net-internals/#dns and click “Clear host cache.” Restart Chrome.

Common Mistakes

Skipping the restart step. Many users jump straight to DNS flushing when a simple browser or PC restart fixes the issue. Always start with the quick wins.
Clearing only cookies. If you clear cookies but not cached images and files, the stale data can still cause timeouts. Select both options.
Not disabling all extensions. Toggling off only a few extensions may miss the problematic one. Turn them all off at once to test.
Changing DNS but not flushing the cache. If you change DNS servers without flushing the old cache, your device may still use the old, broken entries. Always flush after changing.
Assuming it’s your fault. Sometimes the website’s server is genuinely down or overloaded. If the site fails in multiple browsers and on other devices, wait 15-30 minutes before deep troubleshooting.

Tips

Use Chrome’s Incognito mode (Ctrl+Shift+N or Cmd+Shift+N) to test if the issue is extension or cache related. If the site loads in Incognito, the problem is likely an extension or cached data.
Try the site’s IP address directly. Type ping example.com in Command Prompt/Terminal to get the IP, then enter that IP in Chrome’s address bar. If it loads, the issue is DNS resolution.
Check if the error only happens on one device. If other devices on your network load the site fine, the problem is specific to your computer, not your internet connection.
Keep Chrome updated. Go to About Chrome in the menu to check for updates. Older versions have more network bugs.
If you’re on a corporate or school network, the admin may block certain sites. Contact your IT department before making major changes.

Troubleshooting

If you’ve tried all steps and still see the error, work through these additional checks:

Test another device. Connect your phone or tablet to the same Wi-Fi and try the site. If it loads there, the problem is your computer’s network configuration. If it doesn’t, the issue is your router or ISP.
Bypass your router. Plug your computer directly into the modem with an Ethernet cable (if possible) and test. If the site loads, your router is the problem—try resetting it to factory defaults.
Check Windows network reset. On Windows, go to Settings > Network & Internet > Advanced network settings > Network reset. This reinstalls network adapters and resets all settings. You’ll need to reconnect to Wi-Fi afterward. On Mac, delete the Wi-Fi service in System Settings > Network, then re-add it.
Check for malware. Run Windows Defender (Windows) or a trusted malware scanner (Mac). Malware can hijack proxy settings or DNS, causing timeouts.
Try a different profile. Create a new Chrome profile (click your avatar, “Add profile”) and test. If it works, your main profile’s settings are corrupted—consider resetting Chrome to defaults via chrome://settings/reset.
Check the hosts file. On Windows, open Notepad as admin and open C:\Windows\System32\drivers\etc\hosts. On Mac, open Terminal and type sudo nano /etc/hosts. Look for lines containing the site’s domain that aren’t commented out (starting with #). If you find any, delete them and save. This is rare but can cause targeted timeouts.

Frequently Asked Questions

Why does ERR_CONNECTION_TIMED_OUT happen on only one website?
This usually means that specific site’s server is down, your ISP is having routing issues to that server, or your DNS is returning an outdated IP for it. Try flushing DNS first, then check if the site is down for others.

Will clearing my browsing data log me out of websites?
Yes, clearing cookies will log you out of most sites. You’ll need to sign back in after the fix. If you want to avoid this, try the DNS flush and router restart steps first before clearing data.

Is this error caused by a virus?
Rarely, but malware can alter your proxy settings or DNS, causing connection timeouts. If the error persists across all sites and you’ve tried everything, run a full malware scan.

How long should I wait after restarting my router?
Wait at least 2 minutes after the router’s lights stabilize. Some routers take longer to establish a connection with your ISP. If it doesn’t work after 5 minutes, try a factory reset on the router.

Can a VPN cause this error even if it’s off?
Yes, VPN software can leave behind virtual network adapters or modified DNS settings even when “off.” Uninstall the VPN software completely, then restart your computer and test.

Does this error mean my internet is completely down?
No. The error only means Chrome can’t reach that specific server. Other websites may work fine. If all sites fail, the problem is your internet connection itself—check if other devices can browse.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →