About VelocityVerify

VelocityVerify started with a simple frustration: every ISP in the testing team's city was advertising gigabit service while real-world results consistently landed 30–40% below that. The problem wasn't the marketing — ISPs are legally permitted to advertise peak theoretical speeds. The problem was that no tool at the time measured the things that actually matter: loaded latency, bufferbloat, upload behaviour under stress. So we built one.

The platform went live in 2023 with a focus on accuracy over aesthetics. We measure download speed, upload speed, unloaded latency (ping), jitter, and — critically — latency under load, which produces the bufferbloat grade that most tools skip entirely. Every test is designed to reflect what your connection actually delivers, not what it can do for a single clean TCP stream to a specially prioritised server.

The Infrastructure

The speed test itself is a custom measurement engine running on independent edge infrastructure — not ISP-hosted nodes, which can produce inflated results when ISPs detect test traffic and give it priority. Our test probes compete for queue space with real traffic, which is how we catch bufferbloat that a clean test would miss.

Test results — excluding any personally identifiable information — are stored in a Supabase database and used to generate the aggregate statistics that power our ISP Performance Index. IP addresses are hashed before storage. We do not sell this data. We use it to write data-driven articles about real-world network performance, which is the only way to hold ISP marketing claims to account.

Why We Write

A fast speed test is useful for 30 seconds. A well-explained guide on fixing bufferbloat, or a data-driven analysis of peak-hour ISP degradation, is useful for years. The editorial side of VelocityVerify exists because the technical details of home networking are genuinely hard to find explained in plain language — and because ISP marketing has a strong incentive to keep them that way.

Everything we publish is based on real measurements, real hardware testing, and real experience in network operations. We do not accept sponsored content. We do not publish results we haven't personally verified.

Who We Are

• Younes Kirat, CCNA, CWNA — Director of Network Diagnostics. Spent a decade in Tier 3 NOC operations before transitioning to independent benchmarking. Responsible for the speed test engine, the bufferbloat measurement algorithm, and hardware review methodology.
• Sarah Jenkins — Lead Telecommunications Analyst. Covers ISP policy, consumer data rights, privacy infrastructure, and the regulatory context that shapes what ISPs can and cannot claim. Previously worked in telecom compliance.

Read our Editorial Policy for full details on how we test, how we handle corrections, and how our affiliate revenue works. See our Testing Methodology for the technical specifics of how measurements are taken.