The Decision: Your Equipment vs the ISP's Network
The most important question before calling your ISP is: have you eliminated your own equipment as the cause? ISPs routinely send technicians to homes where the problem is the customer's router, a bad Ethernet cable, or Wi-Fi interference — and they are allowed to charge for those visits. Ruling out your equipment first is both financially and diagnostically important. The checklist below separates what you can fix from what you genuinely need to escalate.
Do These First — Before Calling
| Check | How to Do It | What It Rules Out |
|---|---|---|
| Test on Ethernet, not Wi-Fi | Connect laptop directly to router with a cable; run a speed test | Eliminates Wi-Fi as the cause |
| Test with router bypassed | Connect laptop directly to modem; power cycle modem; run a speed test | Eliminates your router as the cause |
| Check modem signal levels | Visit 192.168.100.1 and check downstream power, upstream power, SNR, uncorrected errors | Shows whether the physical line has measurable problems |
| Check the modem event log | 192.168.100.1 → Event Log; look for T3/T4 timeouts | T3/T4 timeouts confirm upstream line issues that are usually ISP territory |
| Run MTR to 1.1.1.1 | mtr --report -c 100 1.1.1.1 on a wired connection | Shows where packet loss begins on the path; if it starts at your ISP's first hop, that is their problem |
| Check the ISP's outage page | Most ISPs have a status page or outage map; check before calling | Avoids calling during a known outage you cannot fix by reporting |
Clear Signs You Should Escalate to the ISP
These findings, verified on a wired Ethernet connection directly to the modem, point unambiguously to the ISP's side of the demarcation point:
- Speed tests on direct modem connection are significantly below your subscribed plan — below 80% of plan speed consistently, across multiple test servers, at off-peak hours.
- Packet loss appears in MTR at the first hop after your modem — this is your ISP's first router, and loss here is clearly on their network.
- T3 or T4 timeouts in the modem event log, recurring over multiple days, indicate upstream channel instability that the ISP must investigate at the tap, node, or head-end.
- Upstream transmit power is above 51 dBmV on a DOCSIS modem — the modem is working too hard to reach the ISP's head-end, indicating line problems in the outside plant.
- Fiber ONT shows a LOS (Loss of Signal) alarm, or Rx power has dropped below -27 dBm — this is always an ISP infrastructure issue.
- The problem is reproducibly time-of-day specific — always bad from 6–9 PM, fine at 3 AM — and your direct modem connection shows the same degradation. This is neighborhood node congestion, which is the ISP's capacity management problem.
What to Say When You Call
ISP support scripts follow a flowchart. Getting past the first-level script requires giving them data that the script cannot handle. Lead with your evidence, not your complaint:
- ”I have tested on a wired Ethernet connection directly to the modem, bypassing my router.” — This immediately bypasses the first 15 minutes of Wi-Fi troubleshooting.
- ”I am getting [X] Mbps on a [plan speed] plan on a direct modem connection.” — This establishes the problem is not in your home equipment.
- ”My MTR report shows [X]% packet loss at your first router, hop 2, at IP [address].” — This tells their engineer exactly where to look.
- ”My modem event log shows T3 timeouts occurring every [frequency], most recently at [time].” — T3/T4 timeouts trigger a different support path than a generic slow speed complaint.
- ”My modem's upstream transmit power is [X] dBmV, which is above the normal 48 dBmV range.” — This prompts a line technician rather than a software fix attempt.
Ask specifically for a line technician who will check the signal level at the tap and the drop cable, not just inside your home. Document the ticket number, the agent's name, and what they committed to. If a technician visit is promised within 48 hours but the problem is affecting work or medical equipment, say so explicitly — most ISPs have escalation paths for business-critical situations.
Frequently Asked Questions
Will the ISP charge me for a technician if the problem is on their side?
Generally not if the problem is definitively on their side of the demarcation point. If the technician determines the problem is in your home wiring, your router, or your own equipment, many ISPs do charge a service call fee ($50–100 is common). This is why ruling out your equipment before calling matters. A clear modem signal problem or an MTR report showing loss at the ISP's first hop makes it very difficult for the ISP to argue the problem is inside your home.
What if the ISP says the problem is intermittent and they cannot reproduce it?
Run PingPlotter continuously for 1–2 weeks, saving graphs that show the problem recurring at specific times. Email the ISP's support ticket with the graphs attached and timestamps clearly visible. Ask specifically that the ticket be escalated to their network operations team rather than being closed as “unable to reproduce.” If the problem recurs after three service calls that find nothing, request escalation to their regional network engineer — most ISPs have a high-impact customer escalation path for persistent issues.
How long should I wait before escalating after calling?
If a technician visit was promised but the problem continues, follow up within 48 hours if you have not heard back. If the problem is intermittent and they dispatched someone who found nothing, give the fix a full week before calling again — some line repairs (corrosion cleanup, tap adjustments) take a few days to stabilize. If the problem continues unchanged after 7 days following a repair visit, call back and reference your previous ticket number.
Is there a better path than calling customer support?
Yes. For technical issues with evidence, most major ISPs have an executive customer relations team or a network support escalation path that bypasses the standard script. You can often reach better support by emailing the ISP's executive team with your documented evidence, or by filing an FCC complaint (fcc.gov/consumers/guides/filing-informal-complaint) — ISPs respond much faster to FCC complaints than to standard support tickets, and the complaint prompts a formal response within 30 days. State PUC complaints are another option for regulated telecommunications services.