City, Gdańsk vs OpenRegistry

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

Uptime · 30d
Uptime · 90d96.6%80.0%
Uptime · 30d93.1%43.3%
P50 · ms602241
P95 · ms43811132
AuthnoneapiKey
CORSyesno
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?

On our scheduled checks, City, Gdańsk leads on measured uptime — City, Gdańsk at 96.6% 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, City, Gdańsk or OpenRegistry?

OpenRegistry has the lower median latency in our checks — City, Gdańsk responds in 602 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 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?

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