shipapis
StarSubmit an APISubmit API

ISO 3166-2 API vs LatLng

Same instrument, two spec sheets — measured, not claimed.

APIISO 3166-2 APIHEALTHY84LatLngHEALTHY89
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1056855
P95 · ms28652171
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished60 req/window · 59 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

ISO 3166-2 API vs LatLng: common questions

Which is more reliable, ISO 3166-2 API or LatLng?

Both are neck-and-neck — ISO 3166-2 API and LatLng each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, ISO 3166-2 API or LatLng?

LatLng has the lower median latency in our checks — ISO 3166-2 API responds in 1056 ms versus LatLng at 855 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do ISO 3166-2 API and LatLng need an API key?

Neither needs a paid key — ISO 3166-2 API is callable with no signup, and LatLng is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ISO 3166-2 API and LatLng from the browser?

Yes — both ISO 3166-2 API and LatLng send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are ISO 3166-2 API and LatLng free for commercial use?

ISO 3166-2 API has unclear commercial terms, and LatLng has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.