Overall
61.1
/ 100
Scores
0–100 vs comparable servers
Ping
100.0/100
Speed
74.0/100
CPU
12.8/100
Memory
32.7/100
Disk
68.0/100
Category scores
Internet speed
Ping to control points
CPU performance
Memory bandwidth
Disk — random IOPS
Disk — sequential throughput
Disk latency (p95 / p99)
Network
| download_speed | 1,596 | Mbps |
| upload_speed | 1,078.5 | Mbps |
| ping_cloudflare | 0.933 | ms |
| ping_google | 3.883 | ms |
| ping_quad9 | 2.138 | ms |
| mtu | 1,500 |
Disk
| random_4k_read_iops | 68,994 | IOPS |
| random_4k_read_bw | 269.5 | MB/s |
| random_4k_read_lat_p95 | 0.782 | ms |
| random_4k_read_lat_p99 | 1.09 | ms |
| random_4k_write_iops | 43,478 | IOPS |
| random_4k_write_bw | 169.8 | MB/s |
| random_4k_write_lat_p95 | 1.204 | ms |
| random_4k_write_lat_p99 | 1.565 | ms |
| sequential_1m_read_iops | 6,570 | IOPS |
| sequential_1m_read_bw | 6,570.2 | MB/s |
| sequential_1m_read_lat_p95 | 1.483 | ms |
| sequential_1m_read_lat_p99 | 1.696 | ms |
| sequential_1m_write_iops | 6,140 | IOPS |
| sequential_1m_write_bw | 6,139.9 | MB/s |
| sequential_1m_write_lat_p95 | 1.679 | ms |
| sequential_1m_write_lat_p99 | 2.114 | ms |
CPU
| sysbench_single | 302.04 | events/s |
| sysbench_multi | 283.92 | events/s |
| gzip_compress | 149.6 | MB/s |
Memory
| memory_write_mb_s | 14,514.27 | MiB/s |
| memory_read_mb_s | 16,990.83 | MiB/s |
| OS | AlmaLinux 10.1 (Heliotrope Lion) |
| Kernel | 6.12.0-124.55.1.el10_1.x86_64 |
| Virtualization | kvm |
| CPU model | Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz |
| vCPU | 1 |
| RAM (MB) | 954 |
| Disk (GB) | 9.93 |
| Agent | 1.1.0 |
| 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 →
Loading…
Could not load the data.
Plain-language summary
ITLDC (1 vCPU · 1 GB RAM) was measured in Dusseldorf, Germany — the real numbers are below. The best result comes from the network path, at 90/100 (ping 0.9 ms, download 1,596 Mbps). If anything holds it back, it is CPU (284 events/s). 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. As always, the numbers reflect this exact instance on the test date and may vary by node.