shipapis
StarSubmit an APISubmit API

IPGeolocation vs Numverify

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

APIIPGeolocationREACHABLE100NumverifyHEALTHY93
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms259449
P95 · ms9941488
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — 1000 requests/dayFree tier — key may be required
Rate limit1000 requests/day on free planUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGeolocation vs Numverify: common questions

Which is more reliable, IPGeolocation or Numverify?

Both are neck-and-neck — IPGeolocation and Numverify 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, IPGeolocation or Numverify?

IPGeolocation has the lower median latency in our checks — IPGeolocation responds in 259 ms versus Numverify at 449 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 IPGeolocation and Numverify need an API key?

Both ask you to authenticate — IPGeolocation uses an API key and Numverify uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call IPGeolocation and Numverify from the browser?

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

Are IPGeolocation and Numverify free for commercial use?

IPGeolocation has unclear commercial terms, and Numverify 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.