Japan East (Tokyo) · Tokyo, JP. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Oracle Cloud Infrastructure |
|---|---|
| Region code | ap-tokyo-1 |
| Region name | Japan East (Tokyo) |
| Datacentre city | Tokyo, JP |
| Coordinates | 35.68, 139.69 |
| Published IPv4 prefixes | 38 |
| Probe endpoint | https://objectstorage.ap-tokyo-1.oraclecloud.com/ |
| Probe style | a CORS request whose reply the page can read |
| Verification | Resolved to an address inside this region’s own published range, TCP 443 open. Checked 2026-08-21. |
Coordinates are the real datacentre city rather than the marketing region name, because they feed the distance maths below.
Light in fibre covers about 100 km per millisecond of round trip. These are the great-circle distances to Tokyo and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.
| From | Distance | Floor |
|---|---|---|
| New York | 10,850 km | 108 ms |
| Los Angeles | 8,817 km | 88 ms |
| São Paulo | 18,535 km | 185 ms |
| London | 9,559 km | 96 ms |
| Frankfurt | 9,333 km | 93 ms |
| Johannesburg | 13,539 km | 135 ms |
| Dubai | 7,934 km | 79 ms |
| Mumbai | 6,723 km | 67 ms |
| Singapore | 5,314 km | 53 ms |
| Tokyo | 4 km | under 0.5 ms |
| Sydney | 7,826 km | 78 ms |
Within 75 km of Tokyo — near enough that distance sets no meaningful floor between them. When several sit in one city, the fastest is the city’s real floor; a slower neighbour is usually the endpoint’s own server time.
These figures are geometry. Your own round trip to ap-tokyo-1 depends on your connection and the route it takes — open the instrument, pick Oracle, and sweep. Every region is timed from your browser against the endpoint listed above, and the result is split into the part physics demands and the part the network added.
See every Oracle region on the Oracle latency page.