When Chrome displays ERR_CONNECTION_TIMED_OUT, it means the browser sent a request to a website but did not receive a response in time. The issue can come from the visitor’s device, the local network, Chrome settings, security software, DNS problems, or the website’s server. In most cases, the error is fixable with a structured troubleshooting process rather than a complex technical repair.

TLDR: ERR_CONNECTION_TIMED_OUT in Chrome usually means the browser cannot reach a website before the connection request expires. The fastest fixes include restarting the router, checking the internet connection, clearing Chrome’s cache, disabling VPN or proxy settings, and flushing DNS. If the problem affects only one website, the site’s server may be down or blocking the connection.

What ERR_CONNECTION_TIMED_OUT Means in Chrome

The ERR_CONNECTION_TIMED_OUT message appears when Chrome waits too long for a response from a website. Instead of loading the page, Chrome ends the attempt and shows the timeout error. This is different from a “page not found” error, which usually means the address does not exist. A timeout means the request was sent, but a response was not received within the expected time.

This error may affect one website, several websites, or all browsing activity. If only one site fails to load, the problem may be related to that website’s server, firewall rules, DNS records, or hosting environment. If every website shows the same message, the cause is more likely local: the device, router, browser, DNS settings, firewall, VPN, or internet service provider.

Common Causes of ERR_CONNECTION_TIMED_OUT

Before attempting repairs, it helps to understand the most common causes. Chrome may show this error because of:

  • Unstable internet connection: Weak Wi Fi, router problems, or an ISP outage can interrupt requests.
  • Browser cache issues: Old or corrupted cached files can interfere with loading.
  • DNS problems: The device may be unable to translate the website address into the correct server IP address.
  • VPN or proxy interference: A VPN, proxy server, or corporate network filter may block or delay traffic.
  • Firewall or antivirus rules: Security software may mistakenly block Chrome or the target website.
  • Website server issues: The destination website may be overloaded, offline, or misconfigured.
  • Incorrect network settings: Bad TCP IP settings, a broken hosts file entry, or outdated network drivers can cause timeouts.

1. Check Whether the Website Is Down

The first step is to confirm whether the problem is local or site specific. A user can try opening the same website on another device, such as a phone using mobile data. If the site works on mobile data but not on the original network, the issue is likely related to the home or office connection. If the website fails everywhere, it may be temporarily down.

Another useful method is to test different websites in Chrome. If popular websites such as search engines or news sites load normally, but one specific site does not, the problem may be on that site’s end. In that case, waiting a few minutes or contacting the site owner may be the only practical option.

2. Restart the Router and Device

A simple restart often fixes temporary network issues. The person troubleshooting should turn off the router, wait at least 30 seconds, and then turn it back on. This allows the router to refresh its connection to the internet service provider and clear temporary connection problems.

The device should also be restarted. Restarting clears background processes, resets temporary network behavior, and closes applications that may be interfering with Chrome. After both the router and device restart, Chrome should be opened again to test the website.

3. Clear Chrome Cache and Cookies

Chrome stores cached files, cookies, and site data to speed up browsing. However, old or corrupted data can sometimes cause loading problems, including timeout errors. Clearing this data gives Chrome a fresh start.

  1. Open Chrome.
  2. Click the three dot menu in the top right corner.
  3. Select Settings.
  4. Go to Privacy and security.
  5. Choose Delete browsing data.
  6. Select Cached images and files and Cookies and other site data.
  7. Set the time range to All time if the problem has lasted for a while.
  8. Click Delete data.

After clearing the data, Chrome should be restarted. The website may ask the user to sign in again because cookies were removed.

4. Disable Extensions Temporarily

Chrome extensions can modify web requests, block scripts, redirect traffic, or interfere with security certificates. Ad blockers, privacy tools, VPN extensions, and script blockers are especially common causes of connection problems.

To test extensions, the user can open an Incognito window because many extensions are disabled there by default. If the website loads in Incognito, an extension may be responsible. Extensions can be managed by typing chrome://extensions into the address bar. From there, each extension can be turned off temporarily. After disabling extensions, Chrome should be restarted and the site tested again.

5. Check VPN and Proxy Settings

A VPN or proxy server can cause ERR_CONNECTION_TIMED_OUT if the remote server is slow, blocked, misconfigured, or overloaded. The simplest test is to disconnect the VPN and reload the page. If the site loads without the VPN, the VPN server or location may be the problem.

Proxy settings should also be checked. On many systems, Chrome uses the operating system’s proxy configuration. If a proxy is enabled accidentally, traffic may be routed through a server that no longer works.

On Windows, proxy settings can be reviewed under Settings > Network & Internet > Proxy. The option for manual proxy setup should be disabled unless a trusted proxy is required. On macOS, proxy settings can be checked under System Settings > Network, then the active connection and proxy options.

6. Flush DNS and Renew the IP Address

DNS translates website names into IP addresses. If the DNS cache contains outdated or incorrect information, Chrome may fail to connect. Flushing DNS forces the system to request fresh DNS information.

On Windows, the user can open Command Prompt as administrator and run these commands:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset

After running the commands, the device should be restarted.

On macOS, the DNS flush command depends on the version, but a common command is:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

The system may ask for the administrator password. Once the DNS cache is cleared, Chrome should be tested again.

7. Change DNS Servers

If the ISP’s DNS servers are slow or unreliable, switching to a public DNS provider may fix the timeout. Popular options include Google Public DNS and Cloudflare DNS.

  • Google DNS: 8.8.8.8 and 8.8.4.4
  • Cloudflare DNS: 1.1.1.1 and 1.0.0.1

DNS settings can be changed in the operating system’s network settings or directly on the router. Changing DNS on the router applies the setting to all connected devices. Changing it only on one computer affects only that machine.

8. Check Firewall and Antivirus Software

Firewalls and antivirus tools protect devices from unsafe connections, but they can sometimes block legitimate traffic. If Chrome is not allowed through the firewall, or if a security suite is filtering web traffic aggressively, pages may time out.

The user should check whether Chrome is allowed in the firewall settings. On Windows, this can be done through Windows Security > Firewall & network protection > Allow an app through firewall. Chrome should be allowed on the appropriate private or public network.

Temporarily disabling third party antivirus web protection can also help identify the cause. However, security tools should only be disabled briefly for testing and turned back on afterward. If disabling the tool fixes the issue, its settings should be adjusted rather than leaving protection off.

9. Reset Chrome Settings

If Chrome itself has a configuration problem, resetting the browser may help. This restores default settings, disables extensions, clears temporary settings, and resets startup pages and search engine preferences. It does not remove bookmarks or saved passwords.

  1. Open Chrome Settings.
  2. Select Reset settings.
  3. Click Restore settings to their original defaults.
  4. Confirm by choosing Reset settings.

This step is useful when the connection works in another browser but fails repeatedly in Chrome.

10. Update Chrome, Network Drivers, and the Operating System

Outdated software can cause compatibility problems. Chrome should be updated by opening the three dot menu, selecting Help, and then choosing About Google Chrome. Chrome will check for updates automatically and prompt for a restart if needed.

Network drivers, especially Wi Fi and Ethernet drivers, should also be kept current. On Windows, the Device Manager can be used to update network adapters. On macOS, network driver updates are generally included with system updates.

Operating system updates may also repair networking bugs, security certificate issues, or DNS behavior. After updates are installed, the device should be restarted before further testing.

11. Inspect the Hosts File

The hosts file can manually map websites to IP addresses. If it contains an incorrect entry, Chrome may try to connect to the wrong server and eventually time out. This is less common but important, especially on devices previously used for development, testing, or security work.

On Windows, the hosts file is usually located at:

C:\Windows\System32\drivers\etc\hosts

On macOS and Linux, it is located at:

/etc/hosts

Any suspicious entry for the affected website should be removed or commented out. The file should be edited carefully because incorrect changes can affect network behavior.

12. Contact the Internet Service Provider or Website Owner

If all local troubleshooting fails, the issue may be outside the user’s control. The internet service provider may be experiencing routing problems, DNS failures, or regional outages. In that case, contacting the ISP can confirm whether there is a known issue.

If only one website is affected, the website owner or hosting provider may need to investigate server logs, firewall rules, DNS configuration, or traffic blocks. A site may also block requests from certain regions, IP ranges, VPNs, or suspicious traffic patterns.

Preventing Future Timeout Errors

While not every timeout can be prevented, good maintenance reduces the chances of repeated errors. Chrome should be kept updated, the router should be restarted occasionally, and unnecessary extensions should be removed. Users who rely on VPNs should choose stable servers and switch locations when a site fails to load.

It is also helpful to use reliable DNS servers and keep security software properly configured. If timeout errors happen frequently across multiple devices, the router may need a firmware update or replacement. A weak Wi Fi signal can also be improved by moving closer to the router, using Ethernet, or adding a mesh network system.

Conclusion

ERR_CONNECTION_TIMED_OUT in Chrome is usually a sign that something is preventing a website from responding quickly enough. The fix may be as simple as restarting the router or clearing Chrome’s cache, but more persistent cases may require DNS changes, firewall checks, proxy adjustments, or network resets. By working through the steps in order, a user can identify whether the problem is caused by Chrome, the device, the local network, the ISP, or the website itself.

FAQ

What does ERR_CONNECTION_TIMED_OUT mean?

It means Chrome tried to connect to a website but did not receive a response before the request expired. The website may be unavailable, or something on the user’s device or network may be blocking the connection.

Is ERR_CONNECTION_TIMED_OUT caused by Chrome?

Sometimes, but not always. Chrome cache, extensions, or settings can cause the error, but router problems, DNS issues, firewalls, VPNs, and website server problems are also common causes.

Why does the error happen on only one website?

If only one website times out, that site may be down, overloaded, blocking the user’s IP address, or misconfigured. The user can test the site from another network to confirm whether the issue is local.

Can a VPN cause ERR_CONNECTION_TIMED_OUT?

Yes. A VPN can slow traffic, route requests through blocked servers, or trigger website security filters. Disconnecting the VPN or switching to another VPN location can often resolve the issue.

Does clearing cache fix the timeout error?

Clearing cache can fix the error when corrupted or outdated browser data interferes with loading. It is one of the safest and easiest early troubleshooting steps.

When should the user contact the ISP?

The ISP should be contacted if multiple websites fail across several devices, especially after restarting the router, changing DNS, and testing without VPN or proxy settings.