shipapis
StarSubmit an APISubmit API

ipapi.co vs ISO 3166 Updates API

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

APIipapi.coNEW—ISO 3166 Updates APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — quota not published; returns 429 when exceededFree — limits not published
Rate limitUnpublished (429 Quota exceeded)500 req/window
In directory since2026-07-052026-07-05
operationalpartialdownno data

ipapi.co vs ISO 3166 Updates API: common questions

Which is more reliable, ipapi.co or ISO 3166 Updates API?

On our scheduled checks, ISO 3166 Updates API leads on measured uptime — ipapi.co at —% versus ISO 3166 Updates API at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do ipapi.co and ISO 3166 Updates API need an API key?

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

Can I call ipapi.co and ISO 3166 Updates API from the browser?

Only ISO 3166 Updates API is browser-friendly — it returns CORS headers over HTTPS. ipapi.co needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are ipapi.co and ISO 3166 Updates API free for commercial use?

ipapi.co has unclear commercial terms, and ISO 3166 Updates API 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.