City, Gdańsk vs OpenRegistry

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

Uptime · 30d
Uptime · 90d98.0%98.0%
Uptime · 30d96.7%96.7%
P50 · ms921363
P95 · ms43811313
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Gdańsk vs OpenRegistry: common questions

Which is more reliable, City, Gdańsk or OpenRegistry?

Both are neck-and-neck — City, Gdańsk and OpenRegistry each measure 98.0% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, City, Gdańsk or OpenRegistry?

OpenRegistry has the lower median latency in our checks — City, Gdańsk responds in 921 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, Gdańsk and OpenRegistry need an API key?

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

Can I call City, Gdańsk and OpenRegistry from the browser?

Yes — both City, Gdańsk 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 City, Gdańsk and OpenRegistry free for commercial use?

City, Gdańsk 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.