Purpose-Built Templates

ZU2B Blueprints

Business in a Box

  • Purpose-built launch kits for local service businesses — website, copy, prompts, SEO, and more.
  • Local Launch Kits →

Website Widgets

  • Working features you install once and own outright — no plugin, no subscription.
  • Chat Widget — Coming Soon

Reference

ZU2B Pulse™

See what visitors experience before they leave — paste any public URL and get a plain-English performance report in seconds.

Scan Your URL Free

When One Domain Times Out on One Device While Everything Else Works Fine

Field Note #172
🔬 Resolved 🟢 Beginner ⏱ 30 Minutes ✓ Observation from Experience

⚡ Quick Fix (TL;DR)

The Fix: 1. Rule out the site/hosting first: if other domains work fine on the same network, and the affected domain works fine on a *different* network, the site itself is very unlikely to be the cause.
2. Flush DNS on the affected device as a first, low-effort step.
3. Test the domain on a completely different network (mobile hotspot) to isolate whether the problem is device-level or network-level.
4. If isolated to one network, suspect the router's own DNS cache rather than anything device-side.

Was this helpful? Thanks for the feedback!
The symptom
A specific domain returned `ERR_CONNECTION_TIMED_OUT` when loaded on one laptop, while every other website loaded normally on that same device, and the same domain also loaded normally on a phone using cellular data (not the home WiFi network).

Initial assumption
The first instinct was that the issue was related to a recent change made to the site itself (in this case, a newly added script), since the timing coincided with a recent edit.
 
This assumption was ruled out: `ERR_CONNECTION_TIMED_OUT` occurs before the browser successfully connects to the server at all, meaning no page content, including any script, had loaded or had any chance to be the cause.

Investigation
Working through likely causes in order of scope: flushing the device’s local DNS cache did not resolve it. Trying a different browser and incognito mode did not resolve it, ruling out browser-specific causes (extensions, corrupted cache). Testing the same domain on a different device over cellular data (bypassing the home network entirely) worked fine, narrowing the cause to something specific to the home network rather than the device or the site.

What to check
When a single domain fails to load on one specific network while working fine elsewhere (other devices, other networks, or the same device on cellular data):
 
1. Rule out the site/hosting first: if other domains work fine on the same network, and the affected domain works fine on a *different* network, the site itself is very unlikely to be the cause.
2. Flush DNS on the affected device as a first, low-effort step.
3. Test the domain on a completely different network (mobile hotspot) to isolate whether the problem is device-level or network-level.
4. If isolated to one network, suspect the router’s own DNS cache rather than anything device-side.

Current finding
Restarting the home router (which clears its own DNS cache, separate from any individual device’s cache) resolved the issue. The underlying reason a stale cache entry existed only for that one domain was not conclusively determined.

Troubleshooting lesson
A domain that fails to load on exactly one network, while working everywhere else including other devices on the same network’s cellular fallback, points to the router itself holding a stale or bad DNS entry — not the site, not hosting, and not the browser. A router restart is a fast, low-risk step worth trying before escalating to a hosting provider.

Tagged in :

More from the field