Battle.net vs Raider

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1024223
P95 · ms31731222
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 limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs Raider: common questions

Which is more reliable, Battle.net or Raider?

Both are neck-and-neck — Battle.net and Raider each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Battle.net or Raider?

Raider has the lower median latency in our checks — Battle.net responds in 1024 ms versus Raider at 223 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.