PROTOCOL RACE · PERFORMANCE THROUGH TIME
See how the measured lead changes.
Keep one test source, choose a time window and compare the observed provider × protocol series. Read the samples and destination coverage before interpreting a change in order.
YOUR NEXT STEP
A shared source is the start
The race does not force every series onto identical exit destinations. It shows historical observations, not a universal provider ranking.
EXPLORE THE SERIES
Set the conditions, then read the chart
Choose retention for baseline-relative throughput, Mbps for raw download speed, or latency and loss for other aspects of the connection.
Observed performance through time
Each line describes one measured provider and protocol setup.
Latest time bucket
| # | Provider | Protocol | Metric | P10–P90 retention | Destinations | Samples | Confidence |
|---|---|---|---|---|---|---|---|
| Loading measured results… | |||||||
INTERPRET THE MOVEMENT
What changed—and what else changed?
Check the samples
A point with few measurements deserves more caution than one supported by repeated observations.
Check the exit coverage
A changing destination mix can move the median. Compare the coverage beside each series.
Choose an appropriate bucket
Daily or weekly views help reveal broader patterns. Finer buckets can expose short-lived changes but may have fewer samples.
KEEP THE RIGHT COMPARISON
Use a balanced view for a headline choice
The race is useful for inspecting observed history. When you need a destination-balanced comparison, move to rankings and read its coverage and method.
