Israel Central (Jerusalem) · Jerusalem, IL. 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 | il-jerusalem-1 |
| Region name | Israel Central (Jerusalem) |
| Datacentre city | Jerusalem, IL |
| Coordinates | 31.77, 35.21 |
| Published IPv4 prefixes | 14 |
| Probe endpoint | https://objectstorage.il-jerusalem-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 Jerusalem 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 | 9,169 km | 92 ms |
| Los Angeles | 12,186 km | 122 ms |
| São Paulo | 10,644 km | 106 ms |
| London | 3,610 km | 36 ms |
| Frankfurt | 2,991 km | 30 ms |
| Johannesburg | 6,491 km | 65 ms |
| Dubai | 2,088 km | 21 ms |
| Mumbai | 4,013 km | 40 ms |
| Singapore | 7,916 km | 79 ms |
| Tokyo | 9,146 km | 91 ms |
| Sydney | 14,130 km | 141 ms |
Within 75 km of Jerusalem — 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 il-jerusalem-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.