shipapis
StarSubmit an APISubmit API

Cartes.io vs ip.app

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

APICartes.ioNEW—ip.appNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source project; user-generated maps)Unverified
Free tierFree, no API key for public readFree — limits not published
Rate limit60 req/window · 59 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cartes.io vs ip.app: common questions

Which is more reliable, Cartes.io or ip.app?

On our scheduled checks, ip.app leads on measured uptime — Cartes.io at —% versus ip.app at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Cartes.io and ip.app need an API key?

Neither needs a paid key — Cartes.io 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 Cartes.io and ip.app from the browser?

Yes — both Cartes.io 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 Cartes.io and ip.app free for commercial use?

Cartes.io 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.