A page says not found, so you restart the router. That may not address the problem. A genuine HTTP 404 response means a server responded but did not find the requested resource.
Read the actual message
MDN’s 404 reference explains that the code does not establish whether the absence is temporary or permanent. A mistyped or moved URL can be involved, but the status alone does not identify the exact cause.
A browser message about failing to connect or resolve a name describes a different stage. Record the wording instead of grouping every failure under internet broken.
Check the address and route
For an ordinary public page, compare the link with the site’s current navigation. Look for a typo or an outdated path. Do not guess addresses for private resources or bypass an access restriction.
If reporting the issue, include where the broken link was found and when you checked it. Remove sensitive parameters before sharing publicly.
Avoid broad fixes first
Changing network settings is unlikely to repair a genuinely missing page. Start with the evidence supplied by the error and make one relevant check at a time.
Our guide to URL components helps you explain which address failed, while keeping the distinction between reaching a server and finding its resource clear.