IBGE vs positionstack

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

Uptime · 30d
Uptime · 90d99.44%100%
Uptime · 30d100%100%
P50 · ms892292
P95 · ms34313328
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBGE vs positionstack: common questions

Which is more reliable, IBGE or positionstack?

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

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

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

Can I call IBGE and positionstack from the browser?

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

Are IBGE and positionstack free for commercial use?

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