shipapis
StarSubmit an APISubmit API

ip.app vs PostalCodes

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

APIip.appHEALTHY100PostalCodesHEALTHY84
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms761030
P95 · ms2762594
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

ip.app vs PostalCodes: common questions

Which is more reliable, ip.app or PostalCodes?

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

Which is faster, ip.app or PostalCodes?

ip.app has the lower median latency in our checks — ip.app responds in 76 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 ip.app and PostalCodes need an API key?

Neither needs a paid key — ip.app 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 ip.app and PostalCodes from the browser?

Only ip.app 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 ip.app and PostalCodes free for commercial use?

ip.app 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.