iTunes vs Warnely

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

Uptime · 30d
Uptime · 90d68.6%90.2%
Uptime · 30d46.7%83.3%
P50 · ms578334
P95 · ms14261375
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

iTunes vs Warnely: common questions

Which is more reliable, iTunes or Warnely?

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

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

Neither needs a paid key — iTunes 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 iTunes and Warnely from the browser?

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

Are iTunes and Warnely free for commercial use?

iTunes 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.