Independent technical referenceOfficial site
  • Software and digital services
  • Web browsers

ERR_CONNECTION_TIMED_OUT

ERR_CONNECTION_TIMED_OUT in Google Chrome: the connection takes too long

Verified with sources3 sourcesReviewed Oct 3, 2026
Technician coming? See the 2 steps they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

Chrome tried to connect to the site and the wait timed out. It may be a slow connection or a busy site. Check whether other sites load, restart the router if they all fail, and try another network.

Safety first

Stop and check this first

  • If the site fails only from your network, restarting the router again and again will not fix it: note the times and take them to your provider.

Safe checks you can perform

  • How fast other sites load
  • Modem and router
  • The site from another network
  • Server load and reachability

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Line check by the provider
  • Do not attempt this professional task: Diagnose the site's server

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Line check by the provider

    What they doThe internet service provider checks the line and router if timeouts affect every site.

    They must show youthe result of their line test.

    In writingfault found and fix applied.

  2. Diagnose the site's server

    What they doThe operator matches the time of the report with server load and server and firewall logs.

    They must show youmetrics or logs from that time.

    In writingcause found and change applied.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. How fast other sites load

    No special tools

    Who:
    you.
    How:
    open several well-known sites and see whether they load normally.
    Result that matters:
    whether the slowness is general or only this site.
    If everything is slow or fails:
    it points to your connection; continue with the router.
    If the others load fine:
    rule out your general connection and test this site from another network.
    Evidence to keep:
    time and sites tried, with their result.

    Evidence: Google Chrome Help - Get help with common error messages in Chrome · Google Chrome Help - Fix connection and loading errors in Chrome

  2. Modem and router

    No special tools

    Who:
    you.
    How:
    restart the modem and router as Chrome Help suggests and test again once the connection lights are steady.
    Result that matters:
    whether sites load after the restart.
    If they load again:
    the router or the line was the source.
    If every site still fails:
    contact your internet service provider with the times you noted.
    Evidence to keep:
    times of the restart and of later failures.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

  3. The site from another network

    No special tools

    Who:
    you.
    How:
    open the same address on your phone using mobile data, with Wi-Fi off.
    Result that matters:
    whether the timeout repeats outside your network.
    If it also times out:
    it indicates the site is busy or down; wait or tell the operator.
    If it opens on mobile data:
    the block is in your network or device; check firewall and antivirus.
    Evidence to keep:
    a screenshot of the error on each network with the time.

    Evidence: Google Chrome Help - Get help with common error messages in Chrome

  4. Server load and reachability

    Tools required

    Who:
    the site operator.
    How:
    review server load and logs at the time of the failure, and test a connection to the public port from an outside network.
    Result that matters:
    whether the server accepts the connection in time.
    If it does not answer from outside:
    it indicates overload, an outage or a filter dropping packets before the server.
    If it answers normally from outside:
    the break is on the visitor's path; ask for their network and time.
    Evidence to keep:
    load metrics and the outside test result with the time.

    Only the site operator. Restarting production services must follow the team's procedure; if you do not run it, stop and report.

    Evidence: Chromium source - net/base/net_error_list.h (network error list)

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Google Chrome
Product type
Web browsers

Known code variants

  • ERR_CONNECTION_TIMED_OUT
  • ERR_CONNECTION_TIMED_OUT (-118)
  • ERR_CONNECTION_TIMED_OUT Chrome
  • net::ERR_CONNECTION_TIMED_OUT

What it means

Chromium defines ERR_CONNECTION_TIMED_OUT (-118) as a connection attempt that timed out; it sits in the connection error range. Chrome Help says the page took too long to connect and that your connection might be too slow or the page too busy. It also lists firewall, antivirus and router among the factors behind connection errors. The code does not separate your network, your provider's network and the server: you separate them by testing from another network.

Warnings and stop conditions

  • Loweditorial warning

    If the site fails only from your network, restarting the router again and again will not fix it: note the times and take them to your provider.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

Symptoms and causes

Probable causes · in order

  • Slow or unstable connectionPossible

    If other sites are also slow or fail, the problem is in your network, router or provider.

    Evidence: Google Chrome Help - Get help with common error messages in Chrome · Google Chrome Help - Fix connection and loading errors in Chrome

  • Busy or down sitePossible

    If only this site fails, also from another network, the server is not answering in time.

    Evidence: Google Chrome Help - Get help with common error messages in Chrome

  • Firewall or antivirus holding the connectionPossible

    Suspect it when the site opens from another device on the same network but not from this one.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

Virtual technician

Does ERR_CONNECTION_TIMED_OUT still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Sources and technical references

Sources: Chromium source - net/base/net_error_list.h (network error list) · Google Chrome Help - Get help with common error messages in Chrome · Google Chrome Help - Fix connection and loading errors in Chromereviewed 2026-10-03 · verified

Was this entry useful?