shipapis
StarSubmit an APISubmit API

Himalayas vs Nager.Date

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

APIHimalayasNEW—Nager.DateNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Himalayas vs Nager.Date: common questions

Which is more reliable, Himalayas or Nager.Date?

On our scheduled checks, Nager.Date leads on measured uptime — Himalayas at —% versus Nager.Date 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 Himalayas and Nager.Date need an API key?

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

Can I call Himalayas and Nager.Date from the browser?

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

Are Himalayas and Nager.Date free for commercial use?

Himalayas has unclear commercial terms, and Nager.Date 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.