ERR_CONNECTION_TIMED_OUT

The short version: ERR_CONNECTION_TIMED_OUT means your browser reached out to a website but heard nothing back within about 30 seconds, so it quit. The trouble is usually local: a flaky network, a stale DNS cache, or a firewall, VPN, or proxy standing in the way. Start by restarting your router, flushing your DNS, and turning off any VPN or proxy.

Key takeaways

• ERR_CONNECTION_TIMED_OUT is silence, not rejection: Chrome opened a connection, waited about 30 seconds, and gave up because no reply ever came back.
• Contrast it with ERR_CONNECTION_REFUSED. Refused fires back an instant TCP reset, a flat no. Timed out leaves you waiting the whole window for an answer that never shows up.
• A firewall that DROPs packets gives you a timeout. One that REJECTs them gives you a refusal. Same blocked port, two different errors, decided entirely by the rule.
• One browser cannot separate a local fault from a genuine outage, because both look identical: nothing answering. Test from a second device or network before you touch a thing.
• Most fixes start on your side: flush DNS, clear Chrome's host cache at chrome://net-internals/#dns, drop any VPN or proxy, then restart the router.

Error type

Browser connection error

Whose side

Usually your side; sometimes the website

Fix difficulty

Easy

Common cause

Stale DNS cache or network issue

What does ERR_CONNECTION_TIMED_OUT mean?

Open a page and your browser opens a network connection to the server, then waits for a reply. When none arrives within roughly 30 seconds, Chrome stops waiting and throws ERR_CONNECTION_TIMED_OUT. This is a timeout, not a refusal: nothing pushed the request away, the answer just never came back in time.

Because the timeout happens silently somewhere along the path, the error itself names no culprit. The cause might be your local connection, your DNS, a VPN or firewall in the way, or a server that is overloaded, down, or quietly dropping the connection. Fastest way to narrow it down: check whether other websites load normally and whether this one is down for other people too.

~30s

Chrome connection timeout

1.1.1.1

Cloudflare public DNS

8.8.8.8

Google public DNS

How the ERR_CONNECTION_TIMED_OUT error appears

The wording changes depending on your browser, device, or server. Here is how this error commonly shows up:

example.com

This site can't be reached

example.com took too long to respond.

ERR_CONNECTION_TIMED_OUT

• Chrome / Edge: ERR_CONNECTION_TIMED_OUT (or ERR_TIMED_OUT)
• Edge: Hmmm… can't reach this page. [website] took too long to respond
• Firefox: The connection has timed out
• Safari: Safari can't open the page because the server isn't responding
• Generic: This site can't be reached / took too long to respond

ERR_CONNECTION_TIMED_OUT vs similar Chrome errors

Chrome shows different connection errors depending on exactly where the request failed, and each points to a different fix.

DROP vs REJECT: why the same block can time out or refuse

A blocked port does not always produce the same Chrome error; it depends on what the firewall is told to do with the packet.

Where the timeout happens, and who can fix it

Matching the symptom to the layer that failed points you straight at the responsible side.

What causes ERR_CONNECTION_TIMED_OUT?

• A shaky or dropped local internet connection, weak Wi-Fi, or a router overdue for a restart.
• DNS records cached on your machine that have gone stale or corrupt, so the browser keeps dialing an address that no longer answers.
• A VPN or proxy server that is slow, misconfigured, or pushing traffic down a path that simply cannot reach the website.
• A firewall or antivirus product silently blocking the outbound connection to that host or port.
• A leftover or wrong entry in your hosts file pointing the domain at a dead or incorrect IP address.
• The website's server is down, overloaded, or too sluggish to finish the connection inside the timeout window.
• A server-side firewall or security rule dropping packets, a closed port (443 for HTTPS, say), or DNS records aimed at the wrong server.

How to find the cause fast

1. Open the site in incognito, and on a second device or mobile data. Loads there? Then the problem is your browser or local network.
2. Pull up a few other websites. If they all time out, blame your connection or router. If only this one fails, blame the site or its DNS.
3. Switch off any VPN, proxy, firewall, and antivirus, then reload, to clear security software from the list of suspects.
4. Run nslookup yourdomain.com to confirm the domain resolves and points at the right server.

Terminal

curl -I --connect-timeout 15 https://example.comcurl: (28) Failed to connect to example.com port 443 after 15001 ms: Connection timed out# packets leave but never get a reply (often a firewall)

How ERR_CONNECTION_TIMED_OUT looks from the outside

One machine cannot tell a local timeout from a real outage; several can. When a site times out from one region but loads fine from the rest, the fault is on the network path, not the server, and that is the one verdict your own browser can never deliver. It is exactly why "it works for me" and "the website is down" are so often both true at once, and why a timeout deserves a check from more than one vantage point before you start changing things.

How to fix ERR_CONNECTION_TIMED_OUT

If you are a visitor

1. See whether other websites load. If they all time out, the problem is your connection, not the website.
2. Confirm the website is not down for everyone using Is Website Down? before you spend more time poking at your own setup.
3. Reload, then restart your router or modem: power it off, wait about 30 seconds, and power it back on.
4. Jump to a different network, for instance a mobile hotspot instead of Wi-Fi, to clear your local connection of suspicion.
5. Turn off any VPN or proxy and disable proxy settings in your system, then reload the page.
6. Disable your firewall or antivirus just long enough to test, and re-enable it the moment you are done.
7. Flush your DNS cache. On Windows, run ipconfig /flushdns in Command Prompt. On macOS, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal.
8. When the timeout sticks around on Windows, reset the network stack: run ipconfig /release, ipconfig /renew, then netsh winsock reset and netsh int ip reset, and reboot.
9. In Chrome, clear the browser's own host cache at chrome://net-internals/#dns and flush sockets at chrome://net-internals/#sockets, then reload.
10. Move to a public DNS resolver, Cloudflare (1.1.1.1) or Google (8.8.8.8), to sidestep a slow or faulty one.
11. Check your hosts file and strip out any stale entry for the domain.
12. Clear your browser cache, or open the site in an incognito window to test without cached data.

If you run the website

1. Make sure the server is genuinely up and reachable. Connect from a different network or machine, since the timeout might only hit certain routes.
2. Look at whether the server is overloaded or slow to accept connections. Heavy traffic or a backed-up service can keep new connections from finishing in time.
3. Probe the connection at the network level with ping yourdomain.com and curl -v https://yourdomain.com to find where it stalls.
4. Confirm the relevant port is open and listening (443 for HTTPS, 80 for HTTP), and that nothing upstream is closing it.
5. Go through firewall and security rules on the server and at your host or CDN. A rule that drops packets instead of refusing them produces a timeout, not an immediate error.
6. Check that your DNS records point at the correct server IP, and after any DNS change give propagation time before you assume it is fixed.
7. If slow scripts are stalling the response, raise limits like max_execution_time in your PHP or server configuration, and loop in your hosting provider when the cause clearly is not on your side.

On Linux

1. Flush the DNS cache with sudo resolvectl flush-caches. On systems that use it, restart the resolver instead: sudo systemctl restart systemd-resolved.
2. Point your network settings or /etc/resolv.conf at a public resolver, Cloudflare (1.1.1.1) or Google (8.8.8.8).
3. Open /etc/hosts and delete any stale or wrong entry that pins the domain to an outdated IP address.
4. Switch off any VPN or proxy, then reload to rule out a routing problem.

On iPhone or iPad

1. Flip Airplane mode on for a few seconds, then off, to force the network connection to reconnect.
2. Go to Settings, Wi-Fi, tap your network, choose Forget This Network, then rejoin by entering the password again.
3. Under that same Wi-Fi network, set Configure DNS to Manual and add a public resolver such as 1.1.1.1 or 8.8.8.8.
4. Still timing out? Go to Settings, General, Transfer or Reset, then Reset, and choose Reset Network Settings.

On Android

1. Toggle Airplane mode on and off to reset the radios and reconnect to the network.
2. Open Wi-Fi settings, press and hold your network, choose Forget, then reconnect with the password.
3. Set a Private DNS provider under Settings, Network and internet, Private DNS (for example 1dot1dot1dot1.cloudflare-dns.com), or change the DNS for your Wi-Fi network by hand.
4. Clear Chrome's cache from Settings, Apps, Chrome, Storage, then reload the page.

Still not fixed? Next steps

• When the same page times out from a second device and from mobile data too, stop tweaking your own settings. The fault is almost certainly the route or the server, and your next move is confirming the site is down for everyone.
• If Chrome alone fails while another browser loads the page, reset Chrome's network state at chrome://net-internals/#dns and chrome://net-internals/#sockets, then try a fresh profile before you reinstall anything.
• Running the site yourself and it only times out from certain regions? Ask your host or CDN to look for a geographic firewall or a routing rule, because a packet drop on one path is indistinguishable from a full outage.
• Timeouts that flicker on and off rather than staying put need continuous watching from outside your own network, so an intermittent drop is caught the moment it happens instead of after a user complains.

Code & configuration

Copy-paste starting points. Replace example.com and the paths with your own, and test changes on staging before production.

Flush DNS and reset the network stack (Windows)

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset
netsh int ip reset
# then restart your computer

Flush DNS (macOS)

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

How to prevent ERR_CONNECTION_TIMED_OUT

You cannot prevent every timeout, but you can stop being the last to hear about one. Pulsetic checks your website and endpoints from multiple locations every 30 seconds with HTTP, TCP, ICMP, port and SSL checks, and alerts you by email, SMS, voice call, Slack, Discord, Telegram or webhook the instant something stops responding. It will not tune your server for you, but it tells you fast when a connection starts timing out, so you can act before more visitors run into the error.

Learn how Pulsetic's uptime monitoring detects this from the outside, across 15+ locations.