Cable / Fiber Modem & ONT diagnostic guide

Cable / Fiber Modem & ONT: test the fault before changing parts or settings.

Use browser network evidence to determine whether the problem is local to one device or more consistent with the gateway, modem, ONT or ISP path.

4 relevant tests3 first checksBrowser limits stated

Start with a clean baseline

Separate the local link from internet reachability and application performance. Wi-Fi marketing speed, Ethernet port speed, ISP speed and browser throughput are different measurements.

Live evidence

Relevant checks

First sequence

Do the high-signal checks before risky changes

  1. 1

    Check gateway/modem status lights against the provider manual

  2. 2

    Test another device on the same connection

  3. 3

    Contact the ISP when multiple devices fail and modem/ONT status indicates loss of service

Decision points

What the result should change

If one client fails, others workPrioritize the client adapter, saved network, cable/port or device policy.
If all clients lose internet but stay associatedPrioritize WAN/modem/DNS/upstream status rather than each device.
If wired is stable and wi-fi is notPrioritize RF placement/interference/channel/client-band behavior.
Browser can help check
  • Confirm web reachability
  • Time requests to DeviceOK
  • Show the public-facing address seen by DeviceOK
Browser cannot prove
  • Read DOCSIS or optical signal levels generically
  • See ISP provisioning state
  • Restart or reprovision protected provider equipment

Repair boundary

Know when to stop browser troubleshooting

  • Do not factory-reset a managed or ISP-provisioned router before saving configuration and credentials.
  • Do not infer 2.5/10GbE from Wi-Fi class names; verify the exact physical ports.
  • Browser Network Information API values are hints and are not a replacement for router/switch counters.

Used-device inspection

What to verify before paying or signing off a repair

  • Verify exact WAN and LAN port speeds
  • Check Wi-Fi generation/bands supported by your actual clients
  • Check mesh/backhaul and VLAN/PoE needs before choosing hardware