Chrome, Edge

ERR_CONNECTION_TIMED_OUT

The browser sent packets and nothing came back within the time limit. Unlike a refused connection, this is silence rather than rejection.

What causes it

A firewall dropping traffic instead of rejecting it.
The server is up but too overloaded to accept new connections.
A routing problem between you and the server.
The server has been shut down or its IP has changed.

If you are the visitor

Test on a different network — mobile data is the quickest check.
Turn off VPNs and proxies.
Restart your router, which clears both its DNS cache and its NAT table.

If it is your website

Check server load and connection limits.
Check the firewall is not silently dropping traffic from certain ranges.
Confirm the DNS record still points at the right IP.

Find out whether the site is down for everyone

A live check from our server shares nothing with your network — it settles the question in seconds.

Run a live check

Other connection errors

ERR_CONNECTION_REFUSED DNS_PROBE_FINISHED_NXDOMAIN ERR_NAME_NOT_RESOLVED ERR_SSL_PROTOCOL_ERROR NET::ERR_CERT_AUTHORITY_INVALID NET::ERR_CERT_DATE_INVALID NET::ERR_CERT_COMMON_NAME_INVALID ERR_TOO_MANY_REDIRECTS ERR_EMPTY_RESPONSE ERR_CONNECTION_RESET 503 Service Unavailable 502 Bad Gateway This site can't be reached