Disney vs PotterDB

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

Uptime · 30d
Uptime · 90d79.4%100%
Uptime · 30d96.7%100%
P50 · ms409525
P95 · ms9351193
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (data derived from Harry Potter Fandom, CC BY-SA)
Free tierFree, no API key requiredFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Disney vs PotterDB: common questions

Which is more reliable, Disney or PotterDB?

On our scheduled checks, PotterDB leads on measured uptime — Disney at 79.4% versus PotterDB 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, Disney or PotterDB?

Disney has the lower median latency in our checks — Disney responds in 409 ms versus PotterDB at 525 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 Disney and PotterDB need an API key?

Neither needs a paid key — Disney 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 Disney and PotterDB from the browser?

Yes — both Disney and PotterDB send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Disney and PotterDB free for commercial use?

Disney has unclear commercial terms, 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.