xkcd vs PotterDB

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial usenounclear
Data licenseCC BY-NC 2.5Unverified (data derived from Harry Potter Fandom, CC BY-SA)
Free tierFree, no API keyFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

xkcd vs PotterDB: common questions

Which is more reliable, xkcd or PotterDB?

On our scheduled checks, PotterDB leads on measured uptime — xkcd at —% versus PotterDB at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do xkcd and PotterDB need an API key?

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

Can I call xkcd and PotterDB from the browser?

Only PotterDB 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 xkcd and PotterDB free for commercial use?

xkcd is personal/non-commercial only, and PotterDB 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.