Latitude.sh vm.medium benchmarks

8 shared vCPU, 32 GB RAM, 320 GB

[Shared CPU](https://rackcensus.com/vps-categories/shared-cpu-vps-benchmarks)

$128.00/mo

$0.35/hr

$255.50/mo at 730 hours

$1,075.00/yr

$89.58/mo effective, 30% less than monthly

[Visit Latitude.sh](https://rackcensus.com/go/latitude)

# Performance by location
[Every run of this plan](https://rackcensus.com/benchmarks?filter%5Bplan%5D=latitude-vm-medium&filter%5Bsort%5D=location)

Medians over the last 90 days. Multi per $ is the multi-core median divided by the current monthly price, USD only.

Price position

Cheaper than 72% of 25 similar plans

Same vCPU count and CPU type, 24 to 43 GB RAM, median $164

[Compare these side by side](https://rackcensus.com/vps-geekbench-scores?filter%5Bc%5D%5B%5D=o_3p47ox&filter%5Bc%5D%5B%5D=o_37snk7&filter%5Bc%5D%5B%5D=o_4isfbg)

| Location | Runs | GB7 single | GB7 multi | 4K IOPS | Price | Multi per $ | Last tested |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Frankfurt, Germany](https://rackcensus.com/locations/frankfurt-vps-benchmarks "Every provider in Frankfurt") Frankfurt | 1 | 1,588 | 8,337 | 26,529 | $128.00/mo | 65 | [Oct 5, 2026](https://rackcensus.com/benchmarks/xp9f3c-latitude-vm-medium-fra-benchmark) |
| [Tokyo, Japan](https://rackcensus.com/locations/tokyo-vps-benchmarks "Every provider in Tokyo") Tokyo | 1 | 1,529 | 7,956 | 24,920 | $128.00/mo | 62 | [Oct 5, 2026](https://rackcensus.com/benchmarks/2acgsl-latitude-vm-medium-tyo3-benchmark) |
| [Ashburn, United States](https://rackcensus.com/locations/ashburn-vps-benchmarks "Every provider in Ashburn") Ashburn | 1 | 1,461 | 7,844 | 29,192 | $128.00/mo | 61 | [Oct 3, 2026](https://rackcensus.com/benchmarks/q3180c-latitude-plan-mdeoapqe0wgbl-ash-benchmark) |

## Geekbench 7 single-core

Per location, medians over the last 90 days

Loading...

## Disk 4K mixed IOPS

Per location, medians over the last 90 days

Loading...

A location is highlighted only when it leads the next best by 5 percent or more. Smaller gaps are normal run-to-run variance.

Network results are not compared here. iperf3 targets are third-party servers, so distance to each target dominates the number.
