shipapis
StarSubmit an APISubmit API

Himalayas vs xfetch

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

APIHimalayasNEW—xfetchNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Himalayas vs xfetch: common questions

Which is more reliable, Himalayas or xfetch?

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

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

Can I call Himalayas and xfetch from the browser?

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

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