Lyrics.ovh vs Radio Browser

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

Uptime · 30d
Uptime · 90d100%95.1%
Uptime · 30d100%98.3%
P50 · ms1241556
P95 · ms27252431
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (lyrics are third-party copyrighted)Unverified
Free tierFree — no key requiredFree and open source — no key
Rate limitUnpublishedUnpublished (clients asked to send a descriptive User-Agent)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lyrics.ovh vs Radio Browser: common questions

Which is more reliable, Lyrics.ovh or Radio Browser?

On our scheduled checks, Lyrics.ovh leads on measured uptime — Lyrics.ovh at 100% versus Radio Browser at 95.1% 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, Lyrics.ovh or Radio Browser?

Radio Browser has the lower median latency in our checks — Lyrics.ovh responds in 1241 ms versus Radio Browser at 556 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 Lyrics.ovh and Radio Browser need an API key?

Neither needs a paid key — Lyrics.ovh is callable with no signup, and Radio Browser is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Lyrics.ovh and Radio Browser from the browser?

Yes — both Lyrics.ovh and Radio Browser send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Lyrics.ovh and Radio Browser free for commercial use?

Lyrics.ovh has unclear commercial terms, and Radio Browser 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.