Home › Blog › Guide

ERR_CONNECTION_TIMED_OUT: Why It Happens and How to Fix It

By the IsItDown team · Updated 2026-10-19

Your browser knocked and nobody answered — here's how to tell whose fault it is and fix it fast.

You click a link, the browser spins for a while, and then: ERR_CONNECTION_TIMED_OUT. No helpful explanation, no error code you can look up on the page — just a dinosaur or a sad tab and the vague feeling that the internet has stopped working. This is one of the most common errors in Chrome, Edge, and every other browser, and the good news is that it tells you something very specific: your browser tried to reach a website, knocked on the door for a while, and nobody answered.

In this guide we will explain what the error actually means, how to tell whether the problem is the site or your connection, and walk through the fixes in the order that solves it for most people.

What ERR_CONNECTION_TIMED_OUT actually means

When you visit a website, your browser sends a connection request to the site's server and waits for a reply. That wait is not infinite: browsers give up after a set time (usually around 30 seconds in Chrome) and show this error. It is different from the other common errors you might see:

• DNS_PROBE_FINISHED_NXDOMAIN means the site's address could not be looked up at all — the domain does not exist or DNS is broken. (We covered that one in detail in a separate guide.)
• ERR_CONNECTION_REFUSED means the server was reached but actively rejected the connection.
• ERR_CONNECTION_TIMED_OUT means the request went out into the network and the reply simply never came back in time.

Think of it like calling a phone number that rings and rings until it goes to dead air. The number exists, the network works — but whoever is supposed to pick up never does. The cause can sit on the website's side, your side, or somewhere in the middle.

The site's server is overloaded, slow, or down

Most of the time, this error is the website's problem, not yours. A few common server-side causes:

• Traffic overload. A sale, a product launch, a viral post, or a ticket drop sends more visitors than the servers can handle. Your request joins a long queue, and the browser gives up before the server gets to it. Refreshing a few minutes later often works.
• A crashed or hanging service. The web server, the database behind it, or a misbehaving script can freeze up. The server machine is online, but nothing is responding to requests — from the outside it looks identical to an overload.
• A botched deployment or configuration change. A bad code release or firewall rule can silently block real visitors while the server appears healthy.
• A DDoS attack or upstream outage. Floods of junk traffic, or an outage at the site's hosting provider or CDN, can make a site unreachable for everyone.

The fastest way to check: try the site on a different network (for example, switch your phone from Wi-Fi to mobile data). If it fails everywhere, it is the site. You can also run it through our free status checker — it tests from an independent connection, so a failure there means the problem is not your device. When the site is the problem, there is nothing to fix on your end: wait it out, check the site's social media or status page, and try again later.

Your own connection is the problem

If every website times out — or one specific site times out for you but loads fine for others — the cause is on your side of the keyboard. Work through these:

• Your internet connection dropped or is unstable. This is the most common personal cause. A router that lost its connection, Wi-Fi signal that keeps cutting out, or packet loss on a weak link will all produce timeouts. Check whether other sites load, restart your router (unplug it for 30 seconds), and try moving closer to it or switching to a wired connection.
• VPN or proxy trouble. If you run a VPN, all your traffic goes through its servers first. A slow, overloaded, or misconfigured VPN server turns every site into a timeout. Disconnect the VPN and reload the page — if it works, the VPN was the bottleneck. The same applies to proxy settings left behind by old software.
• Firewall or antivirus blocking the site. Security software occasionally decides a perfectly safe site is suspicious and silently drops the connection, which looks exactly like a timeout. Temporarily disable your firewall or antivirus (just for a minute, for one test) and reload. If the page loads, add the site to the allowlist rather than leaving protection off.
• Too many extensions or an overworked browser. Rare, but a misbehaving extension — especially ad blockers, script blockers, or security add-ons — can stall page loads. Try the page in an incognito/private window with extensions disabled.

Something in the middle is blocking the road

Sometimes your connection works and the site works, but the path between them is broken:

• DNS problems. If your DNS resolver is slow or failing, the browser can spend most of its time budget just looking up the site's address and then time out. Switching to a fast public DNS (like Cloudflare's 1.1.1.1 or Google's 8.8.8.8) often fixes stubborn timeouts in seconds.
• ISP or regional network issues. Your internet provider, or a network between you and the site, may be dropping traffic to certain destinations. A quick test: does the site load over mobile data? If yes on mobile data but no on home Wi-Fi, the problem lives in your home network or ISP's routing — a router restart and a call to your ISP are the right moves.
• Network-level blocking. School, office, and public networks often block categories of sites. A timeout rather than a "blocked" message is common when the block is done by silently dropping traffic. Try the site on a network you control.
• The hosts file or old DNS cache. A stale entry in your computer's hosts file or a poisoned DNS cache can send your browser to an address that never answers. Flushing your DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS) clears this.

Fix it step by step: the order that works

Do these in order — stop as soon as the page loads:

1. Wait and retry. Server-side hiccups are the most common cause. Wait a minute or two and reload (Ctrl/Cmd + R). If the site just had a traffic spike, this alone fixes it.
2. Check whether it is the site. Test the site with our status checker or from another network (phone on mobile data). If it fails everywhere, stop troubleshooting your setup — the site is down and waiting is the only fix.
3. Restart your router. Unplug it for 30 seconds, plug it back in, and wait for the lights to settle. This clears most transient connection problems.
4. Disconnect your VPN or proxy. Turn it off and reload. If the page loads, switch VPN servers or contact your VPN provider.
5. Try incognito/private mode. This rules out extensions, cached data, and cookies in one shot.
6. Flush your DNS cache and try a public DNS. On Windows: ipconfig /flushdns, then set your DNS to 1.1.1.1. On macOS: sudo dscacheutil -flushcache, then set DNS in System Settings.
7. Check firewall/antivirus. Temporarily disable it for one test load; allowlist the site if that was the cause.
8. Contact your ISP. If one network fails and another works, or many sites time out at once, your provider may have a routing problem or an outage in your area.

The pattern

ERR_CONNECTION_TIMED_OUT almost never means your computer is broken. It means a request went out and no answer came back — and nine times out of ten the answer is either "the site is having a moment" or "your connection hiccupped." Rule out the site first with an independent check, then work through your own network from the router outward. Most of the time you will have the page loading again within five minutes, without touching a single setting you cannot undo.

Frequently asked questions

What does ERR_CONNECTION_TIMED_OUT mean?

It means your browser sent a request to a website's server and got no reply within its time limit (about 30 seconds in Chrome). The site may be overloaded, your connection may have dropped, or something in between may be blocking the request.

Is ERR_CONNECTION_TIMED_OUT the website's fault or mine?

Often the website's: traffic spikes, crashed services, and hosting outages are the most common causes. Check with an independent status checker or try the site on mobile data — if it fails everywhere, the site is down and there is nothing to fix on your end.

How do I fix ERR_CONNECTION_TIMED_OUT quickly?

Reload after a minute, verify the site is actually up, restart your router, disconnect your VPN, try an incognito window, and flush your DNS cache. That sequence resolves the problem for most people within five minutes.

Can a VPN cause ERR_CONNECTION_TIMED_OUT?

Yes — if your VPN server is slow, overloaded, or misconfigured, every site can time out. Disconnect the VPN and reload the page: if it loads, the VPN was the bottleneck, and switching servers usually fixes it.

Why does only one website time out for me?

That usually points to a DNS or routing issue on your side, or the site blocking your network range. Try a public DNS like 1.1.1.1, flush your DNS cache, and test on a different network to narrow it down.

Keep reading