DFlight API vs wttr.in

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
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

DFlight API vs wttr.in: common questions

Which is more reliable, DFlight API or wttr.in?

Only wttr.in is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do DFlight API and wttr.in need an API key?

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

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

DFlight API 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.