Florida Man vs Warnely

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

Uptime · 30d
Uptime · 90d98.0%90.2%
Uptime · 30d96.7%83.3%
P50 · ms255334
P95 · ms8971375
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseMIT (repository license)Unverified
Free tierFree — static JSON on GitHub Pages, no keyFree — limits not published
Rate limitUnpublished (served via GitHub Pages)100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Florida Man vs Warnely: common questions

Which is more reliable, Florida Man or Warnely?

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

Florida Man has the lower median latency in our checks — Florida Man responds in 255 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 Florida Man and Warnely need an API key?

Neither needs a paid key — Florida Man is callable with no signup, and Warnely is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Florida Man and Warnely from the browser?

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

Are Florida Man and Warnely free for commercial use?

Florida Man allows commercial use on its free tier, 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.