shipapis
StarSubmit an APISubmit API

Cutt.ly vs ipify

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

APICutt.lyDEAD0ipifyHEALTHY99
Uptime · 30d
Uptime · 90d0.0%99.02%
Uptime · 30d0.0%100%
P50 · ms—149
P95 · ms—354
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree tier — API key requiredUnlimited
Rate limitUnpublishedNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

Cutt.ly vs ipify: common questions

Which is more reliable, Cutt.ly or ipify?

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

ipify needs no key, while Cutt.ly requires a free API key. If you want to start calling without signup, reach for ipify first.

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

Only ipify 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 ipify free for commercial use?

Cutt.ly has unclear commercial terms, and ipify allows commercial use on its free tier. 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.