Raider vs xkcd

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

Uptime · 30d
Uptime · 90d98.9%100%
Uptime · 30d100%100%
P50 · ms140199
P95 · ms4160881
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearno
Data licenseUnverified (Blizzard game data)CC BY-NC 2.5
Free tierFree, no API key for public dataFree, no API key
Rate limit300 req/window · 0 remaining · resets 1787935537Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Raider vs xkcd: common questions

Which is more reliable, Raider or xkcd?

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

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

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

Can I call Raider and xkcd from the browser?

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

Are Raider and xkcd free for commercial use?

Raider has unclear commercial terms, and xkcd is personal/non-commercial only. 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.