FreeIPAPI vs ISO 3166-2 API

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

Uptime · 30d
Uptime · 90d0.0%100%
Uptime · 30d0.0%100%
P50 · ms1056
P95 · ms2865
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

FreeIPAPI vs ISO 3166-2 API: common questions

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

On our scheduled checks, ISO 3166-2 API leads on measured uptime — FreeIPAPI at 0.0% versus ISO 3166-2 API at 100% 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 FreeIPAPI and ISO 3166-2 API need an API key?

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

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

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

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

FreeIPAPI has unclear commercial terms, and ISO 3166-2 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.