CloudConvert vs ipify

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms433149
P95 · ms1019354
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree tier — key may be requiredUnlimited
Rate limitUnpublishedNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

CloudConvert vs ipify: common questions

Which is more reliable, CloudConvert or ipify?

On our scheduled checks, CloudConvert leads on measured uptime — CloudConvert at 100% 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.

Which is faster, CloudConvert or ipify?

ipify has the lower median latency in our checks — CloudConvert responds in 433 ms versus ipify at 149 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 CloudConvert and ipify need an API key?

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

Can I call CloudConvert and ipify from the browser?

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

Are CloudConvert and ipify free for commercial use?

CloudConvert 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.