CheckWebsiteNow

Connection errors

ERR_TIMED_OUT

Loading the page took too long and the browser gave up.

Quick answer

A step of loading the page, not only connecting, did not finish in time. A slow connection or a busy website is the usual reason.

When to wait: Often yes; try again in a few minutes.

If you are visiting the website

  1. Wait and reload Wait a few minutes, then reload the page once. Busy websites often recover on their own.
  2. Check your own speed Open a few other websites or a video. If everything is slow, your connection is the bottleneck, not this website.
  3. Pause big downloads Large downloads, backups, game updates or several video streams on the same network can slow other traffic. Pause them and try again.
  4. Try another network Switch from Wi-Fi to mobile data, or the other way round. If the site works there, your network or internet provider may be involved.
  5. Restart your connection Turning the connection off and on gives you fresh network links. In Chrome or Edge you can also open chrome://net-internals/#sockets and click 'Flush socket pools' to drop stuck connections.
    Windows
    Click the network icon in the taskbar, turn Wi-Fi off, wait ten seconds and turn it on again.
    macOS
    Click the Wi-Fi icon in the menu bar, turn Wi-Fi off, wait ten seconds and turn it on again.
    Android
    Turn Airplane mode on, wait about ten seconds, then turn it off again.
    iPhone and iPad (iOS)
    Turn Airplane mode on in Control Center, wait about ten seconds, then turn it off again.
  6. Try a private window Open the site in a private (incognito) window. If it loads there, an extension may be slowing it down; turn extensions off one at a time to find it.

If you run the website

  1. Find slow pages Check which requests take long and why: slow database queries, calls to outside services and large files are common reasons.
  2. Measure from outside Run curl -v --max-time 30 https://example.com/slow-page (use your URL). If curl stops at the limit after connecting, the server accepted the connection but answered too slowly.
  3. Move long tasks to the background Let reports, imports and exports run as background jobs and show progress, instead of keeping the browser waiting.
  4. Review proxy timeouts last nginx waits 60 seconds by default between two reads from the app (proxy_read_timeout). Raise it only for specific slow endpoints and only after fixing the cause; test with sudo nginx -t, then sudo nginx -s reload.
  5. Check your hosting provider's status Your host may have a known outage. Their status page or support can confirm it.

How it differs from ERR_CONNECTION_TIMED_OUT

ERR_CONNECTION_TIMED_OUT happens at the very start: the server never answered the connection request. ERR_TIMED_OUT can happen at any step, also after the connection worked.

So with ERR_TIMED_OUT the server is often reachable but slow. That points more toward a busy website or a slow connection than toward a site that is fully down.

What this error is not

It is not a sign of a virus or a hacked device. It is also not a blocked site: a block usually shows a clear refusal or a block page.

Deleting all your browser data will not speed up a slow server. Keep your data and start with the quick checks above.

For developers: what happens technically

Chromium uses error -7, "An operation timed out," for any network step that hit its time limit. That can be reading the response, a proxy step or a stalled transfer.

Check where time is spent with the browser's network panel or with curl -v. A long wait before the first byte points to the server or app.

Common questions

Is the website down?

Not always. ERR_TIMED_OUT often means the site is slow rather than gone. Try again in a few minutes or test it from another network.

Can a slow Wi-Fi signal cause this?

Yes. A weak signal or a crowded network can delay data until the browser gives up. Moving closer to the router or using mobile data is a quick test.

Why does only one website time out?

If other sites are fast, that one website is probably overloaded or has a slow page. You can wait, or tell the owner the exact page and time.

Likely causes

  • Common A slow or overloaded website. (Website side)
  • Common A slow or unstable internet connection. (Your side)

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: