Crates.io vs ipify

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%100%
P50 · ms458149
P95 · ms1317354
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedn/a
Free tierFree — limits not publishedUnlimited
Rate limitUnpublishedNone
In directory since2026-07-052026-05-02
operationalpartialdownno data

Crates.io vs ipify: common questions

Which is more reliable, Crates.io or ipify?

Both are neck-and-neck — Crates.io and ipify each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Crates.io or ipify?

ipify has the lower median latency in our checks — Crates.io responds in 458 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 Crates.io and ipify need an API key?

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

Can I call Crates.io and ipify from the browser?

Yes — both Crates.io and ipify 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 Crates.io and ipify free for commercial use?

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