Verified
14 July 2026
Digitalocean·1 vCPU · 1 GB RAM·Germany
Overall
56.4
/ 100
Scores
0–100 vs comparable servers
Ping
100.0/100
Speed
77.4/100
CPU
15.5/100
Memory
31.2/100
Disk
41.4/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,691.9 | Mbps |
| upload_speed | 601.8 | Mbps |
| ping_cloudflare | 1.021 | ms |
| ping_google | 0.735 | ms |
| ping_quad9 | 0.548 | ms |
| mtu | 1,500 |
Disk
| random_4k_read_iops | 41,475 | IOPS |
| random_4k_read_bw | 162 | MB/s |
| random_4k_read_lat_p95 | 1.45 | ms |
| random_4k_read_lat_p99 | 2.966 | ms |
| random_4k_write_iops | 32,265 | IOPS |
| random_4k_write_bw | 126 | MB/s |
| random_4k_write_lat_p95 | 1.81 | ms |
| random_4k_write_lat_p99 | 3.654 | ms |
| sequential_1m_read_iops | 1,995 | IOPS |
| sequential_1m_read_bw | 1,994.5 | MB/s |
| sequential_1m_read_lat_p95 | 5.734 | ms |
| sequential_1m_read_lat_p99 | 8.454 | ms |
| sequential_1m_write_iops | 1,274 | IOPS |
| sequential_1m_write_bw | 1,273.8 | MB/s |
| sequential_1m_write_lat_p95 | 11.469 | ms |
| sequential_1m_write_lat_p99 | 19.53 | ms |
CPU
| sysbench_single | 340.72 | events/s |
| sysbench_multi | 337.57 | events/s |
| gzip_compress | 153.2 | MB/s |
Memory
| memory_write_mb_s | 12,429.28 | MiB/s |
| memory_read_mb_s | 18,153.77 | 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
We put Digitalocean 1 vCPU · 1 GB RAM (in Germany) through the same tests as every other server on 14 July 2026. Where it shines is the network path: ping 0.5 ms, download 1,692 Mbps, for a score of 91 out of 100. The weaker spot is compute (338 events/s), so demanding compute workloads are not its best fit. For a VPN, tunnel or proxy this is a strong choice — those workloads live on the network, not the processor. Compare it with other providers in the same country to find your best fit.