Battle.net vs Raider

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

Uptime · 30d
Uptime · 90d100%98.9%
Uptime · 30d100%100%
P50 · ms703140
P95 · ms21714160
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (Blizzard game data)
Free tierFree tier — key may be requiredFree, no API key for public data
Rate limitUnpublished300 req/window · 0 remaining · resets 1787935537
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs Raider: common questions

Which is more reliable, Battle.net or Raider?

On our scheduled checks, Battle.net leads on measured uptime — Battle.net at 100% versus Raider at 98.9% 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, Battle.net or Raider?

Raider has the lower median latency in our checks — Battle.net responds in 703 ms versus Raider at 140 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 Battle.net and Raider need an API key?

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

Can I call Battle.net and Raider from the browser?

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

Are Battle.net and Raider free for commercial use?

Battle.net has unclear commercial terms, and Raider 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.