Download test files
Files are generated from memory and served over a dedicated 100 Gbit/s unshared uplink in Amsterdam. Choose a size that matches your test duration.
Useful for verifying reachability and HTTPS handshake.
Good for quick checks without caching side-effects.
A reasonable size for interactive tests and quick comparisons.
Useful to understand per-flow performance and TCP tuning impacts.
Recommended for long-run tests to identify congestion and shaping.
Intended for engineering validation. Please use responsibly.
Recommended methodology
- Use wired connectivity and avoid VPNs during tests.
- Test multiple times of day to identify congestion.
- Compare single-flow vs multi-flow performance.
- Validate both IPv4 and IPv6 when available.
What you can measure
- Throughput (Gbps) and sustained delivery over time.
- TCP behavior (congestion control, BDP effects).
- Route quality to Amsterdam (loss, latency, jitter).
- Impact of peering vs transit paths.
Fair use
- This is a public resource; keep tests reasonable.
- Avoid long-running single-host saturation.
- Excessive usage may be rate-limited.
- For structured testing, contact our NOC.
CLI examples
Repeatable throughput testing to Amsterdam. Use single-stream for per-flow behavior, or parallel streams to approach line rate where RTT/BDP is a factor.
Single stream
curl -o /dev/null https://speedtest.ipvolume.net/10GB.binwget -O /dev/null https://speedtest.ipvolume.net/10GB.binBest for shaping detection and per-flow throughput comparisons.
Parallel streams
seq 1 8 | xargs -n1 -P8 -I{} curl -o /dev/null https://speedtest.ipvolume.net/1GB.bin# Validate headers / size
curl -I https://speedtest.ipvolume.net/1GB.binUse with care on public networks. Parallelism helps approach line rate when single-flow is RTT-limited.
About this node
A dedicated, unshared 100 Gbit/s test endpoint in Amsterdam for reproducible measurements.