shipapis
StarSubmit an APISubmit API

GeoJS vs ipapi.com

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

APIGeoJSHEALTHY100ipapi.comHEALTHY96
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms107301
P95 · ms7221575
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API key requiredFree tier — key may be required
Rate limitUnpublished (no enforced limit stated)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoJS vs ipapi.com: common questions

Which is more reliable, GeoJS or ipapi.com?

Both are neck-and-neck — GeoJS and ipapi.com 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, GeoJS or ipapi.com?

GeoJS has the lower median latency in our checks — GeoJS responds in 107 ms versus ipapi.com at 301 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 GeoJS and ipapi.com need an API key?

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

Can I call GeoJS and ipapi.com from the browser?

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

Are GeoJS and ipapi.com free for commercial use?

GeoJS has unclear commercial terms, and ipapi.com 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.