shipapis
StarSubmit an APISubmit API

Open Government, Luxembourg vs OpenRegistry

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

APIOpen Government, LuxembourgHEALTHY79OpenRegistryDYING86
Uptime · 30d
Uptime · 90d98.9%80.0%
Uptime · 30d100%43.3%
P50 · ms1262241
P95 · ms39831132
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open Government, Luxembourg vs OpenRegistry: common questions

Which is more reliable, Open Government, Luxembourg or OpenRegistry?

On our scheduled checks, Open Government, Luxembourg leads on measured uptime — Open Government, Luxembourg at 98.9% 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.

Which is faster, Open Government, Luxembourg or OpenRegistry?

OpenRegistry has the lower median latency in our checks — Open Government, Luxembourg responds in 1262 ms versus OpenRegistry at 241 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 Open Government, Luxembourg and OpenRegistry need an API key?

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

Only Open Government, Luxembourg 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 Open Government, Luxembourg and OpenRegistry free for commercial use?

Open Government, Luxembourg 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.