Connection timed out: check where access stops

What does this mean?

A connection timeout means the requested connection did not complete in time. It does not identify a single cause. DNS may point to an unreachable address, a firewall may block access, or the server may be unavailable. The browser’s exact error wording helps distinguish connection failure from a gateway timeout.

What should I check first?

Test the same URL on a second network, such as mobile data, and check an unrelated website. If only one local network fails, investigate its proxy, DNS and filtering first. Record the address, time and browser error; do not publish your full network configuration or private addresses in a help forum.

How can I diagnose the cause?

Use DNS lookup to inspect both A and AAAA records for the exact hostname. An outdated IPv6 address can explain why some visitors fail while others succeed. Compare the records with the addresses supplied by the host. Check the host’s status page and any firewall event logs you can access.

How do I fix it safely?

Correct a confirmed wrong address in the authoritative DNS zone after saving the old settings. If DNS is correct, ask the host whether the public web listener and firewall are reachable. Avoid removing the entire firewall or changing unrelated mail records. Do not rely on ping alone; some working servers intentionally ignore it.

Verify the fix and know when to contact your provider

After a targeted change, retest from both networks and allow existing DNS caches to expire where relevant. Escalate if the correct public endpoint remains unreachable. Give the provider the hostname, IPv4 and IPv6 results, timestamps, networks tested and exact error, so they can inspect the correct service.

Work through these checks in order

1. Compare Wi-Fi and mobile-data access to the exact same hostname. Record a success as well as a failure, because a network-specific result helps the host avoid investigating the wrong layer.
2. Query A and AAAA separately. Compare both with the hosting account’s assigned addresses; do not assume an IPv4 success proves the IPv6 destination is correct.
3. Ask the host to check the public web listener and firewall for the failing address family. Provide time and hostname, and make clear whether the browser failed before any HTTP response appeared.

Which tool can help?

DNS lookup · Nameserver checker

DNS tools show one resolver’s public answers. Record explainers do not authenticate a message, and calculators do not monitor a server. Use the evidence alongside your provider’s logs.