Currents vs Florida Man

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

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%96.7%
P50 · ms586255
P95 · ms1165897
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedMIT (repository license)
Free tierFree tier — key may be requiredFree — static JSON on GitHub Pages, no key
Rate limitUnpublishedUnpublished (served via GitHub Pages)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs Florida Man: common questions

Which is more reliable, Currents or Florida Man?

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

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

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

Can I call Currents and Florida Man from the browser?

Only Florida Man is browser-friendly — it returns CORS headers over HTTPS. Currents needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Currents and Florida Man free for commercial use?

Currents has unclear commercial terms, and Florida Man allows commercial use on its free tier. 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.