CountryStateCity vs ip.app

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CountryStateCity vs ip.app: common questions

Which is more reliable, CountryStateCity or ip.app?

On our scheduled checks, ip.app leads on measured uptime — CountryStateCity at —% versus ip.app 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 CountryStateCity and ip.app need an API key?

ip.app needs no key, while CountryStateCity requires a free API key. If you want to start calling without signup, reach for ip.app first.

Can I call CountryStateCity and ip.app from the browser?

Yes — both CountryStateCity and ip.app 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 CountryStateCity and ip.app free for commercial use?

CountryStateCity has unclear commercial terms, and ip.app 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.