Browser Connection Troubleshooting

How to Fix ERR_TIMED_OUT Error in Browser

A practical step-by-step guide to resolving connection timeout errors in Google Chrome, Microsoft Edge, Firefox, Opera, Brave, and other modern browsers.

🌐 Chrome · Edge · Firefox · Opera 📡 DNS · Proxy · VPN 🛡️ Firewall & Antivirus 🧰 Windows 10 / Windows 11
Section 01

What Does the ERR_TIMED_OUT Error Mean?

⏱️
ERR_TIMED_OUT
This site can’t be reached. example.com took too long to respond.
Try checking the connection, checking the proxy and the firewall, or running Windows Network Diagnostics.

ERR_TIMED_OUT means that your browser sent a request to a website, but the response did not arrive within the expected time. In simple terms, the browser waited for the server, network, DNS resolver, proxy, or local connection to answer — and eventually gave up.

The error is especially common in Google Chrome and Chromium-based browsers such as Microsoft Edge, Opera, Brave, and Vivaldi. In Firefox, the same problem may appear as “The connection has timed out”. The wording is different, but the troubleshooting logic is almost the same.

ℹ️
Important A timeout does not always mean the website is down. The cause may be your browser cache, DNS settings, proxy configuration, VPN route, antivirus HTTPS scanning, firewall rules, router, or your internet provider.
Section 02

Most Common Causes of ERR_TIMED_OUT in Chrome, Edge, and Firefox

The fastest way to fix the error is to identify whether it is caused by your device, your browser, your network, or the website itself. The most common reasons are listed below.

📶
Unstable Internet Connection
Packet loss, weak Wi‑Fi, overloaded mobile hotspot, or router issues can delay server responses until the browser times out.
🌍
DNS Resolution Problems
A slow, incorrect, or cached DNS response can prevent the browser from reaching the correct IP address.
🧱
Firewall or Antivirus Blocking
Security software may block the browser, inspect HTTPS traffic, or prevent access to specific domains.
🕵️
Proxy or VPN Misconfiguration
A dead proxy server, overloaded VPN node, or corporate filtering rule may interrupt the route to the website.
🧩
Browser Extensions
Ad blockers, privacy extensions, script blockers, and security add-ons may interfere with page loading.
🖥️
Website Server Issues
The target server may be overloaded, temporarily unavailable, blocked by its own firewall, or misconfigured.
Section 03

Quick Checks Before You Start Fixing ERR_TIMED_OUT

Before changing Windows network settings, run these simple checks. They help determine whether the problem is local or website-side.

01
Open the Same Website on Another Device
Fastest way to locate the source
  1. Try the same website on your phone using mobile data instead of Wi‑Fi.
  2. Try another browser on the same computer.
  3. Ask another person on a different network to open the site.

If the site works everywhere except your computer, focus on browser, DNS, firewall, and Windows network settings. If it fails everywhere, the website may be down or blocking traffic.

02
Check Whether Only One Website Is Affected
Single-site vs. global problem

If all websites are slow or timing out, the issue is probably your connection, DNS, router, VPN, proxy, or ISP. If only one domain fails, the cause is more likely website-side blocking, DNS propagation, server overload, or a route problem between your network and that server.

⚠️
Do Not Skip This If you are connected through a VPN, proxy, corporate network, public Wi‑Fi, or hotel Wi‑Fi, test the page without that network layer first. Many ERR_TIMED_OUT cases are caused by routing or filtering, not by the browser itself.
Section 04

How to Fix ERR_TIMED_OUT in the Browser

Start with browser-level fixes. They are safe, fast, and often enough to solve the problem without changing system-wide network settings.

01
Clear Browser Cache and Cookies
Recommended first fix

Corrupted cached files, outdated cookies, and old redirect data can make the browser repeatedly request the wrong resource or wait for a broken connection.

  1. In Chrome or Edge, press Ctrl + Shift + Del.
  2. Select All time as the time range.
  3. Enable Cookies and other site data and Cached images and files.
  4. Click Clear data, restart the browser, and open the website again.
02
Disable Browser Extensions Temporarily
Useful for ad blockers and privacy tools
  1. Open chrome://extensions/ in Chrome or edge://extensions/ in Edge.
  2. Turn off ad blockers, VPN extensions, script blockers, download managers, and privacy add-ons.
  3. Restart the browser and check the website again.
  4. If the page loads, enable extensions one by one to find the problematic add-on.
03
Reset Browser Network-Related Settings
For persistent timeout errors

In Chrome, open chrome://settings/reset and choose Restore settings to their original defaults. This disables extensions, clears temporary site settings, and resets browser configuration without deleting bookmarks or saved passwords.

04
Update or Reinstall the Browser
When the error appears only in one browser

Open the browser’s About page and install available updates. For example, Chrome uses chrome://settings/help, while Edge uses edge://settings/help. If updating does not help, uninstall the browser, restart Windows, and install the latest version from the official website.

Section 05

Windows Network Fixes for ERR_TIMED_OUT

If the timeout occurs in several browsers, the problem is likely system-wide. The following commands reset common Windows network components.

01
Flush DNS Cache and Renew the IP Address
Safe command-line repair
  1. Right-click Start and open Terminal (Admin) or Command Prompt (Admin).
  2. Run the commands below one by one.
  3. Restart the browser and test the website.
Command Prompt — DNS and IP Refreshipconfig /flushdns
ipconfig /release
ipconfig /renew
02
Reset Winsock and TCP/IP Stack
For damaged network configuration

Winsock and TCP/IP corruption can cause browsers to fail while other apps appear to work normally. 

Command Prompt — Network Stack Resetnetsh winsock reset
netsh int ip reset

Restart Windows after running these commands. The reset does not delete personal files, but it may remove custom network settings such as static IP configuration.

03
Run Windows Network Reset
Last resort for local network issues
  1. Open Settings → Network & Internet.
  2. Open Advanced network settings.
  3. Select Network reset.
  4. Click Reset now and restart your PC.

After the reset, reconnect to Wi‑Fi and reconfigure VPN clients, virtual adapters, or static IP settings if you use them.

Section 06

Fix DNS, Proxy, VPN, Firewall, and Antivirus Causes

These components sit between your browser and the target website. A wrong setting in any of them can lead to a connection timeout.

01
Change DNS Servers
Effective for slow or broken DNS resolution

Try a reliable public DNS provider such as Google DNS, Cloudflare DNS, or Quad9. In Windows 11 and Windows 10, open Settings → Network & Internet → select your connection → edit DNS settings.

Provider Primary DNS Secondary DNS
Google DNS 8.8.8.8 8.8.4.4
Cloudflare DNS 1.1.1.1 1.0.0.1
Quad9 9.9.9.9 149.112.112.112
02
Disable Proxy Settings
Common cause after using corporate tools or proxy apps
  1. Open Settings → Network & Internet → Proxy.
  2. Turn off Use a proxy server unless you intentionally use one.
  3. Leave Automatically detect settings enabled for most home networks.
03
Test Without VPN
Checks routing and geo-blocking problems

Disconnect from the VPN and reload the website. If the page opens, switch to another VPN server, update the VPN client, or check whether the website blocks traffic from the VPN provider’s IP range.

04
Check Firewall and Antivirus Rules
For blocked browser traffic
  1. Make sure your browser is allowed through Windows Defender Firewall.
  2. Temporarily disable third-party antivirus web protection or HTTPS scanning.
  3. If the site starts working, add a proper exception or reinstall the security product.
⚠️
Security Note Disable antivirus or firewall protection only for a short test. Do not leave your computer unprotected. If disabling protection fixes the problem, adjust the rule instead of keeping protection off.
Section 07

Router and Internet Connection Fixes for ERR_TIMED_OUT

If multiple devices on the same network show timeout errors, check the router and internet connection.

01
Restart the Router Correctly
Simple but often effective
  1. Turn off the router or unplug its power cable.
  2. Wait at least 30 seconds.
  3. Turn the router back on and wait until the internet indicator is stable.
  4. Restart the browser and test the website again.
02
Switch Between Wi‑Fi and Ethernet
Checks local wireless problems

If possible, connect the computer directly to the router using an Ethernet cable. If the error disappears, the issue may be weak Wi‑Fi signal, interference, incorrect Wi‑Fi driver settings, or a congested wireless channel.

03
Contact Your ISP if Many Sites Time Out
When local fixes do not help

If many unrelated websites time out on all devices, your internet provider may have a routing, DNS, or outage problem. Provide them with the affected domains and the results of ping and tracert tests.

Section 08

ERR_TIMED_OUT for Website Owners: Server-Side Checks

If users report that your website takes too long to respond, the issue may be on the hosting or server side. Check the following areas.

✅ Server-Side Items to Check

  • Web server status: Apache, Nginx, LiteSpeed, IIS, or Node.js service
  • CPU, RAM, disk I/O, and database load during peak traffic
  • Firewall rules, fail2ban, WAF, CDN, and country/IP blocking
  • DNS records, nameservers, and recent DNS propagation changes
  • SSL/TLS configuration and redirect loops between HTTP and HTTPS
  • CDN origin connectivity between Cloudflare, reverse proxy, and hosting server

⚠️ Symptoms of a Server Problem

  • The website times out from many networks and locations
  • Static pages work, but dynamic pages or admin pages hang
  • The site works without CDN but fails through CDN
  • Server logs show 502, 503, 504, upstream timeout, or database errors
  • Only some countries, IP ranges, or ISPs are affected
  • Resource usage spikes when the timeout appears
ℹ️
For Webmasters If your site uses a CDN or reverse proxy, always test both the public domain and the origin server. A timeout may be caused by the origin server refusing CDN connections, not by the user’s browser.
Section 09

Diagnostic Commands to Find the Cause of ERR_TIMED_OUT

These commands help determine whether the domain resolves correctly, whether the server responds, and where the route fails.

Command Purpose What to Look For
ping example.com Checks basic reachability Packet loss, high latency, or no response
tracert example.com Shows the route to the server Where the route stops or becomes very slow
nslookup example.com Checks DNS resolution Wrong IP, DNS timeout, or no records
curl -I https://example.com Checks HTTP response headers Connection timeout, redirect loop, or server error

Quick Command Set for Windows

Run these commands in Command Prompt or Windows Terminal to collect useful troubleshooting data:

Command Prompt — Website Timeout Diagnosticsnslookup example.com
ping example.com
tracert example.com
curl -I https://example.com

Replace example.com with the real domain. If DNS fails, focus on DNS settings. If DNS works but the route stops, check VPN, proxy, ISP, firewall, or server-side filtering. If curl receives a response but the browser does not, focus on browser cache, extensions, or antivirus web protection.

Section 10

Frequently Asked Questions About ERR_TIMED_OUT

Q Is ERR_TIMED_OUT a browser error or an internet problem? ▼
It can be either. If the error appears in only one browser, it is usually caused by cache, extensions, or browser settings. If it appears in all browsers and on several devices, the cause is more likely DNS, router, VPN, firewall, ISP routing, or the website server.
Q Why does ERR_TIMED_OUT happen only on one website? ▼
A single-site timeout often points to server-side issues, DNS propagation, CDN problems, IP blocking, firewall filtering, or a route problem between your network and that website. Test the site from another device and another network to confirm.
Q Can antivirus cause ERR_TIMED_OUT? ▼
Yes. Antivirus web shields, HTTPS scanning, and firewall modules can delay or block browser traffic. Temporarily disable web protection for testing only. If the site loads after that, update the antivirus, reset its firewall rules, or add a safe exception.
Q Can changing DNS fix ERR_TIMED_OUT? ▼
Yes, especially when your current DNS resolver is slow, unavailable, cached incorrectly, or blocked by the network. Try well-known DNS providers such as Google DNS, Cloudflare DNS, or Quad9, then flush the DNS cache with ipconfig /flushdns.
Q Why does the website work on mobile data but not on Wi‑Fi? ▼
This usually means the problem is related to your Wi‑Fi network, router, ISP DNS, proxy, firewall, or IP-based blocking. Restart the router, change DNS servers, disable proxy/VPN, and test with another device on the same Wi‑Fi network.
Q Is it safe to reset network settings in Windows? ▼
In most cases, yes. Windows Network Reset removes and reinstalls network adapters and returns many network settings to defaults. However, you may need to reconnect to Wi‑Fi, reinstall VPN adapters, or re-enter static IP and DNS settings afterward.

✅ Summary: The Best Way to Fix ERR_TIMED_OUT

ERR_TIMED_OUT usually means the browser cannot receive a timely response from the website. Start with simple checks: open the site in another browser, test another device, clear cache, disable extensions, and restart the router. If the error continues, flush DNS, renew the IP address, reset Winsock, change DNS servers, and check proxy, VPN, firewall, and antivirus settings.

If the website fails from multiple networks, the issue may be server-side. Website owners should check hosting resources, DNS records, CDN configuration, firewall rules, and web server logs. By narrowing down whether the problem is local, network-related, or server-side, you can fix the timeout much faster.