Verify the city field

VPSSpy separates explicit Tokyo records from Japan records with no disclosed city. Examples here use the former instead of treating a nationwide starting price as a purchasable Tokyo configuration. One city can also contain multiple datacenters and transit arrangements. The location field is not network-measurement certification.

Check compatibility before capacity

Deployment images, build toolchains and commercial applications can restrict CPU architecture or operating-system versions. Two machines with equal vCPU and RAM counts are not automatically interchangeable. Confirm the architecture, storage type and required dependencies. Unpublished CPU exclusivity remains unknown rather than being inferred from a series name.

Make routing tests specific

Where a product advertises IIJ, SoftBank or another upstream, inspect the direction and ISP scope. Obtain a test IP for that series and observe the address family the application actually uses. A server calling an API in another region also needs an outbound-destination check; visitor-to-server probes do not answer that question.

Compare the intended lifetime cost

Shortlist on the Tokyo city page and review invoice periods, transfer, backups and renewals. Interactive work needs relevant working-hour observations; batch processing needs task-window and resource-policy checks. These examples include no deployed benchmarks, and a stock observation does not establish availability of every image or optional component.