shipapis
StarSubmit an APISubmit API

IPWhois vs ViaCep

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

APIIPWhoisHEALTHY100ViaCepHEALTHY87
Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%98.3%
P50 · ms23651
P95 · ms5982277
AuthapiKeynone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPWhois vs ViaCep: common questions

Which is more reliable, IPWhois or ViaCep?

On our scheduled checks, IPWhois leads on measured uptime — IPWhois 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, IPWhois or ViaCep?

IPWhois has the lower median latency in our checks — IPWhois responds in 23 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 IPWhois and ViaCep need an API key?

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

Can I call IPWhois and ViaCep from the browser?

Only ViaCep 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 IPWhois and ViaCep free for commercial use?

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