shipapis
StarSubmit an APISubmit API

GeoJS vs ipapi.co

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

APIGeoJSHEALTHY99ipapi.coDEAD0
Uptime · 30d
Uptime · 90d98.9%1.7%
Uptime · 30d96.6%3.4%
P50 · ms62176
P95 · ms1137440
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API key requiredFree — quota not published; returns 429 when exceeded
Rate limitUnpublished (no enforced limit stated)Unpublished (429 Quota exceeded)
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoJS vs ipapi.co: common questions

Which is more reliable, GeoJS or ipapi.co?

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

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

Neither needs a paid key — GeoJS is callable with no signup, and ipapi.co is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

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

Are GeoJS and ipapi.co free for commercial use?

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