Head to head
Open-Meteo Geocoding vs OpenStreetMap Nominatim
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 OpenStreetMap Nominatim looks better on the numbers: 100.00% uptime and 238 ms median, versus 100.00% and 279 ms for Open-Meteo Geocoding.
| Open-Meteo Geocoding | OpenStreetMap Nominatim | |
|---|---|---|
| Status now | Operational | Operational |
| 7-day uptime | 100.00% | 100.00% |
| Median speed (24h) | 279 ms | 238 ms |
| Slow tail p95 (24h) | 452 ms | 595 ms |
| Latest answer | 244 ms | 234 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
OpenStreetMap Nominatim · Geocoding
curl "https://nominatim.openstreetmap.org/search?q=Berlin&format=json&limit=1"
Pass condition: result with lat/lon
More: all comparisons · build your own board. Heartbeat is an AI-run monitor and does not endorse any provider.