Opens in a new tab

ERR_CONNECTION_TIMED_OUT: “took too long to respond”

The connection request went out and nothing came back — not a yes, not a no. Something is silently dropping the packets: a firewall that blocks your address, a server that is down or overloaded, or a domain pointing at an address where nothing lives. If the site loads for others but not for you, your address is the likely target.

This site can’t be reached
example.com took too long to respond.
ERR_CONNECTION_TIMED_OUT
How 9 other clients word the same error

Chrome, its own four-minute limit

ERR_TIMED_OUT

Firefox

The connection has timed out
The server at example.com is taking too long to respond.

curl, while connecting

curl: (28) Connection timed out after 10001 milliseconds

curl, connected but no answer

curl: (28) Operation timed out after 30001 milliseconds with 0 bytes received

WordPress and PHP

cURL error 28: Connection timed out after 5001 milliseconds

Node.js

Error: connect ETIMEDOUT 93.184.215.14:443

Python requests

ConnectTimeoutError: Connection to example.com timed out. (connect timeout=10)

Python on Windows

[WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

Java, Go

java.net.SocketTimeoutException: Connect timed out · dial tcp 93.184.215.14:443: i/o timeout
ErrorERR_CONNECTION_TIMED_OUT
Usually fixed byEither side
On the networkNo answer at all to the connection request
Chrome’s codeERR_CONNECTION_TIMED_OUT (-118); ERR_TIMED_OUT (-7) after its own four minutes
curlExit code 28

Check the site from outside

Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.

What it means

A refused connection gets an answer; a timed-out one gets silence. The browser keeps resending its connection request until it, or the operating system, gives up — Linux after about two minutes. Silence is what a firewall produces when it drops packets instead of rejecting them, which is why a blocked visitor usually sees a timeout.

WordPress shows the same thing as cURL error 28 when it calls another site — or itself, in Site Health’s loopback test — and gets no answer within its default five seconds.

Why it happens

  • The server’s firewall is blocking the visitor’s address — CSF, fail2ban and similar tools block by dropping, after too many failed logins or requests.
  • The server is down, or so overloaded it cannot accept connections.
  • The domain points to an old or wrong IP address where nothing answers.
  • A port filtered by a cloud security group, the host or the visitor’s network.

How to fix it

  1. Check the site from outside with the check above. If it answers there, your address is probably blocked: ask the host to look it up in the firewall (CSF: csf -g followed by the IP).
  2. If it times out from everywhere, check the server is up and that the domain’s A record holds its current address.
  3. Make sure the firewall and any cloud security group allow ports 80 and 443 from everyone.
  4. For WordPress’s cURL error 28, find which address it was calling: its own (a loopback blocked by the firewall or a security plugin) or an outside service that is slow.

If you are visiting the site

  • Try another network — mobile data instead of Wi-Fi. If the site opens there, your usual address is blocked or your network filters the site.
  • Turn off a VPN or proxy and try again.

See it for yourself

curl -v --connect-timeout 10 https://example.com/
traceroute example.com

curl shows the address it waited on; traceroute shows where on the way the packets stop being answered.

Questions

The site works for everyone except me. Why?

Most likely the server’s firewall has blocked your IP address — often after several failed logins, or because of other traffic from your address. Firewalls like CSF and fail2ban drop blocked traffic, which looks exactly like a timeout. The host can find and remove the block.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

Know when your site goes down — before your visitors do

Add your site and we check it every few minutes, confirm a failure from another location — Europe, North America or Asia — before calling it down, and email you when it stops answering and when it is back. Free for two sites.

Create a free account