LIMEHAWK - Managed IT
ISP Dispute: Automated Evidence — automation
dateOct 18, 2024
statusRESOLVED
Incident

Manufacturing client reported intermittent "internet slowdowns" affecting their ERP system. VoIP calls dropping. Cloud backups timing out. ISP sent a tech who ran one speedtest at 2 PM (showing normal speeds) and declared "your internal network equipment is the problem." Client was ready to replace $40K in switches.

The Blame Game
speedtest at 2:14 PM487 Mbps down / 52 Mbps up
conclusion"speeds are fine, not our problem"
recommendation"replace your switches"

Classic ISP move: run a single test during off-peak hours, declare victory, close ticket. But users were complaining about 8-10 AM and 1-3 PM slowdowns - exactly when production data was flowing. We needed continuous evidence.

Solution

Deploy automated Ookla speedtest across endpoints, run every 2 hours, sync results to RMM. Build irrefutable timeline of actual network performance.

Why Ookla CLI
same backendspeedtest.net servers ISPs trust
JSON outputstructured data for trending
result URLsshareable proof with timestamp
no browserruns headless via RMM

When disputing with ISPs, using their preferred tool (Ookla/speedtest.net) removes the "your testing tool is inaccurate" defense. Every test generates a unique URL they can verify independently.

The Evidence

After one week of automated testing (84 tests per endpoint):

6 AM - 7 AM491 Mbps — normal
8 AM - 10 AM47 Mbps — 90% degradation
10 AM - 1 PM483 Mbps — normal
1 PM - 3 PM52 Mbps — 89% degradation
3 PM - 11 PM489 Mbps — normal

Peak business hours showing consistent 90% speed reduction across ALL 47 endpoints simultaneously. Internal switches don't cause synchronized degradation across a site - that's upstream congestion.

Outcome
data points collected3,948 speedtests
ISP responseadmitted node congestion
resolutionbandwidth upgrade at same price
switches replacedzero ($40K saved)

Presented ISP with 168-page PDF of timestamped speedtest results. Their network engineer confirmed oversubscribed node. Client got 1 Gbps upgrade (from 500 Mbps contract) at same rate as "service credit." Still running automated tests monthly to ensure they don't backslide.

one speedtest proves nothing - trend data wins disputes
use ISP-trusted tools (Ookla) to remove "bad test" excuse
sync to RMM for historical records and easy reporting
correlate test times with user complaints for patterns
Get Help

Tired of ISP finger-pointing? We deploy automated network monitoring that builds the evidence you need to hold providers accountable.