shipapis
StarSubmit an APISubmit API

IPWhois vs ISO 3166-2 API

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

APIIPWhoisNEW—ISO 3166-2 APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPWhois vs ISO 3166-2 API: common questions

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

On our scheduled checks, ISO 3166-2 API leads on measured uptime — IPWhois 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 IPWhois and ISO 3166-2 API need an API key?

ISO 3166-2 API needs no key, while IPWhois requires a free API key. If you want to start calling without signup, reach for ISO 3166-2 API first.

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

Neither sends browser-friendly CORS headers reliably, so call IPWhois and ISO 3166-2 API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

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

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