Arbeitnow vs Himalayas

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

Uptime · 30d
Uptime · 90d93.1%99.02%
Uptime · 30d90.0%98.3%
P50 · ms303263
P95 · ms41623783
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredFree — limits not published
Rate limit5 req/window · 4 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Arbeitnow vs Himalayas: common questions

Which is more reliable, Arbeitnow or Himalayas?

On our scheduled checks, Himalayas leads on measured uptime — Arbeitnow at 93.1% versus Himalayas at 99.02% 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, Arbeitnow or Himalayas?

Himalayas has the lower median latency in our checks — Arbeitnow responds in 303 ms versus Himalayas at 263 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 Arbeitnow and Himalayas need an API key?

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

Can I call Arbeitnow and Himalayas from the browser?

Only Arbeitnow 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 Arbeitnow and Himalayas free for commercial use?

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