Isolating the Root Layer: Modem vs Router vs WiFi
When your internet drops, the first step is determining which device in your local network chain is failing. A home network has three potential failure points:
- The WiFi Link: Wireless interference or signal decay between your client device and the router.
- The Router Gateway: The router fails to route local network traffic to the WAN port due to memory, CPU, or firmware errors.
- The Modem / Line: The modem loses sync with the ISP's terminal server due to physical line noise or authentication drops.
To isolate this, run a continuous ping test from a computer. Open two Command Prompt (Windows) or Terminal (Mac) windows:
- In Window 1, ping your router:
ping 192.168.1.1 -t(replace with your gateway IP). - In Window 2, ping a public server:
ping 8.8.8.8 -t.
Watch the windows during a dropout. If both windows display 'Request Timed Out', your connection to the router has failed (WiFi or router crash). If your ping to 192.168.1.1 remains stable (e.g. 1ms, 0% packet loss) but 8.8.8.8 fails, your local network is fine — your modem or ISP line is dropping the connection.
Fiber/GPON Problems: Optical Power Margin & Transceiver Issues
Fiber-to-the-Home (FTTH) networks use **GPON (Gigabit Passive Optical Network)** systems. Unlike copper or coaxial cables, fiber transmits data using light pulses through glass fibers. These systems are highly reliable, but they are sensitive to signal loss caused by physical issues.
**Optical Power Margin** is the measure of light signal strength. It is expressed in negative decibels (dBm). For a GPON ONT (Optical Network Terminal) to function correctly:
- Excellent Signal: -15 dBm to -22 dBm.
- Marginal Signal: -23 dBm to -26 dBm (intermittent packet loss may occur under thermal load).
- Unusable Signal: -27 dBm or worse (the ONT's optical receiver cannot decode the light pulse, causing frequent PON sync loss).
If your ONT's **PON (Passive Optical Network)** light flashes or its **LOS (Loss of Signal)** light blinks red, your optical signal has dropped below the threshold. Common causes include micro-bends in your fiber patch cord (sharp bends leak light out of the glass cladding) or dust on the SC/APC connector end-face. If your fiber patch cord has a sharp bend, straighten it immediately. If signal issues persist, request your ISP to clean the optical ports and measure attenuation with an OTDR (Optical Time-Domain Reflectometer).
ISP Congestion, Node Saturation, and Upstream Packet Loss
ISPs do not provide a dedicated, unshared connection line for each home. Instead, they run a single high-bandwidth connection line to a local neighborhood cabinet (called a **Node** in cable networks or an **OLT** in fiber networks) and split it among 32 to 128 homes.
If your internet drops or slows down only in the evenings (typically between 7:00 PM and 11:00 PM), your neighborhood node is experiencing **Node Saturation**. When too many subscribers download video streams or games simultaneously, the node's output buffer fills up, causing it to drop excess packets. This is called congestion-induced packet loss.
To diagnose node saturation, run a traceroute command:
tracert google.com
Look at the round-trip times (latency) for each hop. Hop 1 is your local router. Hop 2 or 3 is your ISP's local gateway. If Hop 1 shows 1ms, but Hop 2 jumps from 15ms during the day to 150ms+ at night with asterisk (*) symbols (indicating dropped packets), your ISP's local node is saturated. Report these traceroute results to your ISP's tier-2 support.
PPPoE Reconnect Loops and MTU Configuration
Many DSL and fiber connections require your router to authenticate using **PPPoE (Point-to-Point Protocol over Ethernet)**. PPPoE wraps your standard IP traffic inside an authentication layer. This wrapper takes up 8 bytes of space in each packet header.
Standard Ethernet has a maximum packet size of 1500 bytes (called the **MTU / Maximum Transmission Unit**). Because PPPoE consumes 8 bytes, the actual payload size must be restricted to **1492 bytes**.
If your router's WAN MTU size is left at the default 1500 on a PPPoE connection, large packets (like security handshakes or media streams) will exceed the MTU and get fragmented. If the ISP's terminal server drops fragmented packets, the PPPoE session will crash, causing a reconnect loop.
- Log into your router admin panel and open WAN Settings.
- Locate the Connection Type option and verify it is set to PPPoE.
- Find the MTU (or MRU) field and change it from 1500 to **1492**.
- Click Save and reboot your router to apply the new packet size limits.
Latency Spikes and Bufferbloat: How Upload Saturation Kills Connections
Most home internet plans are asymmetrical — they provide fast download speeds but slow upload speeds. For example, a cable plan might provide 300 Mbps download but only 10 Mbps upload.
When a device on your network uploads a file, backs up photos, or runs a cloud sync, it can easily saturate the upload channel. When the upload channel is saturated, the modem's internal memory buffer fills up with pending packets. This is called **Bufferbloat**.
When bufferbloat occurs, simple network acknowledgement packets (TCP ACK) get stuck in line behind the large upload packets. If your computer cannot send ACK packets back to a website, the website stops sending data, assuming your connection has dropped. Your ping latency will spike from 20ms to 1000ms+, causing real-time applications to drop the connection.
To fix this:
- Log into your router, find the **QoS** or **Bandwidth Control** settings, and enable it.
- Set the router's upload bandwidth limit to 90% of your actual speed test result (for example, if you get 10 Mbps upload, set QoS upload limit to 9 Mbps).
- This forces the router to queue packets before they reach the modem, keeping the modem's buffer empty and maintaining low latency.