Visitor Statistics API vs Administrative Divisions DB

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

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

Visitor Statistics API vs Administrative Divisions DB: common questions

Which is more reliable, Visitor Statistics API or Administrative Divisions DB?

Only Administrative Divisions DB is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Visitor Statistics API and Administrative Divisions DB need an API key?

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

Can I call Visitor Statistics API and Administrative Divisions DB from the browser?

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

Are Visitor Statistics API and Administrative Divisions DB free for commercial use?

Visitor Statistics API has unclear commercial terms, and Administrative Divisions DB 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.