DigitalOcean Spaces API vs wttr.in

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished (informal per-IP throttling)
In directory since2026-07-052026-07-05
operationalpartialdownno data

DigitalOcean Spaces API vs wttr.in: common questions

Which is more reliable, DigitalOcean Spaces API or wttr.in?

On our scheduled checks, wttr.in leads on measured uptime — DigitalOcean Spaces API at —% versus wttr.in 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 DigitalOcean Spaces API and wttr.in need an API key?

wttr.in needs no key, while DigitalOcean Spaces API requires a free API key. If you want to start calling without signup, reach for wttr.in first.

Can I call DigitalOcean Spaces API and wttr.in from the browser?

Only wttr.in is browser-friendly — it returns CORS headers over HTTPS. DigitalOcean Spaces API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are DigitalOcean Spaces API and wttr.in free for commercial use?

DigitalOcean Spaces 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.