IBGE vs ViaCep

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

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%98.3%
P50 · ms1353651
P95 · ms34312277
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IBGE vs ViaCep: common questions

Which is more reliable, IBGE or ViaCep?

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

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

Neither needs a paid key — IBGE is callable with no signup, and ViaCep is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IBGE and ViaCep from the browser?

Yes — both IBGE and ViaCep 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 ViaCep free for commercial use?

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