ERR_CONNECTION_TIMED_OUT Not Going Away? Do This Now!

You click on a link, the loading bar slowly advances across the screen—and then Chrome displays this error: ERR_CONNECTION_TIMED_OUT. You refresh the page. Still, nothing happens. You check your Wi-Fi. It seems fine. But the page just won’t open.

The ERR_CONNECTION_TIMED_OUT error means that your browser tried to reach a website’s server for about 30 seconds—and then gave up. It is just like calling someone who never picks up the phone.

The good news is that this issue can almost always be fixed. Whether it is a network glitch, an incorrect setting, or a server-side problem—this guide explains, step-by-step, every solution that works in 2026.

Instant Fixes — Try These First

Before diving deep into the settings, try performing these quick checks. In more than half of the cases, these resolve the issue:

Check if other websites load — If only one site fails, the problem may be on their end.

Restart your router — Unplug it for 30 seconds, plug back in, and wait 60 seconds.

Switch from Wi-Fi to mobile data — if it loads on data, the issue lies with your network.

Disable VPN or antivirus temporarily — These frequently block or redirect connections.

Try a different browser — Confirms if the error is browser-specific or system-wide.

Open the site in Incognito mode — this eliminates the possibility of corrupted cache or extension conflicts.

What is ERR_CONNECTION_TIMED_OUT?

Definition: ERR_CONNECTION_TIMED_OUT is a browser error that appears when your browser sends a request to a website's server but does not receive a response within the default timeout window—which is typically around 30 seconds. Consequently, the browser terminates the connection and displays this error instead of rendering the page.

Think of it like knocking on a door. If no one answers after 30 seconds, you give up and walk away—and your browser does exactly the same thing.

This error shows up most often in Google Chrome, but Firefox calls it “The connection has timed out,” Edge says “Hmmm… can’t reach this page,” and Safari shows “Safari Can’t Open the Page.” Same problem, different labels.

Why Does This Error Occur?

The causes for this could lie with you, the network, or the server. The most common causes are listed here:

• Unstable or slow internet connection — the browser is unable to maintain a stable link with the server.
• Firewall or antivirus blocking — Security software mistakenly blocks outgoing requests.
• Incorrect Proxy Settings — An incorrectly configured proxy redirects traffic in the wrong direction.
• Corrupt DNS Cache — Lookups fail due to outdated DNS records.
• Server Overload (For Website Owners) — The site’s hosting server is so slow that it is unable to respond in a timely manner.
• Outdated Network Drivers — Outdated drivers prevent proper communication with the network hardware.

Step-by-Step Solution For ERR_CONNECTION_TIMED_OUT

1. Check and Reset Your Internet Connection

Start with the basics. A weak or broken connection is the primary cause of this error.

• To ensure that your connection is active, perform a speed test at fast.com or speedtest.net.
• If the speed is slow, unplug your router from the power socket.
• Wait 30 seconds, then plug it back in and allow 60 seconds to reconnect.
• Try loading the website again.

2. Disable Proxy Settings

A misconfigured proxy is one of the most hidden causes of this error—and most users never even think to check for it.

• Press Win + R, type inetcpl.cpl, and press Enter.
• Go to the Connections tab → click LAN Settings.
• Uncheck “Use a proxy server for your LAN” if it’s enabled.
• Check “Automatically detect settings” instead.
• Click OK, close, and retry the site.

3. Flush DNS Cache 

An outdated DNS cache can lead your browser to a dead end every time. Clearing it initiates a fresh lookup.

• Press Win + R, type cmd, run as Administrator.
• Type ipconfig /flushdns and press Enter.
• Then type ipconfig /release followed by ipconfig /renew.
• Restart your browser and test site again.

4. Change Your DNS Server

Your ISP’s DNS may be slow or temporarily down. Switching to Google or Cloudflare DNS is fast and free.

• Go to Control Panel → Network & Sharing Center → Change adapter settings.
• Right-click your active connection → Properties → IPv4 → Properties.
• Select “Use the following DNS server addresses.”
• Enter: Preferred: 8.8.8.8 / Alternate: 8.8.4.4 (Google) or 1.1.1.1 / 1.0.0.1 (Cloudflare).
• Click OK and flush DNS again (Method 3) to apply.

5. Disable Firewall or Antivirus Temporarily

Security software sometimes blocks even completely safe websites. Check this carefully—disable it only for a short time.

• Go to Control Panel → Windows Defender Firewall → Turn off (temporarily).
• Try loading the site. If it works, add the site to your antivirus/firewall whitelist.
• Re-enable your security software immediately after testing.

6. Reset TCP/IP Stack 

A corrupted TCP/IP stack can cause persistent timeout errors, even after other troubleshooting steps have been taken. This constitutes a deep reset.

• Open Command Prompt as Administrator.
• Run: netsh int ip reset
• Run: netsh winsock reset
• Restart your computer. Note: Some security programs may need to be reinstalled after this step.

7. For WordPress Site Owners — Increase PHP Execution Time

If your WordPress site is displaying this error, it is possible that the server is timing out due to heavy scripts. This is a common occurrence on shared hosting.

• Open your php.ini file via cPanel or FTP.
• Find max_execution_time and increase it from 30 to 60 or 120.
• Alternatively, add this to your wp-config.php: set_time_limit(120);
• Save changes and reload your site. Contact your host if you can’t edit these files.

How to Prevent ERR_CONNECTION_TIMED_OUT

• Use a trusted DNS provider, such as Google (8.8.8.8) or Cloudflare (1.1.1.1), as your default.
• Regularly update your router firmware and network drivers.
• Avoid using public Wi-Fi hotspots for important tasks—they are often unstable.
• Regularly clear your browser’s cache and Chrome’s internal DNS cache.
• If you run a WordPress site, upgrade to VPS or Managed Hosting to avoid server timeout limits.

Pro Tips & Best Practices

If this error is occurring on only one specific site, it is highly likely that the problem lies with the server—not on your end. Before spending time troubleshooting the issue on your system, use downforeveryoneorjustme.com to confirm this.

Always flush your DNS cache after changing the DNS server address. Without this step, the old cached records will continue to be used, and the new DNS settings will have no effect.

If you use Chrome extensions—such as privacy tools, ad blockers, or VPN extensions—disable them one by one. Even a single faulty extension can cause this error to appear on every site.

Frequently Asked Questions