Home Network Down? Recover It One Device at a Time

Start with the chain, not the settings

A home network recovers faster when you test one link at a time: internet service, modem or optical network terminal, router, Wi-Fi or Ethernet, and finally the device. First ask whether every device is offline or only one. Then preserve the current settings, check the provider's outage notice over cellular data, inspect power and cables, restart the network in upstream-to-downstream order, and test with one known device. A factory reset is a last resort because it can erase the configuration you need.

The method works because "the internet" is not one box. A phone can remain connected to Wi-Fi while the router has lost its upstream connection. A laptop can fail while every other device is healthy. A single website can be unavailable while the home network is fine. Recovery begins when you stop treating those different failures as one symptom.

Draw the network in one minute

Most homes contain some version of this path:

provider line -> modem or ONT -> router -> Wi-Fi access point or Ethernet switch -> device -> app or website

Some providers combine the modem and router in one gateway. Mesh systems add a primary router and one or more mesh points. An optical network terminal, or ONT, converts a fiber connection for the home. Labels and indicator meanings vary by model, so use the exact provider or manufacturer manual rather than assuming that a red, amber, or blinking light has a universal meaning.

Write down the equipment in order. Photograph cable locations and the router label without sharing the image; it may contain Wi-Fi or administrative credentials. Note which box belongs to the provider and which belongs to you. This small map prevents a long evening of restarting the same downstream device while the upstream link remains down.

Step 0: Stop for damaged or unsafe hardware

Do not open a modem, ONT, router, power adapter, wall plate, or electrical enclosure. Do not handle equipment or power supplies that are wet, swollen, scorched, sparking, producing smoke or a burning smell, or unusually hot. Keep people away and contact the provider, manufacturer, building manager, or a qualified electrical professional as appropriate.

If the equipment looks physically sound, save open work on devices that still have a local connection. Tell other people in the home before interrupting service. A restart disconnects everyone temporarily, including calls, streams, smart-home controls, and security devices that rely on the network.

Step 1: Find the scope with three comparisons

Use a simple matrix before changing anything:

These results are evidence, not proof. A second device might carry a cached page, a mobile connection might silently take over, and an Ethernet cable might have its own fault. Disable cellular data temporarily only when you need to prove that a phone is using Wi-Fi, then turn it back on after the test.

For the narrower case where Wi-Fi says connected but pages do not load, use our published Wi-Fi connected, no internet guide. This pillar continues when the whole network or an unknown part of the chain appears down.

Step 2: Check the provider before touching configuration

Use cellular data or another connection to open the internet provider's official status page or app. Check for a declared outage, maintenance, or an account action. If neighbors use the same provider, their status can be useful context, but it does not replace the provider's result; buildings and streets can sit on different equipment.

Record the time the failure began and whether power or service returned just before it. Do not rely on an unverified social post for restoration times. If the provider reports an outage, repeated resets will not repair it and may leave your equipment harder to restore when service returns.

Step 3: Inspect each physical link without rearranging everything

Work from the provider side toward the device:

1. Confirm that each required power adapter is seated and that a switched power strip has not been turned off.
2. Check the provider cable, fiber handoff, coax, or Ethernet lead for an obviously loose connector without forcing it.
3. Confirm that the modem or ONT connects to the router's designated internet or WAN port, not an ordinary LAN port, using the original map or manual.
4. Check any Ethernet switch or mesh point only after the upstream boxes are accounted for.
5. Examine cables for crushed insulation, broken latches, severe bends, or exposed conductors. Replace a removable low-voltage data cable with a known-good equivalent if the equipment manual permits it. Route damaged building wiring or power hardware to a qualified person.

Do not unplug an optical fiber connector or stare into a fiber port. Fiber ends are delicate, contamination-sensitive, and potentially hazardous to inspect without the correct procedure and equipment. Contact the provider for an ONT or fiber fault.

Indicator lights can tell you whether a box has power or sees a link, but the manual supplies the meaning. Write the observed label, color, and pattern exactly. "Internet light blinking green" is useful when calling support; "router angry" is not a diagnostic state.

Step 4: Restart, but do not reset

A restart, reboot, or power cycle keeps the saved configuration. A factory reset can erase it. The buttons may sit close together, so read the label before pressing anything. Do not press a recessed Reset button during this step.

For a separate modem or ONT and router, follow the provider's exact order if it publishes one. The general sequence in Microsoft's current Windows connection guide is:

1. Disconnect power from the router.
2. Disconnect power from the modem.
3. Wait at least 30 seconds. A modem with battery backup may require provider-specific instructions.
4. Reconnect the modem and wait for its documented ready state.
5. Reconnect the router and wait a few minutes for it to start fully.
6. Test again with one device.

If a single provider gateway combines both roles, restart that one device according to its manual. If you have a mesh system, follow its documented restart sequence; do not invent an order from the position of the boxes in the room.

A power cycle clears temporary state and forces fresh link negotiations. It does not fix a damaged cable, provider outage, expired account, bad firmware, or persistently wrong configuration. If one careful restart changes nothing, continue collecting evidence instead of repeating it.

Step 5: Test one known path

Pick one recently working device. Stand near the primary router. Confirm that it joined the intended network name, not a guest network, a neighbor's network, or a phone hotspot. Load several unrelated sites or services.

If the device connects locally but cannot reach the internet, open the router or provider app using the documented method. Look for plain status fields such as internet or WAN connection, assigned address, and provider connection. Do not change settings yet. Save the exact status text and time.

If you already have a known-good Ethernet path, compare it with Wi-Fi. Do not create a direct modem-to-computer test unless the provider or manufacturer instructs it for your exact setup. Direct attachment can require a modem restart, expose a device differently, or fail because the provider remembers the previous equipment address.

Step 6: Repair one failing device without disturbing the home

When other devices work, stop changing the router. On the failing phone, tablet, or computer:

• turn Wi-Fi off and on;
• confirm airplane mode is off;
• restart the device after saving work;
• check whether a VPN, proxy, security product, or captive portal applies;
• forget and rejoin the network only after confirming the Wi-Fi password.

Forgetting a network deletes its saved credentials on that device. Apple's current Wi-Fi troubleshooting guidance also says network-settings reset should be used only after other solutions fail; on current Apple devices it removes saved Wi-Fi networks and passwords plus cellular, VPN, and APN settings. Paths change by operating-system version.

Microsoft likewise treats Windows network reset as a last step. It removes installed network adapters and their settings, reinstalls adapters after restart, and may require VPN clients or virtual switches to be installed or configured again. Do not use a device-wide network reset to solve a whole-home outage. On a managed work or school device, contact the administrator before removing or resetting network configuration.

Step 7: Separate DNS failure from internet failure

Domain Name System, or DNS, turns a name such as example.com into an address a device can use. DNS may be involved when several devices can maintain existing connections but new names fail to resolve. That pattern is not conclusive: cached results, app behavior, firewalls, and service failures can look similar.

Check the router status and provider notice first. Record any exact DNS message without assigning it an invented meaning. Do not change every device to a public resolver as an opening move; that creates several new configurations before you have shown the shared resolver is the broken link. If testing a different resolver becomes justified, change one reversible test device, record the old automatic/manual state, and follow current operating-system instructions.

Step 8: Treat firmware as maintenance, not a panic button

Firmware can fix defects and security issues, but an update is not a low-risk experiment during unstable power or an unexplained outage. Use only the provider's app or the manufacturer's official administration interface and instructions for the exact model. Confirm the model and hardware revision, preserve the configuration if the product offers a documented export, and do not interrupt an update.

CISA recommends keeping wireless access-point software and firmware patched and changing default administrator passwords. Its wireless-network guidance identifies WPA3 as the strongest listed Wi-Fi protection. After service is stable, use the strongest current mode supported by your required devices and recommended by the maker or provider. Do not weaken security merely to make an old device connect without first understanding the tradeoff.

When is a factory reset justified?

A factory reset is destructive. Depending on the equipment, it can erase the Wi-Fi name and password, administrator password, provider settings, mesh pairings, guest networks, parental controls, reserved addresses, port forwarding, and other local configuration. It may also disconnect devices that cannot be reconfigured immediately.

Consider it only when all of these are true:

• the provider or manufacturer documents it for the exact model and current symptom;
• there is no unresolved provider outage or unsafe hardware;
• ordinary restart and link tests are complete;
• you have the account access, setup method, and any provider credentials needed to rebuild;
• you have recorded or exported every required setting;
• everyone affected accepts the downtime.

If any item is missing, stop and contact support. A factory reset performed without a restoration plan can replace one outage with a second, self-created one.

What to give the provider or manufacturer

A useful support handoff is short and specific:

• service address and account verification through the provider's secure process;
• equipment model and ownership: provider-supplied or personally owned;
• start time and any outage notice;
• exact light labels, colors, and patterns;
• which devices fail and whether Ethernet and Wi-Fi differ;
• restart time and result;
• exact status or error text;
• any recent power event, cable move, firmware update, or equipment change.

Do not send Wi-Fi passwords, administrator passwords, recovery codes, or a full photograph of a credential label through an unverified message or public post. Use the provider's official support channel.

Build a recovery record after service returns

Once the network is stable, record the normal indicator state, equipment order, model numbers, support links, provider account route, and the date firmware was checked. Keep credentials in a password manager, not in the troubleshooting note. Label both ends of removable Ethernet cables.

Then review the network recovery library for the symptom-specific guide you will need next time. The goal is not to memorize a router interface. It is to preserve enough evidence that the next failure begins halfway up the ladder.

Sources and scope

This workflow was checked against current troubleshooting from Microsoft, Apple, and CISA. Equipment labels, paths, light meanings, and reset effects vary by operating-system version, device maker, provider, administrator, and region.

Back up irreplaceable data before deleting network data, removing accounts or adapters, resetting settings, or reinstalling software. Use official instructions for the exact model. Do not bypass workplace or school controls. Route damaged, swollen, wet, overheating, scorched, or electrically unsafe hardware to the provider, manufacturer, building manager, or a qualified repair professional.

An independent publication. Not affiliated with any prior owner of this domain.