ERR_TIMED_OUT: What It Means and How to Fix It

What ERR_TIMED_OUT actually means

A connection was attempted to the resolved IP address, but no response arrived within Chrome's timeout window (typically 30 seconds). The server may be overloaded, the route between you and the server may have excessive packet loss, or an intermediate firewall may be silently dropping the connection.

Most likely causes (ranked)

1. The website's server is overloaded and not responding in time
2. A firewall or ISP is silently dropping packets to the destination
3. Poor routing between your ISP and the target server
4. Your own router is overloaded or has NAT table exhaustion
5. A proxy or VPN is introducing too much latency

How to fix ERR_TIMED_OUT

Step 1: Check if the site is down

Test the URL on your phone using cellular data (not Wi-Fi). If it loads on cellular but not on your home connection, the problem is your network or ISP.

Step 2: Run a traceroute

On Windows: 'tracert '; on macOS: 'traceroute '. Identify where packets stop responding — a timeout at an early hop (3–5) means an ISP routing issue; a timeout at the final hop is the server.

Step 3: Disable firewall temporarily

Turn off Windows Defender Firewall or your security software briefly and retry. A packet-dropping outbound rule causes this error identically to a server timeout.

Step 4: Restart your router

NAT table exhaustion on overloaded routers silently drops new outbound connections. A restart clears the table and restores normal operation.

Step 5: Try with a different DNS and wait

Sometimes the error is transient server overload. Switch DNS to 1.1.1.1, wait 5–10 minutes, and retry — server spikes that cause timeouts often clear quickly.

Still not fixed? Rule out your connection

If the steps above did not clear the error, the next step is verifying the underlying internet connection is healthy. Run a speed test — if download, upload, and ping come back normal, the error is specific to one site or browser state. If the speed test also fails or shows packet loss, the problem is at the network or ISP layer.

Frequently Asked Questions

What is the difference between ERR_TIMED_OUT and ERR_CONNECTION_TIMED_OUT?

They are nearly identical — both indicate a timeout. ERR_CONNECTION_TIMED_OUT specifically means the TCP connection attempt timed out (the server never accepted the connection). ERR_TIMED_OUT can occur later in the connection lifecycle, including while waiting for a response after the connection was established.

Why does ERR_TIMED_OUT happen on some sites but not others?

Because the problem is with the specific server or the routing path to it. Your connection to other destinations is fine. If only one site consistently times out, the server or its CDN has an issue — try again later or contact the site operator.