region·latency

Oracle Cloud latency test

Round-trip time from your browser to every Oracle Cloud Infrastructure region — 57 of them, 17 in North America, 13 in Europe, 12 in Asia, 6 in South America, 5 in the Middle East, 2 in Africa, 2 in Oceania — each against the speed-of-light floor its distance sets, so a slow region is visibly far rather than badly routed.

Is this an Oracle Cloud ping?

Not in the ICMP sense — that is out of reach from a web page. The equivalent is a small HTTPS request to the region’s Object Storage endpoint, which answers 404 rather than 200. That is no obstacle: a refusal arriving quickly measures the path exactly as well as a success would.

How Oracle is probed

objectstorage.{region}.oraclecloud.com answers 404 with Access-Control-Allow-Origin: * from a unicast address inside the region — not an anycast edge.

The first request of a sweep is discarded — it pays for DNS, TCP and TLS — so every sample after it is essentially one round trip, and the reported figure is the fastest of them.

Every Oracle region

RegionCityCountryIPv4 prefixes
af-casablanca-1CasablancaMA12
af-johannesburg-1JohannesburgZA14
ap-batam-1BatamID12
ap-chuncheon-1ChuncheonKR25
ap-delhi-1DelhiIN10
ap-hyderabad-1HyderabadIN22
ap-kulai-1KulaiMY10
ap-kulai-2KulaiMY—
ap-mumbai-1MumbaiIN30
ap-osaka-1OsakaJP20
ap-seoul-1SeoulKR28
ap-singapore-1SingaporeSG22
ap-singapore-2SingaporeSG10
ap-tokyo-1TokyoJP38
eu-amsterdam-1AmsterdamNL33
eu-dublin-3DublinIE10
eu-frankfurt-1FrankfurtDE61
uk-london-1LondonGB44
eu-madrid-1MadridES14
eu-madrid-3MadridES10
eu-marseille-1MarseilleFR14
eu-milan-1MilanIT19
uk-cardiff-1NewportGB15
eu-paris-1ParisFR15
eu-stockholm-1StockholmSE15
eu-turin-1TurinIT—
eu-zurich-1ZurichCH16
me-abudhabi-1Abu DhabiAE10
me-dubai-1DubaiAE16
me-jeddah-1JeddahSA21
il-jerusalem-1JerusalemIL14
me-riyadh-1RiyadhSA11
us-abilene-1Abilene TXUS10
us-ashburn-1Ashburn VAUS72
us-boardman-1Boardman ORUS9
us-chicago-1Chicago ILUS32
us-dallas-1Dallas TXUS13
us-desmoines-1Des Moines IAUS9
us-lenexa-1Lenexa KSUS9
mx-monterrey-1MonterreyMX10
ca-montreal-1MontrealCA15
us-phoenix-1Phoenix AZUS57
mx-queretaro-1QueretaroMX13
us-quincy-1Quincy WAUS9
us-saltlake-2Salt Lake City UTUS8
us-sanantonio-1San Antonio TXUS9
us-sanjose-1San Jose CAUS31
us-shawnee-1Shawnee KSUS9
ca-toronto-1TorontoCA23
ap-melbourne-1MelbourneAU20
ap-sydney-1SydneyAU31
sa-bogota-1BogotaCO10
sa-riodejaneiro-2Rio de JaneiroBR9
sa-santiago-1SantiagoCL22
sa-saopaulo-1Sao PauloBR41
sa-valparaiso-1ValparaisoCL11
sa-vinhedo-1VinhedoBR22

Prefix counts come from Oracle’s own published feed. Each region links to its distance, its physical floor and the endpoint used to time it.

Measure it yourself

Open the instrument, select Oracle, choose regions and run a sweep. Nothing is pre-selected and nothing runs until you press the button.