How to Prove Your ISP is Unreliable (Step-by-Step)

Calling your ISP to complain about frequent outages is an exercise in frustration when you have no hard evidence. Support agents are trained to run basic diagnostics, schedule a technician visit, and move on — without ever acknowledging a systemic reliability problem. If you want to escalate effectively, request a service credit, or file a complaint with a regulatory body, you need timestamped data that documents exactly when your connection failed, for how long, and how often. This guide walks you through building that case from scratch.

Step 1 — Start Continuous Monitoring

The foundation of any ISP complaint is a reliable log of connection events over time. A single screenshot of a failed speed test proves nothing. What you need is a continuous record showing the pattern of failures — their frequency, duration, and timing relative to each other.

Open Monitor My Connection in a browser tab, click Start Monitoring, and leave it running. The tool checks your connection every second using DNS-over-HTTPS and logs every status change — connected, slow, and disconnected events all get timestamped and stored in your browser's local storage. For a meaningful record, run it for at least 24 consecutive hours; a full week gives you enough data to identify patterns that your ISP cannot easily dismiss. See our complete guide on how to set up 24/7 monitoring for tips on keeping the tab active and preserving your data across browser restarts.

Step 2 — Document the Pattern

After collecting at least 24 hours of data, open the MMC dashboard and study the chart. You're looking for patterns rather than isolated incidents. The most common patterns that indicate an ISP problem rather than a local equipment issue are:

Time-of-day clustering: Outages or severe latency spikes that reliably occur during peak hours (typically 7pm–11pm) suggest network congestion at your ISP's infrastructure level — a sign they've oversold capacity in your neighborhood.

Daily regularity: If your connection drops at approximately the same time each day, this is unlikely to be random hardware failure and more likely to be a scheduled process, a congestion window, or a recurring network event your ISP can identify once forced to look.

Duration and frequency: Note the average duration of each outage event and how many occur per day. If your ISP promises 99.9% uptime, that allows only about 43 minutes of downtime per month. Even modest-seeming daily drops of 10–15 minutes each add up to hours beyond that threshold quickly.

Step 3 — Rule Out Local Issues

Before contacting your ISP, eliminate any local causes that their support team will point to first. This step is important for two reasons: it ensures your complaint is valid, and it preempts the deflection tactics that are standard in ISP support scripts.

Test your connection over ethernet rather than WiFi. WiFi introduces its own interference, channel congestion, and distance-related degradation that can mimic ISP reliability problems perfectly. Plug a laptop directly into your router or modem and run MMC from that device. If the outages disappear on ethernet, the problem is your WiFi setup, not your ISP. If they persist, you have strong evidence of an upstream problem.

Check whether all devices in your home are affected simultaneously during outage events. If one device drops while others stay connected, it's a local device issue. If everything goes down at once, the failure is at or above your router. Restart your modem (not just your router) by unplugging it for 30 seconds, letting it fully reconnect, and then resuming monitoring. If outages continue after a clean modem restart, the issue is upstream from your premises. For a detailed walkthrough of the diagnostic process, see our WiFi vs ISP diagnosis guide.

Step 4 — Prepare Your Evidence

Once you have continuous monitoring data and have ruled out local causes, you're ready to build your formal evidence package. This doesn't need to be elaborate — a few screenshots and a simple summary of the numbers is more effective than a wall of text.

Take a screenshot of your MMC dashboard showing the full 24-hour chart with outage events visible as red bars. If you have multiple days of data, take screenshots for each day to show the pattern repeating. Note the specific dates and times of the worst outage events — you'll reference these when talking to your ISP.

Calculate your actual uptime percentage from the data. If your ISP's SLA promises 99.9% uptime and you're experiencing outages totaling 2 hours per day, that's roughly 91.7% uptime — a massive gap. Presenting your ISP with a specific number ("I measured 91.7% uptime this week against your 99.9% SLA") is far more compelling than "my internet keeps going out."

Step 5 — Contact Your ISP

When you contact your ISP, lead with your data rather than your frustration. State your account number, then describe the pattern you've documented: "Over the past seven days, I've recorded daily outages averaging 45 minutes each, clustered between 7pm and 9pm. My measured uptime is 95.6% against the 99.9% stated in my service agreement. I'm requesting a service credit and a network-level investigation."

If the support agent offers standard troubleshooting steps you've already completed, say so explicitly: "I've already tested on ethernet, confirmed the modem is functioning after a cold restart, and verified all devices in my home are affected simultaneously. This is not a local equipment issue."

Request a case number for every contact, and follow up in writing (email or chat transcript) so you have a record that the complaint was filed. If your ISP is unresponsive after two or three escalation attempts, you can file a complaint with the FCC in the United States at fcc.gov/consumers/guides/filing-informal-complaint, or with the equivalent telecommunications regulator in your country. Regulatory complaints, even informal ones, frequently trigger faster internal resolution than standard customer support escalations.