IT Error Decoder

How to Fix Windows: ERR_CONNECTION_TIMED_OUT

Last reviewed

Error message

ERR_CONNECTION_TIMED_OUT — the website takes too long to respond.

Connection timeouts are usually network-path issues, not name resolution issues. They show up after DNS works.

What this error means

The Windows machine couldn't establish a TCP connection to the destination within the timeout window. Either the destination is down, unreachable, or a network device is dropping packets silently.

Why this happens

Common causes: VPN intercepting traffic, firewall blocking outbound, ISP routing issue, destination server is genuinely down, or DNS resolved to a stale IP.

Quick fix (for end users)

  • Try a different network — phone hotspot is fastest.
  • If you're on VPN, disconnect and retest.

Admin / engineer fix

  • Test the connection at the TCP layer.

    command
    Test-NetConnection -ComputerName <hostname> -Port 443
  • Trace the route to find where packets are dying.

    command
    tracert <hostname>
  • Flush DNS in case the resolved IP is stale.

    command
    ipconfig /flushdns

Step-by-step fix

  1. Test from another network to see if it's local.

  2. Run Test-NetConnection to confirm port is reachable.

  3. Trace route to find where it fails.

Affected products

Windows · Browsers

Common variations of this error

People also see these phrasings of the same problem:

  • ERR_CONNECTION_TIMED_OUT chrome
  • Connection timed out edge

Still broken? Try these

  • Check Windows Defender Firewall — temporarily disable it to test (re-enable immediately).
  • If on corporate network, check whether SSL inspection or web filter is mid-stream killing the connection.
  • Check the destination's status page if it's a SaaS service.

Related errors

Related searches

  • err_connection_timed_out fix windows
  • tracert command

Frequently asked questions

What does "Windows: ERR_CONNECTION_TIMED_OUT" mean?

The Windows machine couldn't establish a TCP connection to the destination within the timeout window. Either the destination is down, unreachable, or a network device is dropping packets silently.

What causes "Windows: ERR_CONNECTION_TIMED_OUT"?

Common causes: VPN intercepting traffic, firewall blocking outbound, ISP routing issue, destination server is genuinely down, or DNS resolved to a stale IP.

How do I fix "Windows: ERR_CONNECTION_TIMED_OUT"?

1. Test from another network to see if it's local. 2. Run Test-NetConnection to confirm port is reachable. 3. Trace route to find where it fails. Always test changes in a non-production environment first.

Browse more errors in Windows Admin: Fix Windows administration errors. Access denied, RPC server unavailable, trust relationship failures, Group Policy errors, and network path issues. Or paste your own error into the error decoder tool to find a match. You can also go back to the homepage to browse common errors by topic.