Hong Kong Observatory vs wttr.in
Same instrument, two spec sheets — measured, not claimed.
Hong Kong Observatory vs wttr.in: common questions
Which is more reliable, Hong Kong Observatory or wttr.in?
On our scheduled checks, Hong Kong Observatory leads on measured uptime — Hong Kong Observatory at 100% versus wttr.in at 95.1% 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, Hong Kong Observatory or wttr.in?
wttr.in has the lower median latency in our checks — Hong Kong Observatory responds in 1415 ms versus wttr.in at 700 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 Hong Kong Observatory and wttr.in need an API key?
Neither needs a paid key — Hong Kong Observatory is callable with no signup, and wttr.in is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Hong Kong Observatory and wttr.in from the browser?
Yes — both Hong Kong Observatory and wttr.in send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.
Are Hong Kong Observatory and wttr.in free for commercial use?
Hong Kong Observatory has unclear commercial terms, and wttr.in 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.