City, Gdynia vs OpenRegistry

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

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%96.7%
P50 · ms1230363
P95 · ms39331313
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree / open dataFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Gdynia vs OpenRegistry: common questions

Which is more reliable, City, Gdynia or OpenRegistry?

On our scheduled checks, City, Gdynia leads on measured uptime — City, Gdynia at 100% versus OpenRegistry at 98.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, City, Gdynia or OpenRegistry?

OpenRegistry has the lower median latency in our checks — City, Gdynia responds in 1230 ms versus OpenRegistry at 363 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 City, Gdynia and OpenRegistry need an API key?

City, Gdynia needs no key, while OpenRegistry requires a free API key. If you want to start calling without signup, reach for City, Gdynia first.

Can I call City, Gdynia and OpenRegistry from the browser?

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

Are City, Gdynia and OpenRegistry free for commercial use?

City, Gdynia 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.