ERR_CONNECTION_TIMED_OUT in Chrome
Separate a site taking too long to connect from a failure affecting every site or only the Chrome profile.
Try this first
1 quick checks · ~3 min
Step-by-step solutions
Compare another site before changing the network
The scope determines the next check.
Check the address and reload once. If you just submitted a payment or form, check its status before submitting again.
Open another known site. If only one fails, retry later and report the timeout to its operator; if several fail, check the computer’s connection.
Compare an Incognito window
This can identify a profile difference, not diagnose the server.
Open the same address in an Incognito window. If it works there, return to your regular profile and review extensions.
Temporarily disable extensions you manage and test, then re-enable them one at a time to identify a difference. Do not alter organization-managed extensions or blindly clear cookies.
Update Chrome and keep the result
Save forms before closing the browser.
Open the Chrome menu > Help > About Google Chrome. Apply an available update and relaunch when requested.
If it persists with a VPN, proxy or organizational filtering, give the administrator the domain and error. Do not disable the firewall to make a page load.
Still not working?
If every site fails and Windows shows a connection without internet, use the related Wi-Fi or Ethernet guide. If the message changes to ERR_NAME_NOT_RESOLVED, follow its DNS diagnosis. Record URL, time and comparisons for support without publishing private URL parameters.
Sources
Documentation behind this guide. Editorial recommendations are identified separately.
- Google Chrome HelpOfficialGet help with common error messages in Chrome
- Google Chrome HelpOfficialFix connection and loading errors in Chrome
Source review: . A documentation review, not a physical hardware test.
Related problems
Wi-Fi connected but no internet
Joining Wi-Fi does not guarantee internet access. Compare another device on the same network to separate a PC-specific problem from a local-network or provider-side issue.
View solutionEthernet connected but no Internet
Windows detects a connected Ethernet link, but Internet access fails. A physical link does not establish that the router has Internet access: separate cable, port, PC and network.
View solutionERR_NAME_NOT_RESOLVED in Chrome
Check the site name and distinguish DNS name-resolution failure from a slow site or a general connection outage.
View solution