ipify vs Packagist

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms14961
P95 · ms354939
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licensen/aUnverified
Free tierUnlimitedFree — limits not published
Rate limitNoneUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

ipify vs Packagist: common questions

Which is more reliable, ipify or Packagist?

On our scheduled checks, Packagist leads on measured uptime — ipify at 99.02% versus Packagist at 100% 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, ipify or Packagist?

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

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

Can I call ipify and Packagist from the browser?

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

Are ipify and Packagist free for commercial use?

ipify allows commercial use on its free tier, and Packagist 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.