shipapis
StarSubmit an APISubmit API

Open-Meteo Archive vs wttr.in

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

APIOpen-Meteo ArchiveDEAD0wttr.inHEALTHY84
Uptime · 30d
Uptime · 90d0.0%95.1%
Uptime · 30d0.0%98.3%
P50 · ms—700
P95 · ms—4900
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished (informal per-IP throttling)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open-Meteo Archive vs wttr.in: common questions

Which is more reliable, Open-Meteo Archive or wttr.in?

On our scheduled checks, wttr.in leads on measured uptime — Open-Meteo Archive at 0.0% 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.

Do Open-Meteo Archive and wttr.in need an API key?

Neither needs a paid key — Open-Meteo Archive 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 Open-Meteo Archive and wttr.in from the browser?

Yes — both Open-Meteo Archive 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 Open-Meteo Archive and wttr.in free for commercial use?

Open-Meteo Archive 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.