shipapis
StarSubmit an APISubmit API

IBGE vs ISO 3166 Updates API

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

APIIBGEHEALTHY84ISO 3166 Updates APIHEALTHY79
Uptime · 30d
Uptime · 90d99.44%100%
Uptime · 30d100%100%
P50 · ms8921259
P95 · ms34312062
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?

On our scheduled checks, ISO 3166 Updates API leads on measured uptime — IBGE at 99.44% versus ISO 3166 Updates 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, IBGE or ISO 3166 Updates API?

IBGE has the lower median latency in our checks — IBGE responds in 892 ms versus ISO 3166 Updates API at 1259 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.