shipapis
StarSubmit an APISubmit API

Cutt.ly vs IPGeolocation

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

APICutt.lyNEW—IPGeolocationREACHABLE—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — 1000 requests/day
Rate limitUnpublished1000 requests/day on free plan
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cutt.ly vs IPGeolocation: common questions

Which is more reliable, Cutt.ly or IPGeolocation?

On our scheduled checks, IPGeolocation leads on measured uptime — Cutt.ly at —% versus IPGeolocation 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 Cutt.ly and IPGeolocation need an API key?

Both ask you to authenticate — Cutt.ly uses an API key and IPGeolocation uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Cutt.ly and IPGeolocation from the browser?

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

Are Cutt.ly and IPGeolocation free for commercial use?

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