shipapis
StarSubmit an APISubmit API

Currents vs Warnely

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

APICurrentsHEALTHY93WarnelyDYING89
Uptime · 30d
Uptime · 90d100%90.2%
Uptime · 30d100%83.3%
P50 · ms586334
P95 · ms11651375
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs Warnely: common questions

Which is more reliable, Currents or Warnely?

On our scheduled checks, Currents leads on measured uptime — Currents at 100% versus Warnely at 90.2% 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, Currents or Warnely?

Warnely has the lower median latency in our checks — Currents responds in 586 ms versus Warnely at 334 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 Currents and Warnely need an API key?

Warnely needs no key, while Currents requires a free API key. If you want to start calling without signup, reach for Warnely first.

Can I call Currents and Warnely from the browser?

Neither sends browser-friendly CORS headers reliably, so call Currents and Warnely from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Currents and Warnely free for commercial use?

Currents has unclear commercial terms, and Warnely 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.