Saudi Arabia Central (Riyadh) · Riyadh, SA. 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 | me-riyadh-1 |
| Region name | Saudi Arabia Central (Riyadh) |
| Datacentre city | Riyadh, SA |
| Coordinates | 24.71, 46.68 |
| Published IPv4 prefixes | 11 |
| Probe endpoint | https://objectstorage.me-riyadh-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 Riyadh 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,510 km | 105 ms |
| Los Angeles | 13,290 km | 133 ms |
| São Paulo | 11,389 km | 114 ms |
| London | 4,940 km | 49 ms |
| Frankfurt | 4,309 km | 43 ms |
| Johannesburg | 6,004 km | 60 ms |
| Dubai | 868 km | 8.7 ms |
| Mumbai | 2,770 km | 28 ms |
| Singapore | 6,652 km | 67 ms |
| Tokyo | 8,688 km | 87 ms |
| Sydney | 12,785 km | 128 ms |
The closest regions to Riyadh on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to me-riyadh-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.