shipapis
StarSubmit an APISubmit API

IPGEO vs Administrative Divisions DB

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

APIIPGEONEW—Administrative Divisions DBNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
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

IPGEO vs Administrative Divisions DB: common questions

Which is more reliable, IPGEO or Administrative Divisions DB?

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

Neither needs a paid key — IPGEO 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 IPGEO and Administrative Divisions DB from the browser?

Yes — both IPGEO and Administrative Divisions DB send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are IPGEO and Administrative Divisions DB free for commercial use?

IPGEO 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.