CPFHub vs OpenRegistry

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

Uptime · 30d
Uptime · 90d0.0%80.0%
Uptime · 30d0.0%43.3%
P50 · ms—241
P95 · ms—1132
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CPFHub vs OpenRegistry: common questions

Which is more reliable, CPFHub or OpenRegistry?

On our scheduled checks, OpenRegistry leads on measured uptime — CPFHub at 0.0% versus OpenRegistry at 80.0% 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 CPFHub and OpenRegistry need an API key?

Both ask you to authenticate — CPFHub uses an API key and OpenRegistry uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call CPFHub and OpenRegistry from the browser?

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

Are CPFHub and OpenRegistry free for commercial use?

CPFHub has unclear commercial terms, and OpenRegistry 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.