shipapis
StarSubmit an APISubmit API

FreeGeoIP vs ISO 3166-2 API

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

APIFreeGeoIPHEALTHY97ISO 3166-2 APIHEALTHY84
Uptime · 30d
Uptime · 90d96.1%100%
Uptime · 30d100%100%
P50 · ms2421056
P95 · ms6072865
Authnonenone
CORSyesyes
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

FreeGeoIP vs ISO 3166-2 API: common questions

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

On our scheduled checks, ISO 3166-2 API leads on measured uptime — FreeGeoIP at 96.1% 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.

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

FreeGeoIP has the lower median latency in our checks — FreeGeoIP responds in 242 ms versus ISO 3166-2 API at 1056 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 FreeGeoIP and ISO 3166-2 API need an API key?

Neither needs a paid key — FreeGeoIP 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 FreeGeoIP and ISO 3166-2 API from the browser?

Yes — both FreeGeoIP and ISO 3166-2 API 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 FreeGeoIP and ISO 3166-2 API free for commercial use?

FreeGeoIP 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.