Guide

ERR_CONNECTION_TIMED_OUT: meaning and fixes

With ERR_CONNECTION_TIMED_OUT, the browser waits for a connection or response without receiving a usable result before the timeout expires.

Reviewed: 5 October 2026

What is a timeout?

A timeout is not an HTTP status like 404 or 502. The browser did not receive a normal HTTP response in time. Possible causes include an unreachable server, traffic filtering, an incorrect network route, your ISP, a VPN or local firewall.

The first three checks

  1. Open several unrelated websites.
  2. If only one domain fails, use an external website check.
  3. Compare Wi-Fi with mobile data. The difference can quickly reveal a problem limited to one network.

Timeout versus connection refused

With ERR_CONNECTION_REFUSED, the destination actively refuses the connection. With a timeout, a response never arrives in time, so check firewall, routing, VPN, ISP and server reachability.

If the issue affects only your network

Reconnect the device, check your VPN or proxy and compare without it. If Wi-Fi is unreliable, read the slow Wi-Fi guide.

If you own the website

Check that the origin listens on the correct port, the firewall permits traffic and the reverse proxy can reach the origin. Compare the first failure with the latest deployment or DNS or firewall change.

Why isn't ping definitive proof?

ICMP ping and HTTPS are different protocols. A server may block ping yet provide HTTPS normally, or vice versa. Ping is a diagnostic signal, not a final verdict.

Frequently asked questions

Does a timeout mean the website is down for everyone?

No. It may be unreachable only from your network or along a specific route.

Is ERR_CONNECTION_TIMED_OUT the same as 504?

No. A 504 is an HTTP response from a gateway; a browser timeout may happen before any HTTP response.

Sources

Back to top ↑

Related

Continue troubleshooting