Reading a report

vps.gripe archives the full output of VPS benchmark scripts. Each report has two parts: the raw output the script printed, and the key numbers taken from it.

What a report page shows

  • Title: provider, plan and script, confirmed by the submitter.
  • Raw output: everything the script printed, with only IP addresses, hostnames and similar personal details hidden.
  • Summary: numbers taken from the raw output. L42 next to a number means it comes from line 42; click it to see that line.
  • Tested: the time the script printed. Submitted: when it was published here. Both are in UTC.

Supported scripts

ScriptWhat it measures
YABSCPU score (Geekbench), disk I/O (fio), bandwidth to public test servers (iperf3)
bench.shSystem info, sequential disk writes (dd), speed to test nodes (Speedtest)
HardwareQualityCPU, memory and disk scores, and an overall score derived from them
IPQualityWho the IP belongs to, how databases classify and rate it, which streaming and AI services work, mail port and blocklists
NetQualityRouting registry data, latency between the server and Chinese provinces, return routes on the three carriers, international and China speed tests
NodeQualityRuns the hardware, IP quality and network quality tests in one go

ECS, nws.sh, TcpQuality and other text can be published, but show the raw output only, without a summary.

Reading the numbers

  • A report is one test at one moment. Results for the same machine change with neighbours’ load, busy test servers and time of day, so look at several reports for the same plan.
  • Compare scores only within the same script and version: Geekbench 5 and 6 scores aren’t comparable, and neither are fio and dd disk results.
  • The question mark next to each section title explains what it measures and whether higher or lower is better.

Can I trust a report?

  • Reports are submitted anonymously and this site doesn’t check them; the output may have been edited.
  • The script version, test time and Geekbench result link in the output help you judge: the Geekbench link points to the result stored on Geekbench’s own site, where you can check the scores.
  • If you find a faked result or someone’s personal data, use “Flag” on the report page.