speed.pnq.show

Self-hosted multi-stream throughput & dual-line aggregation probe — client ↔ Cloudflare edge.

Egress IP
CF colo (PoP)
Country
Network (ASN)
HTTP
streams
seconds

Download — aggregate

0.0Mbps
peak 0.0 Mbps · 0 streams

Upload — aggregate

0.0Mbps
peak 0.0 Mbps · 0 streams
Latency (RTT)
— ms
Jitter
— ms

Per-stream throughput (live)

Idle. Pick streams + duration, then Start.
#Down MbpsDown MBUp MbpsUp MB
How to read this. A single stream caps at one WAN line (~300 Mbit); the aggregate across many parallel streams is what reveals dual-line balancing — if both 300-Mbit lines are being used, the aggregate can climb above a single line's ceiling.

This test measures client ↔ Cloudflare edge, not raw line capacity. On the RU-direct path Cloudflare is traffic-shaped, so a low number here may be the shaper, not your lines — run the test through your VPN exit (check the colo/IP above shows Poland/Turkey, not RU) for a clean read. For true per-line aggregation, correlate these numbers with the router's per-interface counters (eth3 and eth2.4): if both lines' RX/TX climb together during the download, aggregation is real.