Colombia Central (Bogota) · Bogota, CO. 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 | sa-bogota-1 |
| Region name | Colombia Central (Bogota) |
| Datacentre city | Bogota, CO |
| Coordinates | 4.71, -74.07 |
| Published IPv4 prefixes | 10 |
| Probe endpoint | https://objectstorage.sa-bogota-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 Bogota 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 | 4,003 km | 40 ms |
| Los Angeles | 5,597 km | 56 ms |
| São Paulo | 4,328 km | 43 ms |
| London | 8,491 km | 85 ms |
| Frankfurt | 9,089 km | 91 ms |
| Johannesburg | 11,447 km | 114 ms |
| Dubai | 13,617 km | 136 ms |
| Mumbai | 15,534 km | 155 ms |
| Singapore | 19,302 km | 193 ms |
| Tokyo | 14,313 km | 143 ms |
| Sydney | 14,334 km | 143 ms |
The closest regions to Bogota on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to sa-bogota-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.