ERR_CONNECTION_TIMED_OUT: The server took too long to respond
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.
Short answer
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.
What ERR_CONNECTION_TIMED_OUT means
A timeout is distinct from a refusal. A refused connection means something answered and said no; a timeout means nothing answered at all. That difference points at firewalls and overload rather than misconfiguration.
Causes and fixes, most likely first
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.
A firewall or security group is silently dropping traffic on port 80/443. Allow inbound traffic on those ports. Dropped — rather than rejected — packets are exactly what produce a timeout instead of a refusal.
The server is overloaded and cannot accept new connections. Check load, connection limits and worker counts. A saturated connection backlog times out new visitors while existing sessions keep working.
The DNS record points at an IP address that no longer exists. Verify the A record matches the server's current address — this is a routine casualty of server migrations.
ERR_CONNECTION_TIMED_OUT on specific platforms
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…
ERR_CONNECTION_TIMED_OUT on Android — On mobile networks the carrier's transparent proxy times out slow origins earlier than a desktop browser does, so a site that is merely…
ERR_CONNECTION_TIMED_OUT on Cloudflare — When Cloudflare cannot reach the origin it returns error 522 rather than passing the timeout through, so a browser timeout with Cloudflare…
ERR_CONNECTION_TIMED_OUT on WordPress — A PHP worker pool exhausted by a slow plugin or a runaway cron job accepts no new connections, so the site times out while the server…
ERR_CONNECTION_TIMED_OUT on AWS S3 — A security group or network ACL that allows your office IP but not the public internet makes an S3-backed site or its origin time out for…
How to stop it happening again
Monitor from multiple locations so a regional network fault is distinguishable from a real outage.
Alert on response time trending upward, not only on hard failures — timeouts are usually preceded by slow responses.
Watch connection-level failures separately from HTTP status: a timeout never produces a status code at all.
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
How do I fix ERR_CONNECTION_TIMED_OUT?
Confirm from outside your network whether the server responds at all. If it does not, check the web server process, firewall rules on ports 80/443, and server load. If it does respond externally, the problem is your local network or ISP.
What is the difference between timed out and refused?
Refused means the server actively rejected the connection — nothing is listening on that port. Timed out means the packets vanished, which usually points at a firewall dropping them or a host that is not up.
Can a slow site cause a connection timeout?
Yes. When the connection backlog saturates, new connections wait and eventually time out even though the machine is running. Rising response times are the early warning.