Administrative Divisions DB vs Open Topo Data

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (see repo)Unverified
Free tierFree, no API key required (static JSON via CDN)Free — limits not published
Rate limitNone (static files served over CDN)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Administrative Divisions DB vs Open Topo Data: common questions

Which is more reliable, Administrative Divisions DB or Open Topo Data?

On our scheduled checks, Open Topo Data leads on measured uptime — Administrative Divisions DB at —% versus Open Topo Data 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 Administrative Divisions DB and Open Topo Data need an API key?

Neither needs a paid key — Administrative Divisions DB is callable with no signup, and Open Topo Data is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Administrative Divisions DB and Open Topo Data from the browser?

Only Administrative Divisions DB is browser-friendly — it returns CORS headers over HTTPS. Open Topo Data needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Administrative Divisions DB and Open Topo Data free for commercial use?

Administrative Divisions DB has unclear commercial terms, and Open Topo Data 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.