iTunes vs My IP API

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

Uptime · 30d
Uptime · 90d68.6%100%
Uptime · 30d46.7%100%
P50 · ms578306
P95 · ms1426700
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

iTunes vs My IP API: common questions

Which is more reliable, iTunes or My IP API?

On our scheduled checks, My IP API leads on measured uptime — iTunes at 68.6% versus My IP API at 100% 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 My IP API?

My IP API has the lower median latency in our checks — iTunes responds in 578 ms versus My IP API at 306 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 My IP API need an API key?

Neither needs a paid key — iTunes is callable with no signup, and My IP API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call iTunes and My IP API from the browser?

Only My IP API 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 My IP API free for commercial use?

iTunes has unclear commercial terms, and My IP API 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.