Serva One·2 vCPU · 2 GB RAM·United States
Network
| download_speed | 109 | Mbps |
| upload_speed | 129.5 | Mbps |
| ping_cloudflare | 2.042 | ms |
| ping_google | 1.495 | ms |
| ping_quad9 | 2.024 | ms |
| mtu | 1,500 |
Disk
| sequential_1m_read_iops | 2,453 | IOPS |
| sequential_1m_read_bw | 2,452.6 | MB/s |
| sequential_1m_read_lat_p95 | 3.654 | ms |
| sequential_1m_read_lat_p99 | 4.62 | ms |
CPU
| sysbench_single | 307.1 | events/s |
| sysbench_multi | 624.59 | events/s |
| gzip_compress | 265.3 | MB/s |
Memory
| memory_write_mb_s | 10,944.09 | MiB/s |
| memory_read_mb_s | 17,340.37 | MiB/s |
| OS | Ubuntu 26.04 LTS |
| Kernel | 7.0.0-22-generic |
| Virtualization | kvm |
| CPU model | QEMU Virtual CPU version 2.5+ |
| vCPU | 2 |
| RAM (MB) | 1962 |
| Disk (GB) | 14.67 |
| 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 →
On 13 July 2026 we ran the full test suite on Serva One (2 vCPU · 2 GB RAM) in United States. Performance leans hardest on the network path — ping 1.5 ms, download 109 Mbps, 59/100. On the other hand, CPU lags behind (625 events/s). That makes it a good pick for VPN and proxy nodes, where low latency and clean connectivity matter far more than raw CPU. The full breakdown, with every metric, is in the tabs above.