The Demarcation Point: Where Your Network Ends and the ISP Begins
Every ISP connection has a demarcation point — the physical boundary between what you own and what the ISP owns. For cable connections it is typically the coaxial port on the back of the modem; for fiber it is the optical network terminal (ONT). Everything on your side of that boundary is your responsibility to diagnose and fix. Everything on the ISP's side is theirs. The test that definitively answers “ISP or my network?” is bypassing your router and connecting a laptop directly to the modem.
The Bypass Test: The Single Most Diagnostic Step
To isolate the ISP from your home network:
- Connect a laptop directly to the modem using an Ethernet cable (not through the router).
- Power-cycle the modem — unplug it, wait 30 seconds, plug it back in. Wait 2 minutes for it to fully re-register with the ISP.
- Run a speed test and a packet loss test (
ping -c 100 1.1.1.1on macOS/Linux;ping -n 100 1.1.1.1on Windows). - Compare the result to your subscribed plan speed.
If the direct modem connection is clean — good speed, no packet loss — everything upstream of your router is working, and the problem is in your home network (router, Wi-Fi, or a specific device). If the direct modem connection also shows slow speed or packet loss, the problem is the modem, the physical line, or the ISP's network. That is your evidence for contacting the ISP.
Reading the Modem Signal Page
Before calling the ISP, check the modem's status page at 192.168.100.1. This page shows the physical signal quality of the connection between your modem and the ISP's head-end. Poor signal here confirms a line problem that is the ISP's responsibility to fix.
| Signal Metric | Target Range | Out-of-Range Meaning |
|---|---|---|
| Downstream power level | −7 to +7 dBmV | Too high or too low indicates signal strength problems on the outside line |
| Upstream transmit power | 38–48 dBmV | Above 51 dBmV means the modem is straining to reach the ISP — line attenuation problem |
| SNR (downstream) | >30 dB | Low SNR means noise on the line; causes packet errors and retransmissions |
| Uncorrected errors | Zero or near-zero | Rising uncorrected errors indicate physical layer problems (bad cable, connector, splitter) |
| T3/T4 timeouts in event log | None | T3/T4 timeouts confirm upstream channel loss — almost always an outside plant problem |
Running MTR to Pinpoint the ISP vs Your Network Boundary
MTR (My Traceroute) shows latency and packet loss at every hop between you and a destination. Run it from a direct modem connection to confirm the bypass test findings:
# macOS / Linux
mtr --report --report-cycles 100 1.1.1.1
# Windows: use WinMTR, set target to 1.1.1.1, run 100 cyclesIn the output, hop 1 is your modem (or the ISP's first device). Hop 2 is the ISP's first router. If packet loss appears at hop 2 and continues through subsequent hops, the problem is definitively on the ISP's network — it began at their first router, not in your equipment. This single piece of output is the clearest possible evidence for an ISP support escalation.
What “Your Network” Problems Look Like
Problems on your side of the demarcation point have characteristic patterns. If the direct modem connection is clean but the router connection is slow, the router is the bottleneck — check its CPU usage, update firmware, or reboot it. If the router connection is fine but specific devices are slow on Wi-Fi, the Wi-Fi link is the issue — move closer to the router, change channels, or check for interference. If only one device is slow regardless of connection type, the problem is that device — check its network settings, disable VPNs, flush the DNS cache, or update the network driver.
Frequently Asked Questions
What if my modem and router are combined into one device?
Many ISPs provide a gateway device that combines the modem and router into a single unit. You can still perform a partial bypass test by enabling the gateway's “bridge mode” or “DMZ mode,” which passes the public IP directly to a connected device. Alternatively, connect a laptop to one of the gateway's LAN Ethernet ports and run speed tests — this at least rules out Wi-Fi — and check the gateway's signal status page for the same metrics (downstream power, upstream power, SNR, event log) to assess line quality.
My direct modem connection is slower than expected, but the ISP says they see no problem on their end. What next?
ISP remote diagnostics sometimes look at different metrics than what you are experiencing. Request that a line technician physically inspect the signal level at the tap on the street (not just at the modem) and measure the signal on the drop cable between the tap and your home. Also request that they check correctable and uncorrectable error counts at the head-end for your modem's MAC address — these logs often reveal intermittent line problems that are invisible to a brief remote diagnostic.
Does the time of day affect the ISP vs home network test?
Yes, significantly. ISP congestion is time-dependent — a connection that performs fine at 3 AM may be heavily throttled by node congestion at 8 PM. Run the bypass test during the exact time window when you experience problems. A direct modem connection that shows 480 Mbps at noon and 80 Mbps at 8 PM on a 500 Mbps plan is clear evidence of ISP-side peak-hour congestion — your home network is irrelevant because the same problem appears whether the router is in the path or not.