GLWS · Osaka / Japan

Osaka.
GLWS hosting close to your users.

Our second Japanese location. Osaka suits users in western Japan, and works well as a counterpart to Tokyo when you plan for resilience.

FACILITY

GLWS facility in Osaka.

Where your servers in Osaka run.

Equinix

Equinix OS1

Shinmachi, Nishi-ku, Osaka, Japan

Equinix's first Osaka data centre, in central Osaka with a direct, low-latency link to the Dojima communications hub.

Colocation space
64,745 sq ft (6,015 m²)
Construction
Eleven-storey steel frame with seismic protection
Floor load
205 psf (10 kN/m²)
Cooling
N+20% redundancy
Architectural illustration of a data centre in Osaka

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

Is Osaka right for you?

Two things to think through.

Use Osaka for separation

Keeping a copy of your data in a different city from your live environment gives you something to restore from. Decide how current the copy needs to be.

Compare routes to your audience

Test response times from the cities where your users are. Do not assume the nearer city is always the faster one.

Nearby locations.

Distances from Osaka to the closest GLWS locations.

Tokyo

Japan

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

Seoul

South Korea

About 830 km away. Physical minimum round trip about 8.3 ms.

Hong Kong

Hong Kong

About 2,490 km away. Physical minimum round trip about 25 ms.

Singapore

Singapore

About 4,950 km away. Physical minimum round trip about 50 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, Sydney is about 7,800 km from Osaka.

Look at the whole request path.

A nearby server is only one part of your application.

Osaka 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 Osaka.

Pick a product, then choose Osaka in the configurator.

Linux VPS

KVM virtual servers for websites, applications and development.

Colocation

Rack space, power and connectivity for your own hardware.

Questions about Osaka.

Quick answers before you choose.

Which facility is this?

Servers in Osaka run at Equinix OS1, Shinmachi, Nishi-ku, Osaka, Japan.

Can I choose Osaka 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.

Nearby locations.

Other locations in the same region.