To make an ISP contract complaint persuasive, connect three facts: what the provider promised, what actually happened, and the specific remedy you want. Save the agreement, plan disclosures, bills, test results, outage records, and written support contacts. One slow Wi-Fi test or an angry phone call usually won't establish a contract breach by itself.

The information below is for U.S. consumers. Contract terms, state procedures, and available remedies vary by provider, service type, and state.

Start with the documents that define the service

Collect the records that show what you bought and what you were charged:

An advertisement can help show what the provider represented. Whether it became part of an enforceable contract depends on the agreement and applicable law. An "up to" speed is generally a maximum claim, not a guaranteed minimum. A label's typical speed can show what the provider disclosed, but it isn't automatically a service-level guarantee.

The FCC's broadband label rules use a standardized point-of-sale disclosure for key plan information, including price, fees, data allowances, typical download and upload speeds, latency, and links to additional terms. A summary of the FCC broadband label rules can help you identify what to save. Keep the label that applied when you enrolled, not only the version displayed today.

Search the agreement for terms that could affect escalation:

These provisions don't necessarily invalidate a complaint, but they can determine where, when, and how you pursue it.

Evidence checklist for an ISP dispute

Create one folder for the account. Download original files before changing or canceling service, and keep a backup outside the provider's account portal.

Don't edit original evidence. If you crop a screenshot to highlight a charge or test result, keep the uncropped file too.

How to document slow internet speeds

There is no fixed number of tests that automatically proves a breach. A repeatable pattern from controlled tests is more useful than one unusually low result.

1. Test in a controlled setup

For the clearest evidence of the connection reaching your home:

  1. Connect a computer directly to the provider's modem or gateway with Ethernet.
  2. Turn off VPN software and pause large downloads, streaming, cloud backups, and game updates.
  3. Confirm that the computer's Ethernet port and cable can handle the speed you purchased.
  4. Record whether the test is wired or over Wi-Fi.
  5. Use the same device and test server when possible.

If you can only test over Wi-Fi, keep those results. They show the experience in your home, but interference, distance from the router, mesh placement, and device limits may give the provider another explanation.

For fixed wireless, mobile broadband, or home 5G, test from the same location and record signal information, weather, and the equipment being used. Ethernet may remove a Wi-Fi problem without removing limitations on the provider's wireless network.

2. Test across several days and times

A useful starting pattern is at least three wired tests on different days, including a busy evening period. Test when the service works normally and when it fails. Record:

The provider's own testing tool can be useful because it may show results recognized by the ISP. Also use a consistent independent test for comparison. Save the complete result page, not only the headline number.

3. Check whether the problem is inside your home

Compare a test from the same computer directly connected to the gateway with a test from your usual Wi-Fi location. A problem that appears only over Wi-Fi may involve the router, wireless signal, cable, or device rather than the provider's line.

You can also compare the connection to your local router with the connection to an outside test server. If the local connection is unstable, the issue may be inside the home. If the local connection is stable while outside service repeatedly fails, that supports an ISP-related complaint, although it still doesn't prove a contract violation.

Router pages may show useful information such as:

These records can establish when a problem occurred. They may require technical interpretation, so describe what the equipment reports without claiming that the log proves a particular cause.

Speed-test evidence table

Test setup What it helps show Main limitation
Wired connection to the provider gateway Performance reaching your home equipment The cable, computer, or gateway can still affect results
Normal Wi-Fi connection The service experience you receive in ordinary use Local interference and router placement may be responsible
Provider's testing tool Results recognized by the ISP The tool and test location may differ from independent tools
Independent speed test Corroboration of repeated performance Results vary by server and network conditions
Router or modem logs Timing of disconnects and line events Logs don't always identify the cause

How to document repeated outages

Use an outage log instead of relying on memory. For each incident, record:

Take screenshots of outage notices and account alerts because online status pages can change. Reports from neighbors or outage-monitoring websites may support the timing of a widespread problem, but they don't prove that your account was without service.

Ask the provider to confirm the outage dates, ticket number, and whether the account qualifies for a credit under its policy. Don't assume an outage automatically produces compensation. Eligibility may depend on the agreement, the type of outage, notice requirements, and the length of the interruption.

If you need to restart the modem, save logs first because a restart may erase useful information. Note every restart and why you made it.

Evidence for billing errors and cancellation problems

Billing disputes are easiest to explain as a before-and-after comparison. Place the relevant bills next to the agreement and mark each difference.

Check for:

A higher bill isn't automatically an error if a disclosed promotion ended or a separately listed fee applied. Identify the exact charge, the document that contradicts it, and the correction you want.

For a cancellation dispute, save the date and method of the request, the representative's confirmation, the account status, and equipment-return tracking. If you moved or switched providers, preserve the final bill from both accounts.

Keep the payment method separate from the contract issue. A credit-card billing dispute, a debit or ACH payment problem, and a request for an ISP refund follow different procedures and may have different deadlines. If you believe a payment is a billing error, contact the issuer promptly and ask which process applies. Don't assume that disputing a payment cancels the service agreement or prevents late fees.

Turn support contacts into a usable timeline

A short chronology can be more persuasive than a large collection of screenshots. Include the provider's promises as well as the problems.

Date or time Problem or promise Your action Provider response Evidence
[date and time] Speeds repeatedly fell below the relevant plan disclosure Ran wired and Wi-Fi tests No outage listed or no explanation provided Test log and screenshots
[date] Reported the problem Opened a support ticket Troubleshooting or escalation requested Chat transcript and ticket number
[date] Problem continued Sent a written request for repair or credit Provider promised action or denied the request Email or secure message
[date] Bill included a disputed charge Requested a correction Credit issued, denied, or still pending Bill and written response

After a phone call, send a short email or secure message:

On [date], I spoke with [name] about account [number]. I understood that you would [specific action] by [date]. Please correct me if that summary is inaccurate.

This creates a contemporaneous record of what you understood. It doesn't automatically change the written contract.

Recording telephone calls may be restricted by state law. Ask for permission or use a written summary instead of secretly recording a conversation.

Write a focused demand for a fix or refund

Give the ISP a clear opportunity to respond before filing with a regulator, unless the circumstances make that impractical. Use a channel that creates a record, such as the provider's secure message system, email, or tracked mail. For a routine dispute, you can request a written response within 10 to 14 days. That request isn't automatically a legal deadline; follow any notice or cure period in the agreement.

Ask for a specific remedy in dollars or concrete actions. Depending on the records, you might request:

Don't assume that an early termination fee disappears because service was poor. Identify the contract term or policy supporting your request.

Sample ISP complaint letter

Subject: Account [number] - request to correct service and billing

I subscribe to [plan name] at [service address]. My order confirmation dated [date] lists [advertised speed and monthly price]. The applicable agreement or label is attached.

Between [date] and [date], I recorded [number] tests using [wired or Wi-Fi] equipment. The results are summarized in the attached log. I also experienced outages on [dates], as shown by the attached router records and support tickets.

I contacted your company on [dates]. The relevant case numbers are [numbers], but the service problem or billing error remains unresolved.

Please:
1. [Investigate and correct the service problem];
2. [Issue a credit or refund of $amount for the identified period or charge]; and
3. [Confirm the correct monthly rate, cancellation status, or equipment balance].

Please provide a written response by [date]. If you deny the request, identify the agreement term or account record on which you rely.

Name:
Service address:
Account number:
Email and phone:

Attach a short evidence index. Start with the agreement, representative test or outage records, relevant bills, and support history. Don't send every file in the first message; identify the strongest records and offer additional material if needed.

Escalate to the right complaint channel

FCC

The FCC Consumer Complaints Center is the federal route for many telecommunications and broadband service complaints. Use it after giving the provider a fair chance to address the issue when possible. Explain the problem with dates, documents, and a specific remedy instead of general accusations.

Include:

When the FCC forwards an informal complaint to the provider, the provider commonly has about 30 days to respond. That is a response period, not a guaranteed repair, refund, or finding that the provider breached the contract. An FCC complaint also isn't a substitute for arbitration or a court case, and you shouldn't assume it will award damages.

Save the FCC confirmation and case number. If the provider replies, compare its explanation with the contract and evidence rather than treating the response as the final word.

FTC

Use the FTC's instructions for reporting fraud and bad business practices when the issue involves suspected deceptive advertising, misleading pricing, or a scam. The FTC's consumer advice resources provide broader information about fraud and consumer-protection issues.

An FTC report is primarily an enforcement and information-gathering channel. It isn't a private case manager and doesn't guarantee that the provider will refund you. Describe the representation accurately, retain supporting material, and avoid calling conduct fraud unless the facts support that description.

State agencies

Your state attorney general may accept complaints about unfair or deceptive business practices. A public utility commission or public service commission may also handle some provider complaints, but its authority differs by state and by type of internet service.

Check the relevant official state website for:

State agencies generally don't act as your private attorney. A complaint may help resolve an account issue or identify a pattern, but it doesn't guarantee compensation.

Arbitration, small claims, or a regular lawsuit

If the provider won't resolve the matter, read the dispute-resolution section before filing anything. Look for:

If arbitration is required, filing in court first may lead the provider to ask the court to compel arbitration. That doesn't mean the clause is always enforceable. It means the agreement should be reviewed before you choose a forum.

Small claims court can be practical when the amount is within your state's limit and the dispute is easy to explain. Rules, fees, service requirements, and limits differ by state. Check the court's official instructions and use the provider's legal name and service information rather than only the brand name on the bill.

Bring the agreement, evidence index, timeline, bills, and proof that you asked the provider to fix the problem. A larger claim, or a dispute involving privacy harm, discrimination, significant losses, or complicated contract terms, may justify speaking with a licensed attorney or legal-aid organization.

A class action isn't an automatic shortcut, especially when the agreement contains a class waiver. A regulatory complaint also may not pause a court or arbitration filing deadline, so check the agreement and applicable state law before waiting.

Build an evidence packet

Whether you're sending a final demand or preparing for a formal claim, organize the material in this order:

  1. One-page summary: The plan, problem, dates, and requested remedy.
  2. Contract documents: Agreement, order confirmation, label, and promotional terms.
  3. Performance records: Speed-test log and representative screenshots.
  4. Outage records: Router logs, provider notices, and support tickets.
  5. Billing records: Relevant invoices with disputed lines marked.
  6. Communications: Emails, chats, call summaries, and written responses.
  7. Loss records: Receipts or other proof of a specific financial loss.
  8. Remedy calculation: The exact refund, credit, or fee reversal requested.

Use consistent file names such as YYYY-MM-DD-wired-speed-test.png or YYYY-MM-bill-disputed-fee.pdf. Keep a backup outside the provider's portal.

Common mistakes that weaken an ISP complaint

Frequently asked questions

Can one speed test prove that my ISP breached its contract?

Usually not. One test may show a problem, but the provider can point to Wi-Fi interference, equipment limits, a busy test server, or a temporary outage. Repeated controlled tests on different days, especially over Ethernet, make the evidence stronger.

Should I test over Wi-Fi or Ethernet?

Do both if possible. Wi-Fi tests show the service you experience during normal use. Ethernet tests are generally better for isolating the connection between your device and the provider's gateway. Label each result so a Wi-Fi limitation isn't mistaken for a line-speed measurement.

What if my plan says "up to" a certain speed?

An "up to" statement generally describes a maximum rather than a guaranteed minimum. Save the full label and agreement to see whether typical performance, a minimum, latency, or another service commitment is also disclosed. Repeated shortfalls or misleading sales statements may support a complaint, but the outcome depends on the documents and applicable law.

Can the FCC or FTC force my ISP to issue a refund?

Don't assume so. An FCC complaint may prompt a provider response, while an FTC report may help with enforcement against deceptive conduct. Neither route is a guaranteed substitute for the refund process in your agreement, arbitration, or court.

What should I do first?

Download your agreement and recent bills, save the provider's plan label, and start a dated log. Run controlled tests before restarting or replacing equipment. Then send a written request that identifies the problem, supporting evidence, and specific remedy.