VPSGrid
Deploy a server

SITE 29 · TYO1 · Asia-Pacific · AS212345

VPS TokyoJapan

The gateway to East Asia.

Configure in Tokyo →All forty-one sites
Live since
2024
Median RTT
3ms
Edge capacity
0.54Tbit/s
from
€1.90/mo
Facility
TYO1 — Otemachi
Certification
Tier IV
Carriers
NTT · Arelion · IIJ
Peering
JPIX
Test IP
203.0.116.10
Stock
In stock

SITE DOSSIER · TYO1

Why Tokyo?

Tokyo, live since 2024, lives in Otemachi — the financial district whose datacentres are so dense that the local joke is that the bedrock is worth more as fibre conduit than as land. We peer on JPIX with NTT, Arelion and IIJ on the wall, which is the Japanese equivalent of arriving with references.

The site carries 0.54 Tbit/s of edge capacity and runs 6 ms to Osaka, 13 to Seoul and 24 to Hong Kong. For anything that must feel local in Japan — a game, a site, a proxy for a Japanese service that blocks foreign IPs — Tokyo is the answer, and 56 ms to Mumbai is a reminder that the Indian Ocean routes run through here too.

FLEET · RATE CARD

Plans in Tokyo

Every plan in the catalogue, at the same price as everywhere else. A server here provisions in about fifty-five seconds.

PART EVPS-NANO · REV. D

I Nano

€1.90/mo

billed €€22.80 once· save 21% vs 6-month

vCPU
1 × EPYC
Memory
2 GB DDR5
Storage
25 GB Gen4 NVMe
Traffic
2 TB
Port
1 Gbit/s

Typically used forSmall website · Personal VPN · DNS or monitoring box · Light cron jobs

Configure

PART EVPS-MICRO · REV. D

II Micro

€3.10/mo

billed €€37.20 once· save 21% vs 6-month

vCPU
2 × EPYC
Memory
4 GB DDR5
Storage
50 GB Gen4 NVMe
Traffic
4 TB
Port
1 Gbit/s

Typically used forDiscord or Telegram bot · Mail server · Home lab jump host · Small website

Configure

PART EVPS-BASE · REV. D

Most chosen

III Base

€5.50/mo

billed €€66.00 once· save 20% vs 6-month

vCPU
4 × EPYC
Memory
8 GB DDR5
Storage
100 GB Gen4 NVMe
Traffic
8 TB
Port
2.5 Gbit/s

Typically used forDocker stack · Nextcloud · Staging server · Game server

Configure

PART EVPS-WORK · REV. D

IV Work

€10.40/mo

billed €€124.80 once· save 19% vs 6-month

vCPU
6 × EPYC
Memory
16 GB DDR5
Storage
200 GB Gen4 NVMe
Traffic
12 TB
Port
2.5 Gbit/s

Typically used forProduction web app · Postgres primary · CI runner · Scraping

Configure
Same price in all 41 sitesMost chosen · BaseCompare every plan →

TELECOM SURVEY · 90-DAY MEDIAN

Latency from Tokyo

Median round-trip time to major cities, measured hourly from this site over the last 90 days. The bar is width-proportional; 200 ms fills the track.

Osaka6 ms
Seoul13 ms
Hong Kong24 ms
Singapore44 ms
Sydney86 ms
Mumbai56 ms
Los Angeles92 ms
Frankfurt152 ms

SCALE · 0–200 MS · JPIX

The hardware behind every server

CPU
AMD EPYC 9354P · 3.80 GHz boost
Memory
384 GB DDR5-4800 ECC per host
Storage
Samsung PM9A3 Gen4 NVMe, RAID-10
Network
2 × 25 GbE LACP to separate leaves
Power
A+B feeds, 72 h diesel autonomy
Hypervisor
KVM on Linux 6.12 LTS
Oversubscription
3:1 fair-share · 1:1 dedicated

Identical spec sheet in all 41 sites — the only thing that changes between locations is the sign on the building.

ADJACENT SHEETS

Nearby regions

Eight sites to compare this one against. If a shorter hop changes the answer, the math is the same everywhere.

Seoul

2 ms

South Korea

ICN1 · Asia-Pacific

Osaka

4 ms

Japan

KIX1 · Asia-Pacific

Singapore

2 ms

Singapore

SIN2 · Asia-Pacific

Hong Kong

3 ms

Hong Kong SAR China

HKG1 · Asia-Pacific

Taipei

4 ms

Taiwan

TPE1 · Asia-Pacific

Mumbai

4 ms

India

BOM1 · Asia-Pacific

Bangkok

5 ms

Thailand

BKK1 · Asia-Pacific

Jakarta

5 ms

Indonesia

CGK1 · Asia-Pacific

Q&A · VER. 4.2

Questions about Tokyo

The two answers people actually ask about this site, then the five we give everywhere.

This site

Tokyo or Osaka — does the second city matter?
For most workloads, no: Tokyo to Osaka is 6 ms, roughly the distance from Frankfurt to Paris. Choose Osaka only if your users are concentrated in western Japan and your service is so latency-sensitive that 6 ms moves the product. Tokyo's peering density — JPIX, plus every major carrier in the building — is the tiebreaker for everything else.
Will Japanese services accept connections from a Tokyo VPS?
Usually, yes — that is half the reason people rent here. Japanese streaming and banking sites routinely block foreign IP ranges, and a Tokyo IP is treated as domestic. The other half is speed. Keep the server's behaviour within the acceptable use policy and both halves work as advertised.

Everywhere

Which region should I pick?
Measure, then read. Median RTT decides most cases: pick the site closest to the users you already have, then check the local law if that matters to your data. We do not charge a regional premium, so the decision is never financial.
Is the price the same in every location?
Yes. A Nano costs €1.90 per month in Frankfurt and in São Paulo. There is no regional pricing tier, no 'emerging market' discount and no 'premium location' markup to optimise around.
Can I move a server to another site later?
Take a snapshot, deploy the same image at the destination, restore, update the DNS. The console does not yet automate the migration end-to-end, but nothing about the price changes if you redeploy somewhere else.
Is DDoS protection included?
Standard volumetric filtering is always on and always free at every site. If you need application-layer scrubbing with custom rules, the Advanced tier costs €3.90 per month per server.
What IP addresses do I get?
Every server ships with one dedicated IPv4 and a routed /64 of IPv6, both announced from the site you chose. Additional IPv4s are €1.20 per month each, up to eight per server.

Payments from Japan

Orders from Japan are handled exactly like every other order: checkout in euros, payment in Bitcoin, Monero or any of twenty-four assets, and the server provisions on the first network confirmation. No card, no bank, no name that has to match one.

Payments →

Two decisions, then a network

Pick a size, pick a site, pay in crypto. Moving later is one snapshot and a redeploy away.

Configure in Tokyo →Compare every plan