shipapis
StarSubmit an APISubmit API

GeoJS vs ip.app

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

APIGeoJSHEALTHY99ip.appHEALTHY100
Uptime · 30d
Uptime · 90d98.9%100%
Uptime · 30d96.6%100%
P50 · ms6275
P95 · ms1137368
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API key requiredFree — limits not published
Rate limitUnpublished (no enforced limit stated)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoJS vs ip.app: common questions

Which is more reliable, GeoJS or ip.app?

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

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

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

Can I call GeoJS and ip.app from the browser?

Yes — both GeoJS and ip.app send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are GeoJS and ip.app free for commercial use?

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