npm Registry vs Piloterr

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree (public registry)Free tier — API key required
Rate limitUnpublished (bulk scraping discouraged)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

npm Registry vs Piloterr: common questions

Which is more reliable, npm Registry or Piloterr?

On our scheduled checks, Piloterr leads on measured uptime — npm Registry at —% versus Piloterr at —% 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 npm Registry and Piloterr need an API key?

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

Can I call npm Registry and Piloterr from the browser?

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

Are npm Registry and Piloterr free for commercial use?

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