shipapis
StarSubmit an APISubmit API

IPGEO vs PostalCodes

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

APIIPGEOHEALTHY76PostalCodesHEALTHY84
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms2661030
P95 · ms20832594
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGEO vs PostalCodes: common questions

Which is more reliable, IPGEO or PostalCodes?

Both are neck-and-neck — IPGEO and PostalCodes each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, IPGEO or PostalCodes?

IPGEO has the lower median latency in our checks — IPGEO responds in 266 ms versus PostalCodes at 1030 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 IPGEO and PostalCodes need an API key?

Neither needs a paid key — IPGEO is callable with no signup, and PostalCodes is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IPGEO and PostalCodes from the browser?

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

Are IPGEO and PostalCodes free for commercial use?

IPGEO has unclear commercial terms, and PostalCodes 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.