MY IP vs npm Registry

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

Uptime · 30d
Uptime · 90d82.4%100%
Uptime · 30d70.0%100%
P50 · ms210243
P95 · ms11451246
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree (public registry)
Rate limitRetry-After: 721sUnpublished (bulk scraping discouraged)
In directory since2026-07-052026-07-05
operationalpartialdownno data

MY IP vs npm Registry: common questions

Which is more reliable, MY IP or npm Registry?

On our scheduled checks, npm Registry leads on measured uptime — MY IP at 82.4% versus npm Registry 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, MY IP or npm Registry?

MY IP has the lower median latency in our checks — MY IP responds in 210 ms versus npm Registry at 243 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 MY IP and npm Registry need an API key?

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

Can I call MY IP and npm Registry from the browser?

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

Are MY IP and npm Registry free for commercial use?

MY IP has unclear commercial terms, and npm Registry 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.