A site that loads after a router restart was blocked in your local connection path, not repaired on the server. A restart clears several temporary states at once, so it hides which one caused the failure.
A router is the box that joins your devices to your internet provider. It holds short-term records for addresses, connections, and name lookups. Clearing all of them together removes the clue.
Table of Contents
- What a Restart Actually Resets
- Why Only One Website Breaks
- How to Tell a Local Fault From Real Downtime
- What to Record Before You Close the Ticket
What a Restart Actually Resets
A restart drops the router DNS cache. That cache turns names like example.com into numeric addresses.
A bad or expired entry can break one site while the rest work. It also renews the DHCP lease, which is the temporary address your provider gives your router. It clears the NAT table, which tracks active connections from your devices. It also restarts stuck IPv6 tunnels and overheated or overloaded router memory.
Why Only One Website Breaks
A single-site failure often points to name resolution or a cached route. Your computer may hold a stale DNS answer for that domain. Your browser may reuse a dead keep-alive connection to that server.
Other triggers affect only certain sites. A content delivery edge node may refuse an old connection. A firewall rule may block one address range. A mismatch between IPv4 and IPv6 can fail on hosts that prefer one path.
How to Tell a Local Fault From Real Downtime
Test from outside the same network before you log a site outage. Use these checks in order: If it loads on phone data but not on office Wi-Fi, the fault sits with that local network. If it fails in both places, treat it as a possible server, domain, or certificate issue.
- Load the page on phone data with Wi-Fi off.
- Load it in a private browser window.
- Ask one person on a different provider to load it.
- Check your hosting control panel for resource limits or blocks.
What to Record Before You Close the Ticket
Do not report "fixed by reboot" as the cause. Record the error code, time, affected address, and who could still reach the site. A screenshot of "DNS error," "Connection Refused: What the Difference Tells You”>connection timed out," or "certificate invalid" points to different next steps. For site owners, check domain expiry, certificate validity, firewall blocks, and server error logs. For managers, ask the reporter for provider name, location, and whether a VPN changed the result. That detail lets support reproduce the path instead of chasing a cleared cache.
