Skip to content
ERR_CONNECTION_TIMED_OUT6 troubleshooting steps2 sources linked

ERR_CONNECTION_TIMED_OUT: check one slow site or the network

The page took too long to connect. Google also groups ERR_TIMED_OUT here and names a slow connection or a busy destination; compare one failing site with general browsing before changing settings.

By Glitchary · Updated · 2 min read

The short version

  1. 01Record the exact address and whether Chrome shows ERR_CONNECTION_TIMED_OUT or ERR_TIMED_OUT.
  2. 02Check whether other websites connect normally on the same device.
  3. 03Retry the failing address later if only that destination is slow.
  4. 04Compare the same address in another browser or permitted network.
  5. 05Use Google's shared connection procedure if the timeout affects Chrome or multiple sites.
  6. 06Give persistent one-site timeouts to the owner with the time and comparison results.

Raw message

ERR_CONNECTION_TIMED_OUT / ERR_TIMED_OUT

Likely causes

  • The requested page takes too long to connect.
  • Google names a slow internet connection or a busy page as possible causes.

The browser waited too long for the connection

Google groups ERR_CONNECTION_TIMED_OUT and ERR_TIMED_OUT as a page taking too long to connect. Its possible causes include a slow internet connection or a busy destination. Our first comparison is unrelated sites on the same device; the browser code does not supply a universal timeout duration.

Compare the same destination before changing the device

For a single failing address, our recommendation is a later retry and another browser or permitted network. Retain the exact address and time. If multiple sites also fail, use Google's shared connection route; that procedure begins by distinguishing one-site failures from broader browsing problems.

Send a persistent destination failure to its owner

Our recommendation is to give the owner the URL, incident time and browser/network comparisons. A working alternative network helps describe the failure but does not prove the server is healthy or the first network is faulty. Use the code for the stage it identifies, then let the owner or administrator investigate that evidence.

Sources and review notes

Checked on . Based on Google's combined timeout definition and shared connection procedure. Later retries, consistent comparisons and the information to retain are editorial guidance. ERR_TIMED_OUT is covered here rather than published as a duplicate page. Glitchary is independent of Google.

Tags

chromebrowsererr-connection-timed-outerr-timed-outtimeoutslowconnectionbusy