ERR_CONNECTION_TIMED_OUT and ERR_CONNECTION_RESET Errors
The browser spins, then shows "This site can't be reached" with ERR_CONNECTION_TIMED_OUT or ERR_CONNECTION_RESET — your domain found an address, but nothing at that address finished the conversation.
Common signs of this issue
- The browser shows "This site can't be reached" with "took too long to respond" and the code ERR_CONNECTION_TIMED_OUT, or "The connection was reset" with ERR_CONNECTION_RESET.
- A timeout hangs first — often 20 to 60 seconds of spinning — before the error appears. A reset usually fails quickly or partway through loading.
- Other websites load normally on the same device and connection.
- It may affect only you, only your office, or only people on one internet provider, while customers elsewhere say the site is fine.
- It often starts right after several failed login attempts, a hosting move, a DNS edit, or installing a new VPN or antivirus product.
- Firefox and Safari show their own wording, such as "The connection has timed out" or "Safari can't open the page because the server isn't responding".
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Split the problem in half first: open the site on your phone using mobile data with wifi turned off, and run your domain through a free "is it down for everyone or just me" checker. Down everywhere points at the server or DNS. Down only for you points at your network or a block against your address.
- Note which error you get and how fast. TIMED_OUT means nothing answered at all within the browser's patience. RESET means a connection started and something cut it off. If you instead see ERR_CONNECTION_REFUSED, read the connection refused guide — that one means the server answered and said no.
- Think back over the last hour: did anyone in your office mistype the WordPress, cPanel, email, or FTP password several times? Many hosts run firewalls that silently drop all traffic from an address after repeated failures. The symptom is exactly this: the site times out for the whole office while it loads fine on a phone on mobile data.
- If a ban looks likely, find your public IP address by searching "what is my IP" on the affected network, then send that number to your host's support and ask them to check their firewall block list. On many cPanel hosts you can also look for an unblock tool in the dashboard. Unblocking usually takes minutes.
- Check that your domain points where you think it does. Search for a free DNS lookup tool, enter your domain, and compare the A record to the server IP shown in your hosting dashboard. A mismatch after a move, a leftover record from an old host, or a typo in a recent edit sends visitors to a machine that never answers.
- Look at your host's status page and your email, including spam, for maintenance notices, outage announcements, or a suspension warning. A server that is down, overloaded, or being moved usually produces timeouts for everyone.
- If only one computer is affected, try it with the VPN or proxy turned off, the antivirus "web protection" paused for a minute, and a private browsing window. Security software that inspects traffic is one of the most common causes of ERR_CONNECTION_RESET on a single machine.
- On the affected network, restart the router and try again. For stubborn cases on one computer, flushing the local DNS cache (on Windows, run
ipconfig /flushdnsin a Command Prompt) is harmless and occasionally clears a stale address. - If you use Cloudflare, check whether you get a Cloudflare-branded error page instead. That means Cloudflare is reachable and your origin server is the slow part — see Cloudflare errors 520, 521, and 522.
What this usually means
Opening a website is a short conversation. The browser looks up your domain to get an address, knocks on that address, and waits for the server to answer and then send the page. ERR_CONNECTION_TIMED_OUT means the knock went unanswered — no reply at all within the time limit. ERR_CONNECTION_RESET means a reply started but the line was cut before the page arrived. Neither error means your website's files are damaged; they are about the path between the visitor and the server.
When everyone gets a timeout, the usual causes are a server that is down or completely overloaded, a hosting account that has been suspended, a server firewall change that blocks web traffic, or DNS pointing at the wrong address — very often an old server after a move, or a mistyped A record. That is different from a 504 Gateway Timeout, where your server did answer but one of its back-end parts was too slow. With ERR_CONNECTION_TIMED_OUT, the browser never got a web server response at all. For the broader picture of an outage, see website is down.
When only some people get it, the most common cause by far is the host's security firewall blocking one internet address — typically after repeated failed logins, too many rapid requests, or a flagged email client using an old password. Because an office shares one public address, one person's mistakes can lock out the whole building, and the site looks down to them while it is fine for every customer. The other usual suspects are local: a VPN, antivirus or firewall software, a corporate network filter, or a router having a bad day. Website down for some users covers that patchy pattern in more depth.
What not to do
- Don't keep retrying a login that failed. If the server bans addresses after repeated failures, every extra attempt can extend the block or lock out everyone who shares your office connection.
- Don't change nameservers or DNS records in a hurry. If DNS was not the cause, you have added a second problem that can take hours to settle.
- Don't restore a backup or reinstall the site. A timeout or reset is about reaching the server, and the site's files are almost always untouched.
- Don't permanently disable antivirus or a firewall because pausing it made the site load. Add an exception for your own domain instead.
- Don't assume one complaint means the site is down for the world. Test from a second network before you escalate or pay for anything.
- Don't buy new hosting in the middle of the outage. Moving a site you cannot currently reach is slow and risky, and the fix is often a quick unblock.
When to get help
If the site times out for everyone, your host's status page is quiet, and the DNS lookup matches the server, the problem is on the server itself — a stopped web service, a firewall rule, or an overloaded account — and only your host or someone with server access can see the logs that name it. It is also worth bringing in help if the timeouts started after a hosting move or DNS change and you are not sure which records are correct, or if your office keeps getting banned and nobody knows why: the cause is usually a phone or laptop still trying an old email password in the background, and finding it takes a little detective work. Every hour of a site that looks dead is lost enquiries, so guesswork on DNS is a poor trade.
Glenn, who runs WebsiteSelfHelp, tracks down sites that time out or reset for customers — firewall bans, half-finished moves, wrong DNS records, and overloaded servers. Tell him what you are seeing, who can and cannot reach the site, and roughly when it started, and you will get a clear answer on where the block is and what it will take to clear it. No passwords are needed to start.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
What does ERR_CONNECTION_TIMED_OUT mean?
Your browser tried to connect to the server your domain points to and got no answer within its time limit. The server may be down or overloaded, a firewall may be silently dropping your traffic, or DNS may be pointing at the wrong machine.
What is the difference between ERR_CONNECTION_TIMED_OUT and ERR_CONNECTION_RESET?
A timeout means nothing answered at all. A reset means a connection started but was cut off partway, usually by a firewall, security software, a VPN, or an unstable server. Both are connection problems rather than problems with your website's files.
Why does my website time out only on my office network?
Most often the host's firewall has blocked your office's internet address, usually after repeated failed logins to WordPress, cPanel, email, or FTP. Load the site on a phone using mobile data to confirm, then ask your host to unblock your public IP address.
Is ERR_CONNECTION_TIMED_OUT my fault or my host's?
If the site is down for everyone, it is on the server or DNS side, which is your host's or registrar's territory. If it is only you or your office, the cause is usually local software or a firewall ban against your address.
How long does an IP block from a hosting firewall last?
It depends on the host and the rule. Some blocks expire after minutes or hours, others stay until someone removes them. Asking support to unblock your address is usually faster than waiting.
Will connection timeouts hurt my Google rankings?
A short outage will not. If Google's crawler keeps timing out for days, it slows crawling and pages can eventually drop out of results, so a lasting timeout for everyone is worth fixing quickly.
Can I fix ERR_CONNECTION_TIMED_OUT myself?
Often, yes. Local causes like a VPN, antivirus, or router can be fixed at your end, and a firewall ban takes one support message. Server outages and wrong DNS after a move usually need your host or someone experienced.