IPGeolocation vs ItsThisForThat

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms259242
P95 · ms994555
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — 1000 requests/dayFree — limits not published
Rate limit1000 requests/day on free planUnpublished (docs ask you not to hammer it)
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGeolocation vs ItsThisForThat: common questions

Which is more reliable, IPGeolocation or ItsThisForThat?

Both are neck-and-neck — IPGeolocation and ItsThisForThat 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 ItsThisForThat?

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

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

Can I call IPGeolocation and ItsThisForThat from the browser?

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

Are IPGeolocation and ItsThisForThat free for commercial use?

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