shipapis
StarSubmit an APISubmit API

Himalayas vs The Calendar

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

APIHimalayasNEW—The CalendarNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (US federal list per 5 U.S.C. § 6103)
Free tierFree — limits not publishedFree, no auth (per site)
Rate limitUnpublishedNone stated (site advertises no rate limit)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Himalayas vs The Calendar: common questions

Which is more reliable, Himalayas or The Calendar?

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

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

Can I call Himalayas and The Calendar from the browser?

Only The Calendar 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 The Calendar free for commercial use?

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