---
title: "ERR_CONNECTION_TIMED_OUT on Chrome: cause and fix"
description: "Chrome's prediction service and a full socket pool can hold a dead connection open, so the timeout repeats in Chrome while the site loads elsewhere."
canonical: "https://lemwatch.com/errors/err-connection-timed-out/on-chrome"
source: "https://lemwatch.com"
---

# ERR_CONNECTION_TIMED_OUT on Chrome

> Chrome's prediction service and a full socket pool can hold a dead connection open, so the timeout repeats in Chrome while the site loads elsewhere.

## Why it happens on Chrome

 Chrome's prediction service and a full socket pool can hold a dead connection open, so the timeout repeats in Chrome while the site loads elsewhere.

## The fix on Chrome

 Test the URL in an incognito window with extensions disabled. If it loads, an extension or a stale socket pool is the cause — flush it at chrome://net-internals/#sockets.

## If that didn't fix it

 Chrome has its own failure mode, but ERR_CONNECTION_TIMED_OUT has a wider set of causes. The most common one overall is: The origin server is down or the web server process has stopped.

 Check the service is running and listening on the expected port, then restart it and confirm from outside the network.

## Check your own domain

 An uptime probe from outside your network tells you whether the server is unreachable for everyone or only from where you are sitting — which is the first fork in every timeout diagnosis.

## Frequently asked questions

### Why does ERR_CONNECTION_TIMED_OUT happen on Chrome?

 Chrome's prediction service and a full socket pool can hold a dead connection open, so the timeout repeats in Chrome while the site loads elsewhere.

### How do I fix ERR_CONNECTION_TIMED_OUT on Chrome?

 Test the URL in an incognito window with extensions disabled. If it loads, an extension or a stale socket pool is the cause — flush it at chrome://net-internals/#sockets.

### What does ERR_CONNECTION_TIMED_OUT mean?

 DNS resolved and the browser tried to open a TCP connection, but nothing answered before the timeout. The server is unreachable, overloaded, or a firewall is dropping the packets silently.


## Related

- [All causes of ERR_CONNECTION_TIMED_OUT](https://lemwatch.com/errors/err-connection-timed-out)
- [All website error codes](https://lemwatch.com/errors)
- [ERR_CONNECTION_TIMED_OUT on Android](https://lemwatch.com/errors/err-connection-timed-out/on-android)
- [ERR_CONNECTION_TIMED_OUT on Cloudflare](https://lemwatch.com/errors/err-connection-timed-out/in-cloudflare)
- [ERR_CONNECTION_TIMED_OUT on WordPress](https://lemwatch.com/errors/err-connection-timed-out/in-wordpress)
- [Free Uptime & response check](https://lemwatch.com/tools/website-uptime)
- [ERR_EMPTY_RESPONSE: The server sent no data](https://lemwatch.com/errors/err-empty-response)
- [All monitoring checks](https://lemwatch.com/features)