Verified
13 July 2026
Digitalocean·1 vCPU · 1 GB RAM·Netherlands
Overall
50.0
/ 100
Scores
0–100 vs comparable servers
Ping
100.0/100
Speed
54.5/100
CPU
13.2/100
Memory
31.2/100
Disk
38.3/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,068 | Mbps |
| upload_speed | 473.5 | Mbps |
| ping_cloudflare | 0.867 | ms |
| ping_google | 0.476 | ms |
| ping_quad9 | 0.998 | ms |
| mtu | 1,500 |
Disk
| random_4k_read_iops | 43,420 | IOPS |
| random_4k_read_bw | 169.6 | MB/s |
| random_4k_read_lat_p95 | 1.45 | ms |
| random_4k_read_lat_p99 | 2.056 | ms |
| random_4k_write_iops | 27,752 | IOPS |
| random_4k_write_bw | 108.4 | MB/s |
| random_4k_write_lat_p95 | 2.212 | ms |
| random_4k_write_lat_p99 | 4.489 | ms |
| sequential_1m_read_iops | 2,175 | IOPS |
| sequential_1m_read_bw | 2,174.7 | MB/s |
| sequential_1m_read_lat_p95 | 5.276 | ms |
| sequential_1m_read_lat_p99 | 6.98 | ms |
| sequential_1m_write_iops | 691 | IOPS |
| sequential_1m_write_bw | 691 | MB/s |
| sequential_1m_write_lat_p95 | 21.627 | ms |
| sequential_1m_write_lat_p99 | 28.443 | ms |
CPU
| sysbench_single | 350.95 | events/s |
| sysbench_multi | 344.61 | events/s |
| gzip_compress | 110 | MB/s |
Memory
| memory_write_mb_s | 13,946.22 | MiB/s |
| memory_read_mb_s | 16,629.76 | MiB/s |
| OS | Ubuntu 24.04.4 LTS |
| Kernel | 6.8.0-124-generic |
| Virtualization | kvm |
| CPU model | DO-Regular |
| vCPU | 1 |
| RAM (MB) | 961 |
| Disk (GB) | 23.17 |
| 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
A hands-on test of Digitalocean 1 vCPU · 1 GB RAM running in Amsterdam, Netherlands. Where it shines is the network path: ping 0.5 ms, download 1,068 Mbps, for a score of 82 out of 100. The weaker spot is compute (345 events/s), so demanding compute workloads are not its best fit. That makes it a good pick for VPN and proxy nodes, where low latency and clean connectivity matter far more than raw CPU. As always, the numbers reflect this exact instance on the test date and may vary by node.