GLWS · Tokyo / Japan

Tokyo.
GLWS hosting close to your users.

Our Japanese capital location. Tokyo suits Japanese audiences and applications serving East Asia. Pair it with Osaka when you want a second Japanese location.

Configure for Tokyo Compare locations

At a glance.

Where it is and who it suits.

LOCATION

Tokyo, Japan

Region: Asia Pacific
Country: Japan
Coordinates: 35.68°, 139.69°
Suits: Japanese users and East Asian traffic.

Coordinates mark the city centre.

FACILITY

GLWS facility in Tokyo.

Where your servers in Tokyo run.

Equinix

Equinix TY2

3-8-21 Higashi-Shinagawa, Shinagawa-ku, Tokyo, Japan

A seven-storey Equinix facility in Tokyo's Shinagawa ward.

Colocation space: 32,487 sq ft
Construction: Seven-storey steel-framed reinforced concrete
Power: N+1 UPS redundancy
Cooling: N+20% redundancy
Fire suppression: Inergen gas system

Architectural illustration of a data centre in Tokyo

Map data © OpenStreetMap contributors · View larger map (opens in a new tab) · 35.6150, 139.7491

Is Tokyo right for you?

Two things to think through.

Consider a second Japanese location

Tokyo and Osaka are far enough apart to be separate failure domains within Japan. If recovery speed matters, decide which one holds live data and which holds copies.

Test from your own users

Latency inside Japan, to the rest of Asia and across the Pacific differs a lot. Measure from the networks your audience actually uses.

Nearby locations.

Distances from Tokyo to the closest GLWS locations.

Osaka

Japan

About 400 km away. Physical minimum round trip about 4.0 ms.

Seoul

South Korea

About 1,150 km away. Physical minimum round trip about 12 ms.

Hong Kong

About 2,880 km away. Physical minimum round trip about 29 ms.

Singapore

About 5,310 km away. Physical minimum round trip about 53 ms.

Distances are straight-line between city centres. The minimum round trip assumes light in fibre at about 200,000 km a second and a straight cable. Real routes are longer, so always test from your own audience. For a second site that survives a regional outage, Seattle is about 7,700 km from Tokyo.

Look at the whole request path.

A nearby server is only one part of your application.

Tokyo and your audience

Compare the route from the audience networks you expect to serve. Test real requests, not only a location label.

Dependencies and data

Count remote APIs, databases, sign-in providers and backup destinations when you plan.

Recovery across locations

Write down how data is restored and who can do it. A copy in another location only helps if you can recover from it.

GLWS VPS plans in Tokyo.

Pick a product, then choose Tokyo in the configurator.

Linux VPS

KVM virtual servers for websites, applications and development.

Dedicated servers

Whole machines, with regional options.

Colocation

Rack space, power and connectivity for your own hardware.

Questions about Tokyo.

Quick answers before you choose.

Which facility is this?

Servers in Tokyo run at Equinix TY2, 3-8-21 Higashi-Shinagawa, Shinagawa-ku, Tokyo, Japan.

Can I choose Tokyo when I configure a plan?

Yes, for any product that offers this location. Your choice is saved with your configuration.

What should I measure?

Test response times and throughput from representative audience networks. Include application dependencies and measure during periods relevant to your users.

What else should I compare?

Compare data handling, resource availability, backup arrangements and the practical process for recovery or on-site work.