FEC vs OpenRegistry

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesyes
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

FEC vs OpenRegistry: common questions

Which is more reliable, FEC or OpenRegistry?

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

Both ask you to authenticate — FEC 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 FEC and OpenRegistry from the browser?

Yes — both FEC and OpenRegistry 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 FEC and OpenRegistry free for commercial use?

FEC 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.