shipapis
StarSubmit an APISubmit API

Himalayas vs Lobsters

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

APIHimalayasNEW—LobstersNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Himalayas vs Lobsters: common questions

Which is more reliable, Himalayas or Lobsters?

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

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

Can I call Himalayas and Lobsters from the browser?

Neither sends browser-friendly CORS headers reliably, so call Himalayas and Lobsters from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Himalayas and Lobsters free for commercial use?

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