Few browser errors are as vague and as universally annoying as ERR_CONNECTION_TIMED_OUT. There's no obvious culprit staring back at you, just a blank page and a message telling you the connection gave up waiting. Sometimes it's your Wi-Fi. Sometimes it's your DNS settings. Sometimes it has nothing to do with you at all and the website itself is struggling. This guide walks through what the error actually means, the most common reasons it shows up, and a full set of fixes for desktop browsers, mobile devices, and for the site owners who might be causing it on their end without realizing it.
This error means your browser sent a request to a server and never got a response back within the expected time frame, so it gave up. It's different from a "site not found" type error, where the domain simply doesn't resolve. Here, the browser knows where it's trying to go, it just never hears anything back after reaching out.
Think of it like calling a phone number that rings and rings with nobody picking up, as opposed to a number that's been disconnected entirely. The connection attempt itself is the problem, not the address you're trying to reach.
This can happen at several different points along the path between your device and the server: your local network, your ISP, your DNS resolver, a firewall somewhere in between, or the destination server itself. That's part of what makes this particular error frustrating to diagnose. The symptom looks identical no matter where the actual breakdown occurred.
A number of things can lead to this timeout, and they fall into a few general categories:
These steps are ordered roughly from the most common fixes to the more advanced ones. Working through them in order usually resolves the issue well before you reach the end of the list.
Start with the basics. Try loading a couple of other websites to see if the problem is isolated or widespread. If nothing loads, restart your router and modem by unplugging them for about thirty seconds. This clears temporary glitches and refreshes your connection to your ISP, and it resolves a surprising number of timeout errors on its own.
A bloated or corrupted cache can interfere with how your browser establishes new connections. Clearing it forces a fresh request to the server instead of relying on stored data that might be stale or damaged. In most browsers this is found under Settings, then Privacy, then Clear Browsing Data.
Your computer stores DNS lookups locally to speed things up, but an outdated entry can point your browser toward a server that's no longer responding correctly. On Windows, open Command Prompt and run:
ipconfig /flushdns
This clears the stored records and forces a fresh lookup on your next visit.
If your ISP's default DNS server is slow or occasionally unresponsive, switching to a cloud based DNS provider like Google Public DNS (8.8.8.8) or Cloudflare (1.1.1.1) often resolves timeout issues almost immediately. These services tend to be faster and more consistently available than many default ISP resolvers, and the switch takes only a couple of minutes in your network adapter settings.
If you're running a VPN or a manually configured proxy, try disabling it temporarily and reloading the page. Proxies and VPNs route your traffic through an additional server, and if that server is slow, overloaded, or misconfigured, it can cause exactly this kind of timeout.
Security software occasionally blocks legitimate connections, particularly after a rule update. Disable your firewall and antivirus briefly to see if the page loads. If it does, you've found your cause, and you can add a specific exception for the site rather than leaving your protection off long term.
This resets your network configuration to a clean state and can clear up deeper connectivity issues that a simple router restart doesn't touch.
Your device's hosts file can override normal DNS resolution, and an old or incorrect entry (sometimes left behind by software you installed previously) can quietly block a site. On Windows, the file is located at C:\Windows\System32\drivers\etc\hosts. On macOS and Linux, it's at /etc/hosts. Open it with a text editor and check for any line referencing the site you're trying to reach.
Outdated network drivers can cause inconsistent connectivity that looks like a random timeout. Check Device Manager on Windows or your system updates on macOS to make sure your network adapter driver is current, and reinstall it if it hasn't been updated in a while.
Extensions that modify network requests, like ad blockers, privacy tools, or proxy managers, can occasionally interfere with normal page loading. Disable your extensions one at a time, or all at once in an incognito window, to check whether one of them is responsible.
Chrome shows this error on its own dedicated page with a "Retry" button, but a few Chrome specific checks are worth doing beyond the general steps above:
chrome://net-internals/#dns and click "Clear host cache" to flush Chrome's internal DNS cache separately from your system's cache.chrome://extensions and disable anything recently installed, since a new extension is a common source of sudden timeout issues.chrome://net-export/ if the problem persists, which can help pinpoint exactly where the connection is failing.Edge shares its underlying engine with Chrome, so most fixes carry over, along with a couple of Edge specific settings:
edge://extensions to rule out a conflict.Firefox handles some of these settings a little differently:
about:preferences#privacy in the address bar and clear cookies and cache under the Cookies and Site Data section.about:preferences#general, scroll to Network Settings, and confirm your proxy configuration is set to "No proxy" or "Use system proxy settings" unless you specifically need something else.Mobile devices run into the same underlying issue, but the fixes look a little different since you're usually working with fewer settings menus.
Before spending too much time troubleshooting your own setup, it's worth confirming where the problem actually lies. A few quick checks:
If every other site loads normally and only one specific website consistently times out across multiple devices and networks, the problem is very likely sitting on that website's end.
Sometimes the timeout has nothing to do with you at all. A website can time out for visitors when its own server is overwhelmed, misconfigured, or experiencing an outage. This is common during traffic spikes, when a server simply can't keep up with the volume of incoming requests, or when a backend issue causes requests to hang instead of completing normally.
Poor website availability during high traffic periods, an origin server located far from a visitor's actual location, or a lack of any real protection against malicious traffic can all contribute to intermittent or widespread timeouts that no amount of troubleshooting on the visitor's side will fix. In these cases the responsibility shifts to whoever manages the site's infrastructure.
If you run a website and users are reporting timeout errors, the fix usually lives in your infrastructure rather than in any individual visitor's settings. A few things worth reviewing:
ERR_CONNECTION_TIMED_OUT is one of those errors that can come from almost anywhere along the path between your browser and the server you're trying to reach. Most of the time, a router restart, a DNS flush, or clearing out a stubborn browser cache is enough to get things working again. When the problem follows you across every device and network you try, the cause is usually sitting on the website's side, whether that's an overloaded server, a routing issue, or a lack of infrastructure built to handle traffic reliably. Working through the steps in order, and knowing how to tell the difference between a local issue and a server side one, takes most of the guesswork out of an error that otherwise feels completely random.
1. Does ERR_CONNECTION_TIMED_OUT mean the website is down for everyone or just me?
Not necessarily. It can mean either. The best way to tell is to check the site on a different device and network, or use a third party tool that checks site status from multiple locations, to see whether the issue is isolated to you or affecting other visitors too.
2. Why does ERR_CONNECTION_TIMED_OUT appear on only one website?
If every other site loads normally, the cause is usually specific to that site, such as a server outage, an overloaded backend, or a routing problem between your ISP and that site's infrastructure. It generally isn't something wrong with your device when the issue is limited to a single destination.
3. Can a VPN or proxy trigger ERR_CONNECTION_TIMED_OUT?
Yes. A VPN or proxy adds an extra hop that your traffic has to pass through, and if that server is slow, overloaded, or misconfigured, your connection can time out even though the destination website itself is working fine. Disabling it temporarily is a quick way to test whether it's the cause.
4. Is ERR_CONNECTION_TIMED_OUT a sign of a virus or malware?
It can be, though it's far more often caused by something mundane like a network hiccup or a DNS issue. Malware that alters your hosts file or intercepts network traffic is a possibility worth ruling out if the error persists despite trying every other fix, but it's not the most likely explanation.
5. Why do I see ERR_CONNECTION_TIMED_OUT on Wi-Fi but not on mobile data?
This points to something specific to your Wi-Fi network rather than the website itself. It could be your router, your ISP's DNS resolver, a firewall setting on your network, or even a temporary outage affecting your home internet provider specifically, none of which would affect a separate mobile data connection.