City, Gdynia vs Open Government, ACT

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

Uptime · 30d
Uptime · 90d100%93.1%
Uptime · 30d100%90.0%
P50 · ms12303297
P95 · ms39334902
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedPer-dataset
Free tierFree / open dataFree — app token optional (raises limits)
Rate limitUnpublishedThrottled; higher limits with a free Socrata app token
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Gdynia vs Open Government, ACT: common questions

Which is more reliable, City, Gdynia or Open Government, ACT?

On our scheduled checks, City, Gdynia leads on measured uptime — City, Gdynia at 100% versus Open Government, ACT at 93.1% 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 Open Government, ACT?

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

Neither needs a paid key — City, Gdynia is callable with no signup, and Open Government, ACT is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call City, Gdynia and Open Government, ACT from the browser?

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

City, Gdynia has unclear commercial terms, and Open Government, ACT 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.