Network
| download_speed | 439 | Mbps |
| mtu | 1,500 | |
| ping_cloudflare | 7.072 | ms |
| ping_google | 6.857 | ms |
| ping_quad9 | 9.624 | ms |
| upload_speed | 418 | Mbps |
Disk
| random_4k_read_bw | 204.5 | MB/s |
| random_4k_read_iops | 52,352 | IOPS |
| random_4k_read_lat_p95 | 0.864 | ms |
| random_4k_read_lat_p99 | 1.597 | ms |
| random_4k_write_bw | 123.4 | MB/s |
| random_4k_write_iops | 31,592 | IOPS |
| random_4k_write_lat_p95 | 1.597 | ms |
| random_4k_write_lat_p99 | 2.408 | ms |
| sequential_1m_read_bw | 1,638.7 | MB/s |
| sequential_1m_read_iops | 1,639 | IOPS |
| sequential_1m_read_lat_p95 | 7.242 | ms |
| sequential_1m_read_lat_p99 | 9.372 | ms |
| sequential_1m_write_bw | 769.5 | MB/s |
| sequential_1m_write_iops | 769 | IOPS |
| sequential_1m_write_lat_p95 | 17.695 | ms |
| sequential_1m_write_lat_p99 | 25.821 | ms |
CPU
| gzip_compress | 120.2 | MB/s |
| sysbench_multi | 318.05 | events/s |
| sysbench_single | 327.45 | events/s |
Memory
| memory_read_mb_s | 16,803.66 | MiB/s |
| memory_write_mb_s | 13,042.34 | MiB/s |
| OS | Debian GNU/Linux 12 (bookworm) |
| Kernel | 6.1.0-49-amd64 |
| Virtualization | kvm |
| CPU model | Common KVM processor |
| vCPU | 1 |
| RAM (MB) | 960 |
| Disk (GB) | 9.64 |
| Agent | 1.1.1 |
| Scoring | 2026.07b |
Exactly what the agent returned from this server — before rounding, with nothing edited out. Every number above is computed from this. Open separately →
We tested a 1 vCPU · 1 GB RAM server at ITLDC in Latvia end to end on 31 July 2026. the network path is the strong side of this server (50/100, ping 6.9 ms, download 439 Mbps). the processor is the soft side here — 318 events/s — worth keeping in mind. That makes it a good pick for VPN and proxy nodes, where low latency and clean the network path matter far more than raw CPU. See the charts and full log above for every measured value.