Radio Browser vs ShotOG

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

Uptime · 30d
Uptime · 90d95.1%99.02%
Uptime · 30d98.3%100%
P50 · ms556179
P95 · ms2431418
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree and open source — no keyFree tier — API key required
Rate limitUnpublished (clients asked to send a descriptive User-Agent)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Radio Browser vs ShotOG: common questions

Which is more reliable, Radio Browser or ShotOG?

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

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

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

Can I call Radio Browser and ShotOG from the browser?

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

Are Radio Browser and ShotOG free for commercial use?

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