shipapis
StarSubmit an APISubmit API

IPGEO vs Open-Elevation API

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

APIIPGEOHEALTHY71Open-Elevation APIHEALTHY87
Uptime · 30d
Uptime · 90d98.9%86.1%
Uptime · 30d98.3%76.7%
P50 · ms423231
P95 · ms23454287
Authnonenone
CORSyesyes
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 Open-Elevation API: common questions

Which is more reliable, IPGEO or Open-Elevation API?

On our scheduled checks, IPGEO leads on measured uptime — IPGEO at 98.9% versus Open-Elevation API at 86.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, IPGEO or Open-Elevation API?

Open-Elevation API has the lower median latency in our checks — IPGEO responds in 423 ms versus Open-Elevation API at 231 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 Open-Elevation API need an API key?

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

Can I call IPGEO and Open-Elevation API from the browser?

Yes — both IPGEO and Open-Elevation API 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 Open-Elevation API free for commercial use?

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