City, Analyze Boston vs OpenRegistry

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Analyze Boston vs OpenRegistry: common questions

Which is more reliable, City, Analyze Boston or OpenRegistry?

On our scheduled checks, OpenRegistry leads on measured uptime — City, Analyze Boston at —% versus OpenRegistry at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do City, Analyze Boston and OpenRegistry need an API key?

Both ask you to authenticate — City, Analyze Boston 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 City, Analyze Boston and OpenRegistry from the browser?

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

Are City, Analyze Boston and OpenRegistry free for commercial use?

City, Analyze Boston 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.