Errors / Network errors

net::ERR_CONNECTION_TIMED_OUT

The server took too long to answer, and the browser gave up.

The page, or the part that depends on that request, hangs and then fails.

Why it happens

• The server is overloaded or down, or a firewall silently drops the connection.
• A third-party host that is slow or blocked in the visitor's country.
• ERR_TIMED_OUT is the same, for a request that connected and then waited too long.

How to fix it

1. Check the server's load and health; for third parties, their status page.
2. Load non-essential third-party scripts async so a slow host does not hold the page.
3. Check whether it is the whole page or one request: in DevTools' Network panel, a single third-party host timing out while the rest loads is theirs, and it only hurts when a script waits on it. A timeout on the page itself, from several networks, is the server or its firewall; a timeout from one country only points at blocking or routing on the way.

Whose problem it is

Either the site's own code or a third party's, depending on where it comes from.

Often seen with

• ERR_CONNECTION_REFUSEDThe server at that address exists but refused to take the connection.