Network and storage devices depend on services upstream of them, so a rushed restart can create confusing false faults. A safe power-up order after an outage restores source equipment first and confirms stability before adding each load.

Quick Answer

After an outage, first confirm the supply and equipment are safe. Then restore the network from upstream to downstream: fibre ONT or modem, router or mesh gateway, switches and satellite nodes, NAS or servers, and the PC. Wait for each device to reach its normal ready state before testing the next link.

Use exact models in the Corsair PSU range and among PSU best sellers when diagnosing a PC power fault. Those pages do not replace the network provider's ONT process or prove a failed device needs replacement.

Stop before power-up when anything looks unsafe

Check for burning smell, smoke, water, cracked plugs, hot sockets, exposed conductors, tripped protection, or visible damage. Do not touch wet electrical equipment or repeatedly reset a breaker.

If several devices failed together, lights are unusually bright or dim, or appliances behave strangely, leave sensitive equipment disconnected and contact the electricity provider or a registered electrician through the appropriate emergency route.

Never open a PSU, UPS, ONT power supply, or fixed electrical enclosure. Preserve the setup and photograph it if an insurance or service assessment may be needed.

When the supply appears normal, disconnect non-essential loads and begin with the smallest required chain. This makes each fault easier to place.

Start at the provider edge

Power the fibre ONT, cable modem, fixed-wireless receiver, or other provider device according to its instructions. Wait for power, optical, link, and service indicators to settle.

An ONT may take several minutes to register. Flashing or red optical indicators can point to a provider line or provisioning problem rather than the router. Do not unplug or look into fibre connectors.

If the provider device remains offline, record indicator states and contact the provider. Power-cycling it repeatedly can delay registration and removes useful evidence.

Where the provider device and router are one unit, treat them as the first step and wait for both service and local network states.

Bring up routing and distribution

Power the router or mesh gateway after the provider edge is ready. Wait for its internet, LAN, and Wi-Fi states. Confirm one wired client or its management page before starting every satellite.

Then power Ethernet switches, mesh satellites, access points, and PoE devices in the order required by their uplinks. A satellite without a gateway can broadcast or blink while having no route to the internet.

Check that DHCP, DNS, and time synchronisation settle. Avoid factory-resetting a router because it takes longer than normal to reconnect. A reset erases configuration and can turn a temporary provider delay into a setup job.

Test local access to the gateway, then an external address or service. This separates the home network from the provider route.

Start the NAS before clients need it

Power a NAS or home server after its network path is stable. Watch its supported status indicators and management page. Storage arrays can need time for file-system checks or service startup after an abrupt loss.

Do not force shutdown or remove drives because boot takes longer than usual. Listen for repeated mechanical faults, check logs, and use the maker's recovery guidance.

Confirm shared folders, backup services, authentication, and any UPS monitoring before starting workloads that write to it. A NAS appearing on the network does not prove every application is ready.

If the NAS shut down cleanly through a UPS, review the UPS and shutdown logs. Recharge and retest the backup system after power stabilises.

Bring PCs and consoles on last

Start the PC after network and storage services are ready. This lets mapped drives, launchers, backups, time sync, and account services connect without a rush of failed retries.

Watch firmware and operating-system startup for repair prompts. Do not approve disk initialisation or formatting after a power event. Back up or assess important data before repair tools write to storage.

For a console, wait for network and external storage before resuming downloads. Let the platform complete its own storage checks. Avoid placing every high-draw device back on one UPS before confirming its load.

Diagnose the first missing hop

If the PC has no internet, check whether it reaches the router. If it reaches the router, check whether the router reports a provider address. If the router is offline, inspect the ONT state.

Use a known-good Ethernet cable and supported port for the baseline. Wi-Fi can add signal and authentication variables. Do not change DNS, reset the router, and reinstall network drivers together.

Record which step fails and its indicator or error. That evidence lets the provider, network technician, or PC support route focus on the right device.

Prepare the order before the next outage

Label power adapters, UPS outlets, network cables, and device roles. Similar DC plugs can use different voltages or polarities, so never swap adapters by fit.

Put the ONT, gateway, and required switches on a measured backup path when internet continuity matters. Configure the NAS for safe automatic shutdown and test it.

Keep a printed startup order near the network cabinet. A dark room is a poor place to remember which small black box is the gateway.

FAQ

Must the ONT always power up first?

It is a useful upstream-first sequence for diagnosis. Combined gateway devices and provider procedures can differ, so follow the exact manuals and service guidance.

How long should I wait between devices?

Wait for normal ready indicators or management status, not a universal number of seconds. Registration, mesh startup, and NAS checks vary.

Should I reset a router that does not reconnect?

Power-cycle only through supported steps and check the ONT or provider state first. A factory reset erases settings and should follow evidence and provider guidance.

Confirm the supply is safe, then restore provider edge, routing, storage, and client devices one hop at a time while recording the first failure.