ERR_CONNECTION_TIMED_OUT: what it means and how to fix it

Kofi Agyem, Founder and CEO, CloudzyroPublished November 1, 2026 · 5 min read

On this page

1. The short answer
2. What you'll see
3. What causes it
4. Fixes for visitors, quickest first
5. Fixes for site owners
6. A worked example
7. How to check
8. Sources

ERR_CONNECTION_TIMED_OUT means the site's server never answered. Why that happens, quick fixes for visitors, and what site owners should check.

1. The short answer

ERR_CONNECTION_TIMED_OUT means your browser tried to connect to the site's server and never heard back. It sent the opening packet of a TCP connection, retried, and got no reply before the time limit. Nothing said no; nothing answered at all.

That silence usually means one of three things: a firewall is dropping the traffic, the server is off or overloaded, or DNS points to an address where nothing is running any more. If other sites load and this one fails on every network, it's the site. If it works on your phone's mobile data, it's your network. It's part of the This site can't be reached family.

2. What you'll see

Chrome: This site can't be reached. example.com took too long to respond. ERR_CONNECTION_TIMED_OUT.
Edge: Hmm... can't reach this page. example.com took too long to respond.
Firefox: The connection has timed out. The server at example.com is taking too long to respond.
Safari: Safari can't open the page because the server where this page is located isn't responding.
curl: Failed to connect to example.com port 443 after 75001 ms: Timeout was reached (the exact time varies).

3. What causes it

A firewall dropping packets. A server firewall, cloud security group or network firewall that silently discards traffic produces a timeout, not a refusal. A missing rule for port 443 is a classic cause.
The server is down or unreachable, powered off, crashed or cut off from its network.
DNS points to the wrong address, such as an old server after a move, or a typo in an A record.
A broken IPv6 address. If a domain has an AAAA record for a server that doesn't answer on IPv6, some clients wait on it before falling back to IPv4.
The server is overloaded and can't accept new connections fast enough.
Your network blocks the site, or blocks the port, as some workplaces and public Wi-Fi do.
Your IP address is blocked by the site's firewall, which drops your traffic.
A VPN or proxy that's slow, down or blocked.

4. Fixes for visitors, quickest first

Reload after a few seconds. A busy server may answer the second time.
Try another network, such as your phone on mobile data. If it works there, the cause is your network.
Turn off your VPN or proxy, and check Windows' proxy settings (Settings, Network and internet, Proxy).
Flush your DNS cache, in case your device remembers an old address for the site.
Check your firewall or antivirus isn't blocking the browser.
Restart your router.
If it fails everywhere, the site is down. Check its status page or try later.

# Windows (Command Prompt or PowerShell)
ipconfig /flushdns

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux with systemd-resolved (Ubuntu, Fedora and most others)
resolvectl flush-caches

# Chrome's own cache: open this address, then click Clear host cache
chrome://net-internals/#dns

5. Fixes for site owners

Check DNS points to the right server. Run dig +short for both the bare domain and www, and compare with your server's address. Remove any stale AAAA record.
Check the server is up and reachable: can you SSH to it, does your host's dashboard show it running?
Check the firewall allows ports 80 and 443 from the internet. On cloud hosts, check the security group or network firewall as well as the server's own.
Check something is listening on 443 (ss -tlnp on Linux). If nothing is, you'd usually get ERR_CONNECTION_REFUSED instead, unless a firewall drops the packets first.
Check load. A server out of memory or CPU, or with a full connection queue, may stop accepting connections in time.
Check for IP blocks in your firewall or security tools if only some visitors are affected.

On Cloudzyro Sites & Apps, the servers and firewalls are ours to run, so a timeout on your domain is almost always DNS. www should be a CNAME to domains.cloudzyro.app, and the bare domain an A record to 173.234.137.167. An A record still pointing at a previous host will time out once that host is switched off. The site's Domains tab shows what it found; see the domain troubleshooting guide.

6. A worked example

A developer moves a site to a new cloud server and updates the domain's A record. Hours later, some visitors still see ERR_CONNECTION_TIMED_OUT.

dig +short A www.example.com shows the new address. dig +short AAAA www.example.com still shows an IPv6 address from the old host, which was switched off.
curl -4 -v https://www.example.com/ loads the page. curl -6 -v https://www.example.com/ hangs, then times out.
Visitors whose networks prefer IPv6 were trying the dead address first. The developer deletes the stale AAAA record.
A second check shows the security group on the new server allows port 443 but not port 80, so plain http:// links also time out. They open port 80 for the redirect to HTTPS.

When you move a site, check every record for the name, A and AAAA, and both ports.

7. How to check

# Which addresses does the name point to? Check both IPv4 and IPv6
dig +short A www.example.com
dig +short AAAA www.example.com

# Can you open port 443? Times out = dropped, refused = nothing listening
nc -vz -w 10 www.example.com 443                        # macOS and Linux
Test-NetConnection www.example.com -Port 443            # Windows PowerShell

# Try the connection with a short timeout and full detail
curl -v --connect-timeout 10 https://www.example.com/

# Where along the path it stops
traceroute www.example.com      # macOS and Linux
tracert www.example.com         # Windows

If curl -4 works and curl -6 times out, your IPv6 setup or AAAA record is the problem. If the port check times out from everywhere, look at the server's firewall and whether it's running. A traceroute that stops partway shows roughly where traffic is dropped, though many routers don't reply to traceroute, so gaps aren't always failures.

8. Sources

Questions

What does ERR_CONNECTION_TIMED_OUT mean?

Your browser tried to open a connection to the site's server and got no reply at all within the time limit. The server is down, unreachable, or a firewall is silently dropping the traffic.

Is ERR_CONNECTION_TIMED_OUT my problem or the website's?

If the site fails on every network, it's the website: its server is down, overloaded, or its DNS points to the wrong address. If it works on mobile data but not your Wi-Fi, your network, VPN or firewall is the cause.

What's the difference between timed out and refused?

Refused means the server answered and said no, so something is there but nothing listens on that port. Timed out means nothing answered at all, which usually means a firewall dropping packets or a server that's off.

Can DNS cause ERR_CONNECTION_TIMED_OUT?

Yes, indirectly. If the domain's record still points to an old server address that no longer answers, the lookup succeeds but the connection times out. Check the address dig returns.

How long does Chrome wait before ERR_CONNECTION_TIMED_OUT?

Chrome leaves connection timing largely to the operating system, which retries for a while before giving up, often somewhere between 20 seconds and a couple of minutes depending on the system.

Does ERR_TIMED_OUT mean the same thing?

Close. ERR_CONNECTION_TIMED_OUT is a timeout while opening the connection. ERR_TIMED_OUT is a more general timeout, for example when a connection opened but the server stopped responding.