shipapis
StarSubmit an APISubmit API

IBGE vs IPWhois

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

APIIBGEHEALTHY80IPWhoisHEALTHY100
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms135323
P95 · ms3431598
AuthnoneapiKey
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key may be required for production
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBGE vs IPWhois: common questions

Which is more reliable, IBGE or IPWhois?

Both are neck-and-neck — IBGE and IPWhois 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 IPWhois?

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

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

Can I call IBGE and IPWhois from the browser?

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

Are IBGE and IPWhois free for commercial use?

IBGE has unclear commercial terms, and IPWhois 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.