GeoNet API vs IPinfo

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

Uptime · 30d
Uptime · 90d100%94.1%
Uptime · 30d100%90.0%
P50 · ms2533200
P95 · ms2808473
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedKeyless /json works with limits; free token recommended (IPinfo Lite offers higher/unlimited access with a token)
Rate limitUnpublishedKeyless/unauthenticated access is rate-limited; numeric caps not stated on the developers page
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoNet API vs IPinfo: common questions

Which is more reliable, GeoNet API or IPinfo?

On our scheduled checks, GeoNet API leads on measured uptime — GeoNet API at 100% versus IPinfo at 94.1% 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, GeoNet API or IPinfo?

IPinfo has the lower median latency in our checks — GeoNet API responds in 2533 ms versus IPinfo at 200 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 GeoNet API and IPinfo need an API key?

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

Can I call GeoNet API and IPinfo from the browser?

Yes — both GeoNet API and IPinfo 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 GeoNet API and IPinfo free for commercial use?

GeoNet API has unclear commercial terms, and IPinfo 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.