iTunes vs RestoSignals

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

Uptime · 30d
Uptime · 90d23.3%100%
Uptime · 30d0.0%100%
P50 · ms421748
P95 · ms1187748
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-07-052026-10-19
operationalpartialdownno data

iTunes vs RestoSignals: common questions

Which is more reliable, iTunes or RestoSignals?

On our scheduled checks, RestoSignals leads on measured uptime — iTunes at 23.3% versus RestoSignals 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 RestoSignals?

iTunes has the lower median latency in our checks — iTunes responds in 421 ms versus RestoSignals at 748 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 RestoSignals need an API key?

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

Can I call iTunes and RestoSignals from the browser?

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

Are iTunes and RestoSignals free for commercial use?

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