Technical Methodology Statement¶
For Ombudsman & Formal Complaints
This statement ensures your evidence is treated with the same weight as an engineer's report. Include it as a preface to any evidence pack submitted to the ISP, Ombudsman, or Ofcom.
Testing Environment & Integrity¶
All performance data was captured using a dedicated monitoring service (isp-monitor) running on a hardwired Linux environment connected via Category 6 Ethernet directly to the LAN1 port of the Trooli-supplied Technicolor router. To ensure a "clean-room" diagnostic environment, all tests were performed while the primary network gateway was isolated or verified idle.
Data Acquisition & Verification¶
Primary Metric (Contractual)¶
Automated throughput tests were conducted using the official Ookla Speedtest CLI (v1.2+), specifically targeting the Trooli Maidstone server (ID: 35143) to eliminate third-party routing variables and browser-based CPU overhead.
Secondary Verification (Real-World)¶
To verify network peering capacity beyond prioritized test nodes, a back-to-back 1GB throughput test was performed against the Cloudflare CDN, measuring sustained real-world transfer speeds.
Local Traffic Control¶
Simultaneous with each test, WAN utilization metrics were polled directly from the UniFi Cloud Gateway Ultra API. This confirms that total household throughput (RX/TX) was negligible during the test windows, ensuring the recorded breaches represent the total available capacity of the Trooli network at the ONT.
How to Use This Statement¶
-
As a Preface: Put this at the very beginning of any PDF or email where you share your "Daily Summary" or "Breach Log."
-
The "Expert" Effect: By mentioning CLI (Command Line Interface) and CDN (Content Delivery Network), you move your complaint out of the "General Support" pile and into the "High-Level Technical" pile. Support agents are much less likely to send you a generic "reboot your router" script if they see this.
Evidence Position Summary¶
| Component | Status | Notes |
|---|---|---|
| Hardware | ✅ Bulletproof | Technicolor router (ISP-supplied), Cat6 hardwired |
| Logic | ✅ Verification Pair | Ookla (contractual) + Cloudflare (real-world) |
| Audit | ✅ WAN Stats | Internal traffic logged, backfilled from UniFi API |
| False Positive Filter | ✅ Active | Self-caused breaches flagged and filterable |
Technical Specifications¶
| Parameter | Value |
|---|---|
| Monitoring Host | CT1118 (LXC on Proxmox px3-suzuka) |
| OS | Debian 12 (Bookworm) |
| Connection | 10.44.1.118 → Cat6 → Technicolor LAN1 |
| Speedtest Tool | Ookla Speedtest CLI v1.2+ |
| Target Server | Trooli Maidstone (ID: 35143) |
| Secondary Test | Cloudflare CDN 1GB download |
| WAN Metrics Source | UniFi Cloud Gateway Ultra API |
| Data Storage | SQLite (/opt/isp-monitor/data/isp_evidence.db) |
Test Schedule¶
| Time Window | Test Type | Purpose |
|---|---|---|
| 05:00-06:00 | Control | Off-peak baseline (lowest contention) |
| 07:00-24:00 | Peak | Every 30 minutes during peak hours |
| 00:00-07:00 | Off-peak | Every 60 minutes |
Each test includes:
- Ookla speedtest (download, upload, latency, jitter)
- Cloudflare TBB 1GB download (sustained throughput)
- WAN utilization snapshot (internal traffic check)
Contractual Reference¶
| Metric | Declared | Guaranteed (Ofcom 90%) |
|---|---|---|
| Download | 900 Mbps | 810 Mbps |
| Upload | 900 Mbps | 810 Mbps |
Any test result below 810 Mbps on either metric constitutes a contract breach under Ofcom guidelines.
Why This Methodology Matters¶
This methodology preemptively addresses common ISP deflection tactics:
| ISP Excuse | Our Counter-Evidence |
|---|---|
| "It's your Wi-Fi" | Hardwired Cat6 direct to router |
| "It's your device" | Dedicated Linux server, CLI tools |
| "Other devices were using bandwidth" | WAN stats prove idle during tests |
| "Our test server shows good speeds" | We test against YOUR server (Trooli Maidstone) |
| "CDN peering isn't our responsibility" | Cloudflare test shows real-world capacity |
| "It was a one-off" | Timestamped logs over 30+ days |
Copyable Statement¶
Use this condensed version in emails or complaint forms:
TECHNICAL METHODOLOGY STATEMENT
All performance data was captured using a dedicated monitoring service
running on a hardwired Linux environment connected via Category 6 Ethernet
directly to the LAN1 port of the Trooli-supplied Technicolor router.
Tests conducted:
- Primary: Ookla Speedtest CLI targeting Trooli Maidstone server (ID: 35143)
- Secondary: Cloudflare CDN 1GB sustained download test
- Verification: WAN utilization metrics from UniFi Cloud Gateway Ultra API
This confirms total household throughput was negligible during test windows,
and recorded breaches represent the total available capacity of the Trooli
network at the ONT.
Related Documentation¶
- ISP Monitor Overview - Full service documentation
- Ofcom Broadband Speeds - Official guidance
Document Version: 1.0
Last Updated: 2026-02-02