shipapis
StarSubmit an APISubmit API

IBGE vs ISO 3166 Updates API

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

APIIBGEHEALTHY80ISO 3166 Updates APIHEALTHY78
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms13531402
P95 · ms34312526
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished500 req/window
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBGE vs ISO 3166 Updates API: common questions

Which is more reliable, IBGE or ISO 3166 Updates API?

Both are neck-and-neck — IBGE and ISO 3166 Updates API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, IBGE or ISO 3166 Updates API?

IBGE has the lower median latency in our checks — IBGE responds in 1353 ms versus ISO 3166 Updates API at 1402 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 IBGE and ISO 3166 Updates API need an API key?

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

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

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