Nothing on the network has internet
Use the whole-network path first so WAN, modem, provider, and restart-order checks stay ahead of Wi-Fi-only guesses.
Use this page when the network is the problem but the right path is not obvious yet. Start from what is failing in real life, then move into the cleanest guide or flow.
Use the whole-network path first so WAN, modem, provider, and restart-order checks stay ahead of Wi-Fi-only guesses.
Start with the dead-zone or one-room path before treating the whole network as the problem.
Use the drops path when the main clue is timing or repeat instability, then switch to the flow when you need the tighter evidence-first version.
Switch to the planning and comparison layer when the symptom points to layout, coverage shape, or equipment-role issues.
Start with the WAN and modem path before assuming the Wi-Fi gear is the real problem.
Separate one-room coverage problems from broader network or device issues first.
Use pattern timing and scope to separate WAN instability from Wi-Fi behavior.
Start with placement and coverage shape before deciding the answer is more hardware.
Use the reachability path when the network works broadly but one device path does not.
Switch to the planning and comparison layer when the symptom points to a bigger layout issue.
First decide whether the problem affects everything, one room, or one device path. That one distinction usually chooses the right next page faster than any gear guess.