shipapis
StarSubmit an APISubmit API

IP2Proxy vs Open-Elevation API

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

APIIP2ProxyDEAD0Open-Elevation APIHEALTHY86
Uptime · 30d
Uptime · 90d0.0%92.2%
Uptime · 30d0.0%88.3%
P50 · ms—739
P95 · ms—4287
AuthapiKeynone
CORSnoyes
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

IP2Proxy vs Open-Elevation API: common questions

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

On our scheduled checks, Open-Elevation API leads on measured uptime — IP2Proxy at 0.0% versus Open-Elevation API at 92.2% 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 IP2Proxy and Open-Elevation API need an API key?

Open-Elevation API needs no key, while IP2Proxy requires a free API key. If you want to start calling without signup, reach for Open-Elevation API first.

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

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

Are IP2Proxy and Open-Elevation API free for commercial use?

IP2Proxy 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.