Country.is vs ISO 3166-2 API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Country.is vs ISO 3166-2 API: common questions

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

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

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

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

Are Country.is and ISO 3166-2 API free for commercial use?

Country.is 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.