Are you getting ERR_CONNECTION_TIMED_OUT in Chrome? Learn why the server took too long to respond and try 12 proven fixes for visitors and site owners.
You click a link and nothing happens. The tab spins. You wait, then wait a bit longer, and then Chrome gives up and shows its grey “This site can’t be reached” page with a line that reads “example.com took too long to respond.” At the bottom, in tiny letters, is the name of the problem: ERR_CONNECTION_TIMED_OUT.
It’s one of the more irritating errors out there, because you get no clear message. The site isn’t saying no, and it isn’t saying anything at all. Your browser asked for a connection and heard silence.
This guide explains what that silence means, why it happens, and how to fix it, whether you’re just trying to open a page or you run the website and need to find out why visitors are stuck waiting.
Quick answer: how to fix ERR_CONNECTION_TIMED_OUT
If you’re a visitor, work through this list:
- Check whether the site is down for everyone
- Test your own internet connection
- Restart your router and modem
- Try another network or device
- Turn off your VPN and proxy
- Check your firewall and antivirus
- Clear DNS and browser caches, then try another DNS server
- Look at the hosts file and reset your network settings
If you manage the site or server, check these:
- Is the server overloaded or out of resources?
- Is a firewall silently dropping traffic?
- Do your DNS records point to the right server?
- Is your host or network having an outage?
What does ERR_CONNECTION_TIMED_OUT mean?
Before a browser can load any web page, it has to open a connection to the server. It does this by sending a small request packet and waiting for a reply. Think of it like calling someone on the phone and letting it ring.
If the server picks up, the page loads. If the server rejects the call, you get a different error. But if nobody answers within the time limit, the browser stops waiting and shows ERR_CONNECTION_TIMED_OUT.
That waiting time varies by browser and operating system, but it’s usually long enough to feel painful. It’s also why this error feels so different from a quick refusal: you wait, and then it fails.
One point worth knowing: this is a connection-level problem, not an HTTP status code. The server never got far enough to say 404 or 503. If you want to compare it with codes that do come from the server, our HTTP errors guide covers the common ones.
Timed out vs refused vs reset
People swap these errors around all the time, but they point to different problems:
| Error | What actually happened | Usual suspects |
|---|---|---|
| ERR_CONNECTION_TIMED_OUT | No reply came back before the time limit | Overloaded server, firewall dropping packets, network or routing problem |
| ERR_CONNECTION_REFUSED | The server or a firewall answered with a clear no | Stopped web server, closed port. See our ERR_CONNECTION_REFUSED guide |
| ERR_CONNECTION_RESET | The connection opened, then was cut | Network interruption, security software, crash mid-request |
| ERR_NAME_NOT_RESOLVED | The domain couldn’t be matched to an IP | DNS failure. See our DNS errors guide |
In short: refused means someone said no, timed out means nobody said anything, and reset means someone hung up.
What the error looks like in each browser
| Browser | Message |
|---|---|
| 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. The server stopped responding.” or “The request timed out.” |
Why does ERR_CONNECTION_TIMED_OUT happen?
Reasons on your side
- An unstable or very slow internet connection
- A VPN or proxy that isn’t passing traffic properly
- A firewall or antivirus that’s quietly blocking the connection
- Bad or outdated DNS cache entries
- Wrong network or proxy settings
- A modified hosts file sending the domain to the wrong address
- Router problems, or a poor Wi-Fi signal
Reasons on the website’s side
- The server is overloaded and can’t accept new connections
- A firewall or cloud security group drops traffic instead of rejecting it
- The server or hosting network is having an outage
- DNS points to an old or wrong IP address
- Rate limiting or DDoS protection is treating real visitors as a threat
- The web server has hit its connection or worker limit
- Routing problems between certain networks and the server
Start here: is it you or the site?
Two quick tests will save you a lot of time:
- Open a few other websites. If nothing loads, your internet connection is the issue, not this one site.
- Open the site on your phone using mobile data with Wi-Fi turned off. If it opens there, the problem is somewhere between your computer and the internet (your device, your router or your ISP).
If you’re a site owner and the site won’t load for anyone, jump to the server fixes (Fix 9 onward).
Fixes for visitors
Fix 1: Check if the site is down for everyone
Use an “is it down for everyone or just me” website. If the site is unreachable from several locations, the server is the problem and the only thing you can do is wait or contact the owner. If it loads fine for others, keep going.
Fix 2: Test your own internet connection
It sounds obvious, but a shaky connection is the number one cause of timeouts. Run a few checks:
- Load a couple of big, reliable sites. If they’re slow or fail too, your connection is the problem.
- Move closer to the router, or plug in with an Ethernet cable to rule out weak Wi-Fi.
- Pause big downloads, streaming or cloud backups that might be hogging bandwidth.
You can also run a basic ping test. On Windows, open Command Prompt and type:
ping 8.8.8.8
If you see lots of lost packets or very high times, the connection itself is unstable, and you’ll want to talk to your internet provider.
Fix 3: Restart your router and modem
It’s the oldest advice in tech, and it still works. Routers build up stale connection data over time.
- Unplug the router and modem from power.
- Wait a full 30 seconds.
- Plug in the modem first, then the router.
- Give it a couple of minutes to fully reconnect before testing again.
Fix 4: Try another network or device
Connect through your phone’s hotspot, or try a different Wi-Fi network.
- Site loads on the other network: your home network or ISP is blocking or slowing the route. Keep going with Fix 5 to Fix 8, and if nothing helps, contact your ISP.
- Site fails everywhere: the server is almost certainly the cause.
Fix 5: Turn off your VPN and proxy
A VPN adds an extra stop between you and the site. If its server is slow, overloaded or blocked by the website, your connection will time out.
- Disconnect the VPN and reload the page.
- On Windows, go to Settings > Network & internet > Proxy and turn off any proxy you didn’t set up yourself.
- On Mac, open System Settings > Network, select your connection, click Details and then Proxies, and untick anything that’s on.
In a work or school network, a proxy may be required. If so, ask your IT team before changing it.
Fix 6: Check your firewall and antivirus
Security software can silently drop connections it doesn’t like, and a drop looks exactly like a timeout.
- Temporarily turn off your antivirus web protection and your third-party firewall, then reload the page.
- On Windows, open Windows Security > Firewall & network protection and make sure your browser isn’t blocked.
- If that fixes it, add an exception for your browser or the website, and turn your protection back on right away.
Fix 7: Clear caches and try a different DNS server
Stale DNS data can send your browser to an address that no longer answers.
Chrome’s DNS cache: go to chrome://net-internals/#dns and click Clear host cache.
Your system DNS cache:
Windows (Command Prompt as administrator):
ipconfig /flushdns
macOS (Terminal):
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Browser cache: in Chrome, open Settings > Privacy and security > Delete browsing data, tick Cached images and files, and clear.
Switch DNS servers. Your ISP’s DNS can be slow or unreliable. Try Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1) in your network adapter settings, then test again.
Fix 8: Check the hosts file and reset network settings
Hosts file. This small file can override DNS on your computer. If someone, or some software, added a line for the domain you’re visiting, it can send you to an address that’s dead. On Windows the file is in C:\Windows\System32\drivers\etc\hosts, and on Mac and Linux it’s /etc/hosts. Remove any line that mentions the problem domain, unless you added it on purpose.
Reset Windows networking. Open Command Prompt as administrator, run these commands, and restart:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
Reset Chrome. If only Chrome fails, open chrome://settings/reset and choose Restore settings to their original defaults. Try a different browser first, since it will tell you right away whether Chrome is the problem.
Fixes for website owners and server admins
If your visitors are the ones seeing a timeout, the work moves to the server. These checks go from the most common cause to the least.
Fix 9: Check whether the server is overloaded
A server that’s out of CPU, memory or connection slots may accept requests slowly or not at all. New visitors then wait until the browser gives up.
Log in over SSH (if you can) and look at the load:
top
free -m
df -h
Things to look for:
- CPU pinned near 100% for long stretches
- Little or no free memory, or heavy swap use
- A full disk, which can stop services from working
- Too many open connections, which you can count with
ss -s
Common fixes include restarting the web stack, adding caching, blocking abusive bots, raising the web server’s connection limits (like worker or worker_connections settings), and moving to a bigger plan. If you’re not sure how much capacity you need, our Server Size Calculator and Bandwidth Calculator give a good starting estimate.
On shared hosting you can’t log in to the server, so check your hosting dashboard for resource limit warnings and open a ticket with support. Our web hosting errors guide lists other problems to look for.
Fix 10: Look for firewalls that silently drop traffic
This one catches a lot of people. A firewall can handle unwanted traffic in two ways:
- Reject it, which sends back a clear “no” and causes a connection refused error
- Drop it, which says nothing and causes a timeout
Cloud firewalls such as AWS security groups and many network firewalls drop blocked traffic by default, so a wrong rule shows up as a timeout instead of a refusal.
Check each layer:
- Cloud security groups and network ACLs: make sure inbound rules allow ports 80 (HTTP) and 443 (HTTPS) from the right sources.
- Server firewall: run
sudo ufw statusorsudo iptables -L -nand look for DROP rules on your web ports. - Hosting panel or security tools: CSF, Imunify360, Fail2ban and similar tools can block IPs or whole regions.
- Geo-blocking and rate limits: make sure legitimate visitors aren’t being caught by country blocks or aggressive limits.
Test from outside your network to see what visitors see:
curl -v --connect-timeout 10 https://yourdomain.com
nc -zv -w 5 your-server-ip 443
If these hang and then time out, something between the outside world and your server is dropping traffic.
Fix 11: Make sure DNS points to the right server
If you recently moved hosts, changed your IP or edited DNS records, your domain might still point to an old server that’s switched off or no longer answers.
nslookup yourdomain.com
Compare the IP in the answer with your current server’s IP. If they don’t match, update your A record (and AAAA record, if you use IPv6) at your DNS provider. Don’t forget the AAAA record: a wrong IPv6 address can cause timeouts for visitors whose devices try IPv6 first. DNS changes can take anywhere from minutes to a day to spread. See our DNS errors guide for more help.
If you use Cloudflare or another proxy service, make sure the origin IP in your settings is correct and reachable. Timeouts between a proxy and your origin often show up as specific codes, which our Cloudflare errors guide explains.
Fix 12: Check for host or network outages, and trace the route
If the server looks healthy and the firewall is fine, the problem may be in the network between your visitors and the server.
- Check your host’s status page and social accounts for outages or maintenance.
- Run a traceroute to see where packets stop: use
tracert yourdomain.comon Windows, ortraceroute yourdomain.comormtr yourdomain.comon Mac and Linux. - Ask visitors where they are. If only certain countries or ISPs have the problem, the cause is probably a routing issue or a regional block, not your server itself.
- Contact your hosting provider with the traceroute results, the time of the problem and the steps you’ve tried.
A clear ticket like “Connections to my server time out from several UK ISPs, here’s the traceroute” gets a faster answer than “my site is down.”
ERR_CONNECTION_TIMED_OUT on Android and iPhone
The fixes are shorter on a phone:
- Switch between Wi-Fi and mobile data to see which one fails.
- Toggle airplane mode on and off for a few seconds.
- Turn off any VPN or content-blocking app.
- Clear the browser’s cache and site data.
- On Android, check Settings > Network & internet > Private DNS and try setting it to Automatic or Off.
- Restart your phone and router.
What about WordPress sites?
If you run WordPress and the site loads slowly before timing out, a few extra WordPress-specific things can help:
- Deactivate heavy plugins, especially security, backup and page builder plugins that run lots of requests.
- Turn on page caching so the server isn’t rebuilding every page for every visitor.
- Check that scheduled tasks or imports aren’t pinning the CPU.
- Make sure your PHP version is supported, and that memory limits aren’t too tight.
These issues often lead to a 504 or a 503 once the connection succeeds. See our guides on 504 Gateway Timeout and 503 Service Unavailable if the symptoms change.
How to prevent connection timeouts on your site
- Use uptime monitoring with alerts, so you know about timeouts before your visitors do.
- Add caching and a CDN to take pressure off your server during traffic spikes.
- Review firewall rules after every change and test from an outside network.
- Keep an eye on resources like CPU, memory, disk and open connections.
- Plan capacity ahead of launches, sales and campaigns.
- Keep DNS records tidy, and lower the TTL before a migration so changes spread quickly.
- Pick dependable hosting with clear status pages and responsive support.
Does ERR_CONNECTION_TIMED_OUT hurt SEO?
It can, if it keeps happening. Search engine crawlers that can’t connect will retry, but frequent or long timeouts can slow down crawling and may push pages out of the index.
Slow connections can also push real visitors away, which hurts engagement. After you fix the problem, check Settings > Crawl stats in Google Search Console to confirm Google can reach your site again.
Frequently asked questions
What does ERR_CONNECTION_TIMED_OUT mean?
It means your browser tried to connect to a website’s server and got no reply before the time limit ran out. The server didn’t refuse the request; it just never answered.
Is ERR_CONNECTION_TIMED_OUT my fault or the website’s?
It could be either one. If the site opens on other devices and networks, the problem is on your side. If it fails for everyone, the website’s server or network is the cause.
What is the difference between ERR_CONNECTION_TIMED_OUT and ERR_CONNECTION_REFUSED?
A timeout means no answer came back at all. A refused connection means the server or a firewall replied with a clear rejection. Refused errors usually point to a stopped service or closed port, while timeouts often point to overload, dropped packets or network trouble.
How long does a connection timeout take to appear?
It depends on your browser and operating system, but it usually takes a while, often 20 seconds or more. That wait is a sign the browser is retrying before it gives up.
Can a VPN cause ERR_CONNECTION_TIMED_OUT?
Yes. A slow, overloaded or blocked VPN server can stop your traffic from reaching the website. Disconnect it and reload the page to test.
Can my firewall or antivirus cause this error?
Yes. Security software can silently drop connections, which looks the same as a timeout. Temporarily turn off its web protection to test, and turn it back on afterward.
Why does ERR_CONNECTION_TIMED_OUT only happen on one website?
Usually the problem is with that site’s server, its firewall, or the route between you and it. Test the site on another network. If it still fails, the site owner needs to fix it.
Will changing DNS servers fix ERR_CONNECTION_TIMED_OUT?
Sometimes. If your ISP’s DNS is slow or returning stale data, switching to Google or Cloudflare DNS can help. It won’t fix a server that’s actually down or blocked.
How do I fix ERR_CONNECTION_TIMED_OUT on my own website?
Check server resources, look for firewall rules that drop traffic, confirm DNS points to the right IP, and test from an outside network. Then check your hosting provider’s status page for outages.
Does ERR_CONNECTION_TIMED_OUT go away on its own?
Often yes, if it’s caused by a temporary overload or a network hiccup. If a firewall rule, wrong DNS record or lasting server issue is the cause, it stays until you fix it.
Final thoughts
ERR_CONNECTION_TIMED_OUT is frustrating because it gives you so little to go on, but the pattern is predictable. For visitors, it’s usually the connection, a VPN, security software or DNS. For site owners, it’s usually an overloaded server, a firewall that drops traffic or a DNS record pointing to the wrong place.
Start by working out whether the problem is local or global, then follow the fixes that match. If you get stuck, trace the route, check your logs and bring your host the details.
Still getting the error after all this? Leave a comment with your browser, the website and what you’ve tried, and we’ll help you track it down.