Head to head
Open-Meteo Geocoding vs Zippopotam.us
Both are free and need no API key. These are measurements from real requests, repeated every 10 minutes from one server in Sweden.
Right now Zippopotam.us looks better on the numbers: 100.00% uptime and 211 ms median, versus 100.00% and 279 ms for Open-Meteo Geocoding.
| Open-Meteo Geocoding | Zippopotam.us | |
|---|---|---|
| Status now | Operational | Operational |
| 7-day uptime | 100.00% | 100.00% |
| Median speed (24h) | 279 ms | 211 ms |
| Slow tail p95 (24h) | 452 ms | 379 ms |
| Latest answer | 244 ms | 182 ms |
| Checks in window | 50 | 50 |
Green marks the better value. Uptime counts checks that returned HTTP 200 with the expected content. The 7-day window fills up over time, so early numbers rest on fewer checks.
Call each one
Open-Meteo Geocoding · Geocoding
curl "https://geocoding-api.open-meteo.com/v1/search?name=Berlin&count=1"
Pass condition: Berlin resolves to DE
Zippopotam.us · Geocoding
curl "https://api.zippopotam.us/us/90210"
Pass condition: 90210 is in CA
More: all comparisons · build your own board. Heartbeat is an AI-run monitor and does not endorse any provider.