sodcalculator

10 Tech How-To

ERR_TIMED_OUT in Chrome: How to Fix It

Guide 10-45065 · Updated · Step by step

This guide covers the most common causes of the ERR_TIMED_OUT error in Google Chrome and walks you through fixes that resolve it for most users. The error means Chrome could not establish a connection to the website within a set time, so the fixes below target your network, browser, and system settings in that order.

What You’ll Need

  • Access to your router’s admin page (usually via a browser at an address like 192.168.1.1 or 192.168.0.1)
  • Your Windows, macOS, or Android device’s network settings
  • Optional: a USB-to-Ethernet adapter if you want to test a wired connection on a laptop

Step-by-Step

  1. Check if the site is down for everyone. Open a different browser (Firefox, Edge, Safari) or your phone’s browser and try the same URL. If it fails everywhere, the problem is likely the website itself or your entire network. Try a major site like google.com to confirm your internet is working.
  2. Restart your modem and router. Unplug the power from both devices, wait 30 seconds, plug the modem back in first, wait for it to fully boot (lights stabilize), then plug in the router. Wait another minute and try the site again.
  3. Clear Chrome’s DNS cache. In Chrome’s address bar, type chrome://net-internals/#dns and press Enter. Click the “Clear host cache” button. Then go to chrome://net-internals/#sockets and click “Flush socket pools.” Restart Chrome.
  4. Flush your operating system’s DNS cache. On Windows, open Command Prompt as administrator and run ipconfig /flushdns. On macOS, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On Linux, run sudo systemd-resolve --flush-caches (or sudo resolvectl flush-caches on newer systems).
  5. Change your DNS server. If flushing doesn’t help, switch to a public DNS like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1). In Windows: Settings > Network & Internet > Wi-Fi or Ethernet > your connection > DNS server assignment > Edit > Manual > IPv4, then enter the addresses. On macOS: System Settings > Network > your connection > Details > DNS, then add the servers. On Android: Wi-Fi settings > your network > Modify > IP settings > Static, then set DNS 1 and DNS 2.
  6. Disable Chrome extensions. Type chrome://extensions in the address bar, toggle off all extensions, then try the site. If it works, re-enable them one by one to find the culprit. Pay special attention to VPN, ad-blocker, and security extensions.
  7. Turn off your VPN or proxy. If you use a VPN, disconnect it and try the site. If you use a proxy, go to Chrome settings > System > “Open your computer’s proxy settings” and disable the proxy or set it to automatic detection. On Windows, also check Settings > Network & Internet > Proxy and turn off “Use a proxy server.”
  8. Reset Chrome’s flags. Type chrome://flags in the address bar, click “Reset all” at the top right, and restart Chrome. This reverts experimental settings that can break connections.
  9. Disable IPv6 temporarily. On Windows, go to Network Settings > your adapter > Properties, uncheck “Internet Protocol Version 6 (TCP/IPv6)” and click OK. On macOS, System Settings > Network > your connection > Details > TCP/IP, change Configure IPv6 to Link-local only. Restart your network adapter. Re-enable IPv6 after testing.
  10. Run Chrome’s built-in cleanup. Go to chrome://settings/cleanup and click “Find and remove harmful software.” This removes malware that can interfere with network requests.
  11. Reset Chrome to default settings. Go to chrome://settings/reset and click “Restore settings to their original defaults.” This disables extensions, clears temporary data, and resets shortcuts—but keeps your bookmarks and saved passwords.
  12. Check your firewall or antivirus. Temporarily disable your firewall (Windows Defender Firewall or a third-party one) and try the site. If it works, add Chrome to the allowed apps list. Do the same for antivirus software, which sometimes blocks connections it misidentifies.
  13. Test with a wired connection. If you’re on Wi-Fi, plug in an Ethernet cable directly to the router and try again. This isolates Wi-Fi interference or a failing wireless adapter.

Common Mistakes

  • Skipping the router restart. Many users try software fixes first, but a simple router power cycle resolves a large percentage of timeout errors.
  • Only clearing Chrome’s cache, not the DNS cache. Clearing browsing data (Ctrl+Shift+Del) does not flush DNS. You need the specific steps in step 3 and 4.
  • Leaving VPN or proxy on. VPNs and proxies are a frequent cause. Even if they work for other sites, some servers or regions may be blocked or slow.
  • Disabling IPv6 and forgetting to re-enable it. Some networks require IPv6. If you disable it and the problem persists, turn it back on.
  • Ignoring the website itself. If the site is down for everyone, none of these steps will help. Always check with another device or browser first.

Tips

  • Use Chrome’s Incognito mode (Ctrl+Shift+N) as a quick test. If the site loads there, the issue is likely an extension or cached data.
  • Check the date and time on your computer. Incorrect system time breaks HTTPS connections and can cause timeouts.
  • Update your network drivers. Outdated Wi-Fi or Ethernet drivers can cause intermittent timeouts. On Windows, use Device Manager to check for updates.
  • Try a different Chrome profile. Create a new profile via the profile icon top right and test the site there. A corrupted profile can cause this error.
  • Use Chrome’s “Network” panel in Developer Tools (F12 > Network tab) and reload the page. The red entries show which request timed out, which can help identify if it’s the main page or a resource like an image or script.

Troubleshooting

If you’ve followed all steps and still see ERR_TIMED_OUT:

  • Try a different browser. If the site works in Firefox or Edge but not Chrome, the problem is Chrome-specific. A full uninstall and reinstall of Chrome (back up your bookmarks first) may be needed.
  • Check your hosts file. On Windows, open Notepad as administrator and open C:\Windows\System32\drivers\etc\hosts. On macOS/Linux, open /etc/hosts. Look for any lines that block the site you’re trying to reach (they’d contain the domain name). Remove those lines and save.
  • Test with a different network. Use your phone’s mobile hotspot or a public Wi-Fi network. If the site loads there, the problem is your home network or ISP. Contact your internet service provider.
  • Check router settings. Log into your router and look for parental controls, content filtering, or MAC address filtering that might block the site. Also check if the router’s firewall is set too aggressively.
  • Scan for malware. Run a full system scan with Windows Defender or your antivirus. Malware can modify network settings or redirect traffic.
  • Try a different DNS port. Some ISPs block port 53 (standard DNS). Use DNS over HTTPS in Chrome: Settings > Privacy and security > Security > “Use secure DNS” and select a provider like Google or Cloudflare.

Frequently Asked Questions

Why does ERR_TIMED_OUT happen only on some websites?
It usually means those specific sites have slow servers, are geographically far from you, or their hosting provider is having issues. It can also happen if a firewall or extension blocks that particular domain.

Is ERR_TIMED_OUT the same as “This site can’t be reached”?
Yes, ERR_TIMED_OUT is one of the specific error codes shown under that general message. Other codes include ERR_CONNECTION_REFUSED (the server actively rejected the connection) and ERR_NAME_NOT_RESOLVED (DNS couldn’t find the address).

Will clearing my browsing history fix this error?
Clearing regular browsing history rarely helps. The relevant caches are the DNS cache, socket pools, and SSL state. Follow steps 3 and 4 instead of clearing your history.

Can a bad Chrome update cause ERR_TIMED_OUT?
Yes, occasionally a Chrome update introduces a bug. If the error started right after an update, try the “Reset all” option in chrome://flags, or check Chrome’s help forum for known issues. Reinstalling Chrome also reverts to the latest stable build.

Does this error mean my internet is broken?
Not necessarily. If other websites load fine, your internet is working. The timeout is specific to the connection between Chrome and that particular server. If no websites load, the issue is your network connection or ISP.

How long should I wait before trying again?
If the site’s server is overloaded, it may recover in minutes. If it’s a network issue on your side, the fixes above should work immediately. If the error persists for hours on one site while others work, check the site’s status page or social media for outages.

Related

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 →