shipapis
StarSubmit an APISubmit API

ipapi.co vs IPWhois

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

APIipapi.coDYING35IPWhoisHEALTHY100
Uptime · 30d
Uptime · 90d1.0%100%
Uptime · 30d1.7%100%
P50 · ms44023
P95 · ms440598
AuthnoneapiKey
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — quota not published; returns 429 when exceededFree tier — API key may be required for production
Rate limitUnpublished (429 Quota exceeded)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ipapi.co vs IPWhois: common questions

Which is more reliable, ipapi.co or IPWhois?

On our scheduled checks, IPWhois leads on measured uptime — ipapi.co at 1.0% versus IPWhois 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, ipapi.co or IPWhois?

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

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

Can I call ipapi.co and IPWhois from the browser?

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

ipapi.co 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.