ERR_CONNECTION_TIMED_OUT: why it happens and how to fix it
ERR_CONNECTION_TIMED_OUT means the browser never received any answer to its connection attempt within the timeout window, unlike a refused connection, which gets a fast, explicit rejection. Something between the client and the server is silently dropping the request.
What ERR_CONNECTION_TIMED_OUT means
When a browser opens a connection, it sends a SYN packet and waits for a SYN-ACK in reply. A timeout means no reply arrived at all, neither an acceptance nor a rejection, before the client gave up. That silence is the key difference from a refused connection: refusal is a fast, definite no from the target machine, while a timeout means the packet may never have reached anything that could answer it. Chrome typically waits around 30 seconds before giving up and showing the error.
The operating system usually retries the SYN a few times before giving up, spacing the attempts out over the wait window rather than sending one request and waiting silently. That retry behavior is part of why a timeout takes noticeably longer to surface than a refusal: the client keeps trying in case the first attempt was lost to ordinary packet loss, and only reports the error once every retry has also gone unanswered.
How the error appears
Chrome shows "This site can't be reached ... ERR_CONNECTION_TIMED_OUT" only after the full wait, which is the clearest visual sign that separates it from a fast failure. From the command line:
curl -v --max-time 10 https://example.com/
* Trying 203.0.113.10:443...
* Connection timed out after 10001 milliseconds
curl: (28) Connection timed out after 10001 millisecondsWithout a --max-time flag, curl uses the system default, which can run well past a minute; setting the flag explicitly keeps diagnosis fast.
What causes ERR_CONNECTION_TIMED_OUT
- The host is down. A server that is powered off, hung, or unreachable at the network level cannot answer any packet, including a reset.
- A firewall silently drops the packet. A DROP rule discards the SYN without sending anything back, which is a common security posture for ports that should not be reachable from the internet.
- DNS resolves to the wrong or an outdated IP address. The browser connects to a real, reachable address, just not the one anything is actually listening on.
- A routing problem exists somewhere on the path. A misconfigured route, a broken peering link, or an ISP-level outage can strand packets before they ever reach the destination network.
- The server is overloaded and cannot accept new connections. A full connection queue or exhausted worker pool leaves incoming SYN packets unanswered even though the machine itself is running.
Refused, reset, or timed out
| Error | What happens | Typical cause |
|---|---|---|
| ERR_CONNECTION_REFUSED | Fast, explicit rejection (RST) | Nothing listening on the port, or a REJECT firewall rule |
| ERR_CONNECTION_RESET | Connection worked, then was torn down | Firewall, crash, or proxy interference mid-connection |
| ERR_CONNECTION_TIMED_OUT | No answer at all, full wait before giving up | Host down, DROP firewall rule, routing, or wrong IP |
How to tell whose fault it is
Try the same address from a different network, such as mobile data. If it connects there, the problem is local: your router, ISP, or a firewall on your own network. If it times out everywhere, the server or a network segment close to it is the cause. Running a port check from several locations at once confirms this in one step and shows whether the timeout is consistent across regions or limited to one path.
How to fix ERR_CONNECTION_TIMED_OUT
If you are a visitor
- Try a different network, such as mobile data, to rule out a local router or ISP route issue.
- Restart your router to clear a stuck routing or DNS cache entry.
- Flush your local DNS cache in case it is holding a stale, unreachable IP address for the domain.
- Disable a VPN temporarily if one is active; a VPN's own exit node can be the thing that is unreachable.
If you run the site
- Confirm the host is actually up and reachable from outside its own network, not just from a local shell on the same machine.
- Check cloud security groups and firewall rules for a DROP rule on the port in question; a rule that silently discards traffic is easy to overlook because it produces no log entry by default.
- Trace the path to confirm where packets stop:
A trace that stops cleanly at your own edge router points at a local or cloud-provider firewall rather than the wider internet.traceroute example.com mtr example.com - Confirm the service listens on
0.0.0.0, not just127.0.0.1. A service bound only to the loopback address is invisible to anything outside the machine, which looks identical to a firewall drop from the outside. - Check for connection queue exhaustion under load; a full backlog queue can leave new SYN packets unanswered even while existing connections work normally.
How to prevent ERR_CONNECTION_TIMED_OUT
A silent drop produces no error log on the server, since nothing ever received the request to log, which makes this failure mode easy to miss without active checks. Regular port and HTTP monitoring from outside the network catches an unreachable host or a silently dropped port the moment it starts, and alerts by email, SMS, voice call, Slack, Telegram and more before visitors report it themselves.
Related errors
- ERR_CONNECTION_REFUSED is a fast, explicit rejection rather than silence.
- ERR_ADDRESS_UNREACHABLE means there is no route to the address at all, rather than an unanswered attempt on a valid route.
- This site can't be reached covers the full set of connection errors Chrome groups under one heading.
Frequently asked questions
How long does Chrome wait before showing ERR_CONNECTION_TIMED_OUT?
Around 30 seconds, though the exact figure can vary by platform and network conditions. A consistently fast failure well under that time is more likely a refused connection than a timeout.
Why does the site load on my phone but time out on my laptop?
This usually points at something specific to the laptop's network path: a corporate firewall, a VPN client, or a locally cached DNS entry pointing at an unreachable address.
Can a DNS problem cause ERR_CONNECTION_TIMED_OUT instead of a DNS error?
Yes, if DNS resolves successfully but returns an IP address that nothing is reachable at, such as an old server that has since been decommissioned. The lookup succeeds, but the connection attempt to that address then times out.
Is ERR_CONNECTION_TIMED_OUT the same on every browser?
The underlying cause is the same, but the wording differs: Firefox shows "The connection has timed out," and Safari shows "This webpage is unable to load" after a similar wait.
Does a timeout always mean the server is down?
No. It means nothing answered the connection attempt, which can also mean a firewall silently dropped it, a route is broken somewhere in between, or DNS points at the wrong address while the real server is fine.
Why does the same site time out for me but load for a coworker on the same office network?
Check for a per-device VPN client, a locally cached DNS entry, or a browser-level proxy setting that only your machine has configured; a shared network problem usually affects everyone on it equally, so a difference between two devices on the same network points at something specific to one of them.