Glax Weather API vs Hong Kong Observatory

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedHKO open data (see terms of use)
Free tierFree — limits not publishedFree, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Glax Weather API vs Hong Kong Observatory: common questions

Which is more reliable, Glax Weather API or Hong Kong Observatory?

On our scheduled checks, Hong Kong Observatory leads on measured uptime — Glax Weather API at —% versus Hong Kong Observatory 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 Glax Weather API and Hong Kong Observatory need an API key?

Neither needs a paid key — Glax Weather API is callable with no signup, and Hong Kong Observatory is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Glax Weather API and Hong Kong Observatory from the browser?

Only Hong Kong Observatory is browser-friendly — it returns CORS headers over HTTPS. Glax Weather API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Glax Weather API and Hong Kong Observatory free for commercial use?

Glax Weather API has unclear commercial terms, and Hong Kong Observatory 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.