BigDataCloud Geocode vs positionstack

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BigDataCloud Geocode vs positionstack: common questions

Which is more reliable, BigDataCloud Geocode or positionstack?

On our scheduled checks, positionstack leads on measured uptime — BigDataCloud Geocode at —% versus positionstack 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 BigDataCloud Geocode and positionstack need an API key?

BigDataCloud Geocode needs no key, while positionstack requires a free API key. If you want to start calling without signup, reach for BigDataCloud Geocode first.

Can I call BigDataCloud Geocode and positionstack from the browser?

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

Are BigDataCloud Geocode and positionstack free for commercial use?

BigDataCloud Geocode has unclear commercial terms, and positionstack 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.